[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6FSMP30QG1PJDQZD18TVYT3":3,"skill-same:01M6FSMP30QG1PJDQZD18TVYT3":69},{"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":23,"publishedAt":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":47,"commitSha":48,"skillDirectory":49,"forksCount":14,"repositoryHtmlUrl":50,"repositoryHomepageUrl":6,"ownerHtmlUrl":51,"ownerBlogUrl":52,"ownerDescription":53,"updatedAt":54,"install":55,"resources":68},"01M6FSMP30QG1PJDQZD18TVYT3","make-automation",null,"Automate Make (Integromat) tasks via Rube MCP (Composio): operations, enums, language and timezone lookups. Always search tools first for current schemas.","reikiplanet\u002Fdaoskills","reikiplanet","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F96377599?v=4","01M6CVWCMD740YHQDK7E9QYBW4","Reiki Planet","01M6CVWCS4KXVA2CWFVJ43EAXK",0,"MIT","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fautomation\u002Fmake-automation\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37],"automation","make automation","make","MCP","tasks","search","Tools","first","automate","operations","community","language","composio","via","2026-11-10 10:12:30",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.\"\nrequires:\n  mcp: [rube]\nrisk: unknown\nsource: community\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":43,"source":34,"requires":44,"description":7},"unknown",{"mcp":45},[46],"rube","master","dff58085da947e81e8418c922055644bf0082b1b","automation\u002Fmake-automation","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills","https:\u002F\u002Fgithub.com\u002Freikiplanet","https:\u002F\u002Fwww.reiki-planet.com","Reiki Planet Game","2026-03-29 06:02:29",{"source":8,"skillName":5,"commands":56,"prompt":66,"zipAvailable":67},[57,60,63],{"tool":58,"command":59},"npx","npx skills add reikiplanet\u002Fdaoskills --skill make-automation",{"tool":61,"command":62},"bunx","bunx skills add reikiplanet\u002Fdaoskills --skill make-automation",{"tool":64,"command":65},"pnpm","pnpm dlx skills add reikiplanet\u002Fdaoskills --skill make-automation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fautomation\u002Fmake-automation\u002FSKILL.md",true,[],[70,96,108,123,143,166],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":38},"01M6G614JTEQJHPT8AKK3YQ18S","web-games","Web browser game development principles. Framework selection, WebGPU, optimization, PWA.","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fweb-games\u002FSKILL.md",[],[77,78,79,80,81,82,34,83,84,85,86,87,88,89,90,91,92,93,94,95],"games","web games","web","grep","principles","selection","framework selection","edit","write","read","pwa","game","web browser","game development","Optimization","framework","browser","development","webgpu",{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":38},"01M6G611H2YGV0GZFP90D38ZMJ","vr-ar","VR\u002FAR development principles. Comfort, interaction, performance requirements.","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fvr-ar\u002FSKILL.md",[],[103,104,94,105,106,34,84,85,86,80,107,81],"ar","vr ar","interaction","requirements","performance",{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":114,"publishedAt":38},"01M6G60XNMHAMV1SV0EJ1CX0AY","templates","Project scaffolding templates for new applications. Use when creating new projects from scratch. Contains 12 templates for various tech stacks.","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Ftemplates\u002FSKILL.md",[],[110,115,116,117,118,119,34,120,86,121,122,80],"project scaffolding","From Scratch","tech","project","scaffolding","use","projects","applications",{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":129,"publishedAt":38},"01M6G60T0GATMK3Q5H8GDC1Z8S","wcag-audit-patterns","Conduct WCAG 2.2 accessibility audits with automated testing, manual verification, and remediation guidance. Use when auditing websites for accessibility, fixing WCAG violations, or implementing ac...","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fskills\u002Fsecurity\u002Fwcag-audit-patterns\u002FSKILL.md",[],[130,131,132,133,134,34,135,136,137,138,120,139,140,141,142],"wcag audit patterns","wcag audit","patterns","WCAG","audit","manual","with","automated testing","guidance","remediation","verification","accessibility","testing",{"skillNo":144,"name":145,"nameZh":6,"description":146,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":147,"categories":148,"keywords":149,"publishedAt":38},"01M6G60PMCHW1FRZ63F931QK3R","vulnerability-scanner","Advanced vulnerability analysis principles. OWASP 2025, Supply Chain Security, attack surface mapping, risk prioritization.","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fskills\u002Fsecurity\u002Fvulnerability-scanner\u002FSKILL.md",[],[150,151,152,153,154,155,156,157,34,86,80,158,81,159,160,161,162,163,164,165],"scanner","vulnerability scanner","vulnerability","prioritization","2025","mapping","chain","supply chain","Bash","analysis","risk","owasp","supply chain security","security","supply","advanced",{"skillNo":167,"name":168,"nameZh":6,"description":169,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":170,"categories":171,"keywords":172,"publishedAt":38},"01M6G60JZBB8DK0W3DSG1WNMZK","threat-modeling-expert","Expert in threat modeling methodologies, security architecture review, and risk assessment. Masters STRIDE, PASTA, attack trees, and security requirement extraction. Use for security architecture r...","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fskills\u002Fsecurity\u002Fthreat-modeling-expert\u002FSKILL.md",[],[173,174,175,176,177,178,179,180,163,120,181,182,183,34,184,185,186,160,187,188],"modeling","threat modeling expert","threat modeling","expert","threat","risk assessment","architecture review","architecture","security architecture review","trees","security architecture","security requirement extraction","assessment","extraction","review","stride"]