[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F1HSNNV1XHH2WD46ASTXPS":3,"skill-same:01M7F1HSNNV1XHH2WD46ASTXPS":49},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M7F1HSNNV1XHH2WD46ASTXPS","make-automation",null,"Automate Make (Integromat) tasks via Rube MCP (Composio): operations, enums, language and timezone lookups. Always search tools first for current schemas.","lza6\u002FArmor-piercing-system-prompts","lza6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F128880206?v=4","01M7EB3K7WPX5T28EJ2NVHE6EG","Chinese-tingfeng","01M7EB3K97E1KQ16QWKJMFNGX8",11,"MIT","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fmake-automation-antigravity-awesome-skills-main\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: make-automation\ndescription: \"Automate Make (Integromat) tasks via Rube MCP (Composio): operations, enums, language and timezone lookups. Always search tools first for current schemas.\"\nrisk: critical\nsource: community\ndate_added: \"2026-02-27\"\n---\n\n# Make Automation via Rube MCP\n\nAutomate Make (formerly Integromat) operations through Composio's Make toolkit via Rube MCP.\n\n## Prerequisites\n\n- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)\n- Active Make connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `make`\n- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas\n\n## Setup\n\n**Get Rube MCP**: Add `https:\u002F\u002Frube.app\u002Fmcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.\n\n\n1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds\n2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `make`\n3. If connection is not ACTIVE, follow the returned auth link to complete Make authentication\n4. Confirm connection status shows ACTIVE before running any workflows\n\n## Core Workflows\n\n### 1. Get Operations Data\n\n**When to use**: User wants to retrieve operation logs or usage data from Make scenarios\n\n**Tool sequence**:\n1. `MAKE_GET_OPERATIONS` - Retrieve operation records [Required]\n\n**Key parameters**:\n- Check current schema via RUBE_SEARCH_TOOLS for available filters\n- May include date range, scenario ID, or status filters\n\n**Pitfalls**:\n- Operations data may be paginated; check for pagination tokens\n- Date filters must match expected format from schema\n- Large result sets should be filtered by date range or scenario\n\n### 2. List Available Languages\n\n**When to use**: User wants to see supported languages for Make scenarios or interfaces\n\n**Tool sequence**:\n1. `MAKE_LIST_ENUMS_LANGUAGES` - Get all supported language codes [Required]\n\n**Key parameters**:\n- No required parameters; returns complete language list\n\n**Pitfalls**:\n- Language codes follow standard locale format (e.g., 'en', 'fr', 'de')\n- List is static and rarely changes; cache results when possible\n\n### 3. List Available Timezones\n\n**When to use**: User wants to see supported timezones for scheduling Make scenarios\n\n**Tool sequence**:\n1. `MAKE_LIST_ENUMS_TIMEZONES` - Get all supported timezone identifiers [Required]\n\n**Key parameters**:\n- No required parameters; returns complete timezone list\n\n**Pitfalls**:\n- Timezone identifiers use IANA format (e.g., 'America\u002FNew_York', 'Europe\u002FLondon')\n- List is static and rarely changes; cache results when possible\n- Use these exact timezone strings when configuring scenario schedules\n\n### 4. Scenario Configuration Lookup\n\n**When to use**: User needs to configure scenarios with correct language and timezone values\n\n**Tool sequence**:\n1. `MAKE_LIST_ENUMS_LANGUAGES` - Get valid language codes [Required]\n2. `MAKE_LIST_ENUMS_TIMEZONES` - Get valid timezone identifiers [Required]\n\n**Key parameters**:\n- No parameters needed for either call\n\n**Pitfalls**:\n- Always verify language and timezone values against these enums before using in configuration\n- Using invalid values in scenario configuration will cause errors\n\n## Common Patterns\n\n### Enum Validation\n\nBefore configuring any Make scenario properties that accept language or timezone:\n```\n1. Call MAKE_LIST_ENUMS_LANGUAGES or MAKE_LIST_ENUMS_TIMEZONES\n2. Verify the desired value exists in the returned list\n3. Use the exact string value from the enum list\n```\n\n### Operations Monitoring\n\n```\n1. Call MAKE_GET_OPERATIONS with date range filters\n2. Analyze operation counts, statuses, and error rates\n3. Identify failed operations for troubleshooting\n```\n\n### Caching Strategy for Enums\n\nSince language and timezone lists are static:\n```\n1. Call MAKE_LIST_ENUMS_LANGUAGES once at workflow start\n2. Store results in memory or local cache\n3. Validate user inputs against cached values\n4. Refresh cache only when starting a new session\n```\n\n### Operations Analysis Workflow\n\nFor scenario health monitoring:\n```\n1. Call MAKE_GET_OPERATIONS with recent date range\n2. Group operations by scenario ID\n3. Calculate success\u002Ffailure ratios per scenario\n4. Identify scenarios with high error rates\n5. Report findings to user or notification channel\n```\n\n### Integration with Other Toolkits\n\nMake workflows often connect to other apps. Compose multi-tool workflows:\n```\n1. Call RUBE_SEARCH_TOOLS to find tools for the target app\n2. Connect required toolkits via RUBE_MANAGE_CONNECTIONS\n3. Use Make operations data to understand workflow execution patterns\n4. Execute equivalent workflows directly via individual app toolkits\n```\n\n## Known Pitfalls\n\n**Limited Toolkit**:\n- The Make toolkit in Composio currently has limited tools (operations, languages, timezones)\n- For full scenario management (creating, editing, running scenarios), consider using Make's native API\n- Always call RUBE_SEARCH_TOOLS to check for newly available tools\n- The toolkit may be expanded over time; re-check periodically\n\n**Operations Data**:\n- Operation records may have significant volume for active accounts\n- Always filter by date range to avoid fetching excessive data\n- Operation counts relate to Make's pricing tiers and quota usage\n- Failed operations should be investigated; they may indicate scenario configuration issues\n\n**Response Parsing**:\n- Response data may be nested under `data` key\n- Enum lists return arrays of objects with code and label fields\n- Operations data includes nested metadata about scenario execution\n- Parse defensively with fallbacks for optional fields\n\n**Rate Limits**:\n- Make API has rate limits per API token\n- Avoid rapid repeated calls to the same endpoint\n- Cache enum results (languages, timezones) as they rarely change\n- Operations queries should use targeted date ranges\n\n**Authentication**:\n- Make API uses token-based authentication\n- Tokens may have different permission scopes\n- Some operations data may be restricted based on token scope\n- Check that the authenticated user has access to the target organization\n\n## Quick Reference\n\n| Task | Tool Slug | Key Params |\n|------|-----------|------------|\n| Get operations | MAKE_GET_OPERATIONS | (check schema for filters) |\n| List languages | MAKE_LIST_ENUMS_LANGUAGES | (none) |\n| List timezones | MAKE_LIST_ENUMS_TIMEZONES | (none) |\n\n## Additional Notes\n\n### Alternative Approaches\n\nSince the Make toolkit has limited tools, consider these alternatives for common Make use cases:\n\n| Make Use Case | Alternative Approach |\n|--------------|---------------------|\n| Trigger a scenario | Use Make's native webhook or API endpoint directly |\n| Create a scenario | Use Make's scenario management API directly |\n| Schedule execution | Use RUBE_MANAGE_RECIPE_SCHEDULE with composed workflows |\n| Multi-app workflow | Compose individual toolkit tools via RUBE_MULTI_EXECUTE_TOOL |\n| Data transformation | Use RUBE_REMOTE_WORKBENCH for complex processing |\n\n### Composing Equivalent Workflows\n\nInstead of relying solely on Make's toolkit, build equivalent automation directly:\n1. Identify the apps involved in your Make scenario\n2. Search for each app's tools via RUBE_SEARCH_TOOLS\n3. Connect all required toolkits\n4. Build the workflow step-by-step using individual app tools\n5. Save as a recipe via RUBE_CREATE_UPDATE_RECIPE for reuse\n\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\n","# Make Automation via Rube MCP\n\nAutomate Make (formerly Integromat) operations through Composio's Make toolkit via Rube MCP.\n\n## Prerequisites\n\n- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)\n- Active Make connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `make`\n- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas\n\n## Setup\n\n**Get Rube MCP**: Add `https:\u002F\u002Frube.app\u002Fmcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.\n\n\n1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds\n2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `make`\n3. If connection is not ACTIVE, follow the returned auth link to complete Make authentication\n4. Confirm connection status shows ACTIVE before running any workflows\n\n## Core Workflows\n\n### 1. Get Operations Data\n\n**When to use**: User wants to retrieve operation logs or usage data from Make scenarios\n\n**Tool sequence**:\n1. `MAKE_GET_OPERATIONS` - Retrieve operation records [Required]\n\n**Key parameters**:\n- Check current schema via RUBE_SEARCH_TOOLS for available filters\n- May include date range, scenario ID, or status filters\n\n**Pitfalls**:\n- Operations data may be paginated; check for pagination tokens\n- Date filters must match expected format from schema\n- Large result sets should be filtered by date range or scenario\n\n### 2. List Available Languages\n\n**When to use**: User wants to see supported languages for Make scenarios or interfaces\n\n**Tool sequence**:\n1. `MAKE_LIST_ENUMS_LANGUAGES` - Get all supported language codes [Required]\n\n**Key parameters**:\n- No required parameters; returns complete language list\n\n**Pitfalls**:\n- Language codes follow standard locale format (e.g., 'en', 'fr', 'de')\n- List is static and rarely changes; cache results when possible\n\n### 3. List Available Timezones\n\n**When to use**: User wants to see supported timezones for scheduling Make scenarios\n\n**Tool sequence**:\n1. `MAKE_LIST_ENUMS_TIMEZONES` - Get all supported timezone identifiers [Required]\n\n**Key parameters**:\n- No required parameters; returns complete timezone list\n\n**Pitfalls**:\n- Timezone identifiers use IANA format (e.g., 'America\u002FNew_York', 'Europe\u002FLondon')\n- List is static and rarely changes; cache results when possible\n- Use these exact timezone strings when configuring scenario schedules\n\n### 4. Scenario Configuration Lookup\n\n**When to use**: User needs to configure scenarios with correct language and timezone values\n\n**Tool sequence**:\n1. `MAKE_LIST_ENUMS_LANGUAGES` - Get valid language codes [Required]\n2. `MAKE_LIST_ENUMS_TIMEZONES` - Get valid timezone identifiers [Required]\n\n**Key parameters**:\n- No parameters needed for either call\n\n**Pitfalls**:\n- Always verify language and timezone values against these enums before using in configuration\n- Using invalid values in scenario configuration will cause errors\n\n## Common Patterns\n\n### Enum Validation\n\nBefore configuring any Make scenario properties that accept language or timezone:\n```\n1. Call MAKE_LIST_ENUMS_LANGUAGES or MAKE_LIST_ENUMS_TIMEZONES\n2. Verify the desired value exists in the returned list\n3. Use the exact string value from the enum list\n```\n\n### Operations Monitoring\n\n```\n1. Call MAKE_GET_OPERATIONS with date range filters\n2. Analyze operation counts, statuses, and error rates\n3. Identify failed operations for troubleshooting\n```\n\n### Caching Strategy for Enums\n\nSince language and timezone lists are static:\n```\n1. Call MAKE_LIST_ENUMS_LANGUAGES once at workflow start\n2. Store results in memory or local cache\n3. Validate user inputs against cached values\n4. Refresh cache only when starting a new session\n```\n\n### Operations Analysis Workflow\n\nFor scenario health monitoring:\n```\n1. Call MAKE_GET_OPERATIONS with recent date range\n2. Group operations by scenario ID\n3. Calculate success\u002Ffailure ratios per scenario\n4. Identify scenarios with high error rates\n5. Report findings to user or notification channel\n```\n\n### Integration with Other Toolkits\n\nMake workflows often connect to other apps. Compose multi-tool workflows:\n```\n1. Call RUBE_SEARCH_TOOLS to find tools for the target app\n2. Connect required toolkits via RUBE_MANAGE_CONNECTIONS\n3. Use Make operations data to understand workflow execution patterns\n4. Execute equivalent workflows directly via individual app toolkits\n```\n\n## Known Pitfalls\n\n**Limited Toolkit**:\n- The Make toolkit in Composio currently has limited tools (operations, languages, timezones)\n- For full scenario management (creating, editing, running scenarios), consider using Make's native API\n- Always call RUBE_SEARCH_TOOLS to check for newly available tools\n- The toolkit may be expanded over time; re-check periodically\n\n**Operations Data**:\n- Operation records may have significant volume for active accounts\n- Always filter by date range to avoid fetching excessive data\n- Operation counts relate to Make's pricing tiers and quota usage\n- Failed operations should be investigated; they may indicate scenario configuration issues\n\n**Response Parsing**:\n- Response data may be nested under `data` key\n- Enum lists return arrays of objects with code and label fields\n- Operations data includes nested metadata about scenario execution\n- Parse defensively with fallbacks for optional fields\n\n**Rate Limits**:\n- Make API has rate limits per API token\n- Avoid rapid repeated calls to the same endpoint\n- Cache enum results (languages, timezones) as they rarely change\n- Operations queries should use targeted date ranges\n\n**Authentication**:\n- Make API uses token-based authentication\n- Tokens may have different permission scopes\n- Some operations data may be restricted based on token scope\n- Check that the authenticated user has access to the target organization\n\n## Quick Reference\n\n| Task | Tool Slug | Key Params |\n|------|-----------|------------|\n| Get operations | MAKE_GET_OPERATIONS | (check schema for filters) |\n| List languages | MAKE_LIST_ENUMS_LANGUAGES | (none) |\n| List timezones | MAKE_LIST_ENUMS_TIMEZONES | (none) |\n\n## Additional Notes\n\n### Alternative Approaches\n\nSince the Make toolkit has limited tools, consider these alternatives for common Make use cases:\n\n| Make Use Case | Alternative Approach |\n|--------------|---------------------|\n| Trigger a scenario | Use Make's native webhook or API endpoint directly |\n| Create a scenario | Use Make's scenario management API directly |\n| Schedule execution | Use RUBE_MANAGE_RECIPE_SCHEDULE with composed workflows |\n| Multi-app workflow | Compose individual toolkit tools via RUBE_MULTI_EXECUTE_TOOL |\n| Data transformation | Use RUBE_REMOTE_WORKBENCH for complex processing |\n\n### Composing Equivalent Workflows\n\nInstead of relying solely on Make's toolkit, build equivalent automation directly:\n1. Identify the apps involved in your Make scenario\n2. Search for each app's tools via RUBE_SEARCH_TOOLS\n3. Connect all required toolkits\n4. Build the workflow step-by-step using individual app tools\n5. Save as a recipe via RUBE_CREATE_UPDATE_RECIPE for reuse\n\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\n",{"name":5,"risk":24,"source":25,"date_added":26,"description":7},"critical","community","2026-02-27","main","d69096e239f2a89aabc2cd078c47664a9d3b1e11","05-技能与代理开发\u002Fmake-automation-antigravity-awesome-skills-main",3,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts","https:\u002F\u002Fgithub.com\u002Flza6","个人vx：Tf00798\r\n个人✈：@TFGY999","2026-10-08 14:29:22",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add lza6\u002FArmor-piercing-system-prompts --skill make-automation",{"tool":41,"command":42},"bunx","bunx skills add lza6\u002FArmor-piercing-system-prompts --skill make-automation",{"tool":44,"command":45},"pnpm","pnpm dlx skills add lza6\u002FArmor-piercing-system-prompts --skill make-automation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fmake-automation-antigravity-awesome-skills-main\u002FSKILL.md",true,[],[50,57,62,69,76,83],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":19},"01M7FFG485KY83TD6HSC4YPCMC","obsidian-clipper-template-creator","Guide for creating templates for the Obsidian Web Clipper. Use when you want to create a new clipping template, understand available variables, or format clipped content.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator\u002FSKILL.md",[],[],{"skillNo":58,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M7FFG0T6AZ0STEJPSB3CX84K","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator-antigravity-awesome-skills-main\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M7FFFY0QEM14SKWPDYGMXM2P","python-api","Programmatic Object-Detection-Metrics API guidance for BoundingBox, BoundingBoxes, Evaluator, enums, coordinate conversion, AP\u002FmAP semantics, and source-style import diagnostics.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Fpython-api\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M7FFFVZQZ2GJ0C0TGP7JHD20","file-evaluation","Folder-based PASCAL VOC AP\u002FmAP evaluation from ground-truth and detection text files.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Ffile-evaluation\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M7FFFSFNYSE77SJ6PE1CK2DA","object-detection-metrics","Guides legacy Object-Detection-Metrics PASCAL VOC AP\u002FmAP evaluation from detection text folders and direct Python API classes.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M7FFFP0GCK1RVXBCPQ8APBMT","nx-workspace-patterns","Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fnx-workspace-patterns\u002FSKILL.md",[],[]]