[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6G15ZJ0RFQC7WN5S2YSCF2D":3,"skill-same:01M6G15ZJ0RFQC7WN5S2YSCF2D":70},{"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":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":48,"commitSha":49,"skillDirectory":50,"forksCount":14,"repositoryHtmlUrl":51,"repositoryHomepageUrl":6,"ownerHtmlUrl":52,"ownerBlogUrl":53,"ownerDescription":54,"updatedAt":55,"install":56,"resources":69},"01M6G15ZJ0RFQC7WN5S2YSCF2D","render-automation",null,"Automate Render tasks via Rube MCP (Composio): services, deployments, projects. 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\u002Fskills\u002Fautomation\u002Frender-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,38],"automation","render automation","render","MCP","tasks","search","services","Tools","first","projects","automate","deployments","community","composio","via","2026-11-10 10:12:30",false,"---\nname: render-automation\ndescription: \"Automate Render tasks via Rube MCP (Composio): services, deployments, projects. Always search tools first for current schemas.\"\nrequires:\n  mcp: [rube]\nrisk: unknown\nsource: community\n---\n\n# Render Automation via Rube MCP\n\nAutomate Render cloud platform operations through Composio's Render toolkit via Rube MCP.\n\n## Prerequisites\n\n- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)\n- Active Render connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `render`\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 `render`\n3. If connection is not ACTIVE, follow the returned auth link to complete Render authentication\n4. Confirm connection status shows ACTIVE before running any workflows\n\n## Core Workflows\n\n### 1. List and Browse Services\n\n**When to use**: User wants to find or inspect Render services (web services, static sites, workers, cron jobs)\n\n**Tool sequence**:\n1. `RENDER_LIST_SERVICES` - List all services with optional filters [Required]\n\n**Key parameters**:\n- `name`: Filter services by name substring\n- `type`: Filter by service type ('web_service', 'static_site', 'private_service', 'background_worker', 'cron_job')\n- `limit`: Maximum results per page (default 20, max 100)\n- `cursor`: Pagination cursor from previous response\n\n**Pitfalls**:\n- Service types must match exact enum values: 'web_service', 'static_site', 'private_service', 'background_worker', 'cron_job'\n- Pagination uses cursor-based approach; follow `cursor` until absent\n- Name filter is substring-based, not exact match\n- Service IDs follow the format 'srv-xxxxxxxxxxxx'\n- Default limit is 20; set higher for comprehensive listing\n\n### 2. Trigger Deployments\n\n**When to use**: User wants to manually deploy or redeploy a service\n\n**Tool sequence**:\n1. `RENDER_LIST_SERVICES` - Find the service to deploy [Prerequisite]\n2. `RENDER_TRIGGER_DEPLOY` - Trigger a new deployment [Required]\n3. `RENDER_RETRIEVE_DEPLOY` - Monitor deployment progress [Optional]\n\n**Key parameters**:\n- For TRIGGER_DEPLOY:\n  - `serviceId`: Service ID to deploy (required, format: 'srv-xxxxxxxxxxxx')\n  - `clearCache`: Set `true` to clear build cache before deploying\n- For RETRIEVE_DEPLOY:\n  - `serviceId`: Service ID\n  - `deployId`: Deploy ID from trigger response (format: 'dep-xxxxxxxxxxxx')\n\n**Pitfalls**:\n- `serviceId` is required; resolve via LIST_SERVICES first\n- Service IDs start with 'srv-' prefix\n- Deploy IDs start with 'dep-' prefix\n- `clearCache: true` forces a clean build; takes longer but resolves cache-related issues\n- Deployment is asynchronous; use RETRIEVE_DEPLOY to poll status\n- Triggering a deploy while another is in progress may queue the new one\n\n### 3. Monitor Deployment Status\n\n**When to use**: User wants to check the progress or result of a deployment\n\n**Tool sequence**:\n1. `RENDER_RETRIEVE_DEPLOY` - Get deployment details and status [Required]\n\n**Key parameters**:\n- `serviceId`: Service ID (required)\n- `deployId`: Deployment ID (required)\n- Response includes `status`, `createdAt`, `updatedAt`, `finishedAt`, `commit`\n\n**Pitfalls**:\n- Both `serviceId` and `deployId` are required\n- Deploy statuses include: 'created', 'build_in_progress', 'update_in_progress', 'live', 'deactivated', 'build_failed', 'update_failed', 'canceled'\n- 'live' indicates successful deployment\n- 'build_failed' or 'update_failed' indicate deployment errors\n- Poll at reasonable intervals (10-30 seconds) to avoid rate limits\n\n### 4. Manage Projects\n\n**When to use**: User wants to list and organize Render projects\n\n**Tool sequence**:\n1. `RENDER_LIST_PROJECTS` - List all projects [Required]\n\n**Key parameters**:\n- `limit`: Maximum results per page (max 100)\n- `cursor`: Pagination cursor from previous response\n\n**Pitfalls**:\n- Projects group related services together\n- Pagination uses cursor-based approach\n- Project IDs are used for organizational purposes\n- Not all services may be assigned to a project\n\n## Common Patterns\n\n### ID Resolution\n\n**Service name -> Service ID**:\n```\n1. Call RENDER_LIST_SERVICES with name=service_name\n2. Find service by name in results\n3. Extract id (format: 'srv-xxxxxxxxxxxx')\n```\n\n**Deployment lookup**:\n```\n1. Store deployId from RENDER_TRIGGER_DEPLOY response\n2. Call RENDER_RETRIEVE_DEPLOY with serviceId and deployId\n3. Check status for completion\n```\n\n### Deploy and Monitor Pattern\n\n```\n1. RENDER_LIST_SERVICES -> find service by name -> get serviceId\n2. RENDER_TRIGGER_DEPLOY with serviceId -> get deployId\n3. Loop: RENDER_RETRIEVE_DEPLOY with serviceId + deployId\n4. Check status: 'live' = success, 'build_failed'\u002F'update_failed' = error\n5. Continue polling until terminal state reached\n```\n\n### Pagination\n\n- Use `cursor` from response for next page\n- Continue until `cursor` is absent or results are empty\n- Both LIST_SERVICES and LIST_PROJECTS use cursor-based pagination\n- Set `limit` to max (100) for fewer pagination rounds\n\n## Known Pitfalls\n\n**Service IDs**:\n- Always prefixed with 'srv-' (e.g., 'srv-abcd1234efgh')\n- Deploy IDs prefixed with 'dep-' (e.g., 'dep-d2mqkf9r0fns73bham1g')\n- Always resolve service names to IDs via LIST_SERVICES\n\n**Service Types**:\n- Must use exact enum values when filtering\n- Available types: web_service, static_site, private_service, background_worker, cron_job\n- Different service types have different deployment behaviors\n\n**Deployment Behavior**:\n- Deployments are asynchronous; always poll for completion\n- Clear cache deploys take longer but resolve stale cache issues\n- Failed deploys do not roll back automatically; the previous version stays live\n- Concurrent deploy triggers may be queued\n\n**Rate Limits**:\n- Render API has rate limits\n- Avoid rapid polling; use 10-30 second intervals\n- Bulk operations should be throttled\n\n**Response Parsing**:\n- Response data may be nested under `data` key\n- Timestamps use ISO 8601 format\n- Parse defensively with fallbacks for optional fields\n\n## Quick Reference\n\n| Task | Tool Slug | Key Params |\n|------|-----------|------------|\n| List services | RENDER_LIST_SERVICES | name, type, limit, cursor |\n| Trigger deploy | RENDER_TRIGGER_DEPLOY | serviceId, clearCache |\n| Get deploy status | RENDER_RETRIEVE_DEPLOY | serviceId, deployId |\n| List projects | RENDER_LIST_PROJECTS | limit, cursor |\n\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\n","# Render Automation via Rube MCP\n\nAutomate Render cloud platform operations through Composio's Render toolkit via Rube MCP.\n\n## Prerequisites\n\n- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)\n- Active Render connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `render`\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 `render`\n3. If connection is not ACTIVE, follow the returned auth link to complete Render authentication\n4. Confirm connection status shows ACTIVE before running any workflows\n\n## Core Workflows\n\n### 1. List and Browse Services\n\n**When to use**: User wants to find or inspect Render services (web services, static sites, workers, cron jobs)\n\n**Tool sequence**:\n1. `RENDER_LIST_SERVICES` - List all services with optional filters [Required]\n\n**Key parameters**:\n- `name`: Filter services by name substring\n- `type`: Filter by service type ('web_service', 'static_site', 'private_service', 'background_worker', 'cron_job')\n- `limit`: Maximum results per page (default 20, max 100)\n- `cursor`: Pagination cursor from previous response\n\n**Pitfalls**:\n- Service types must match exact enum values: 'web_service', 'static_site', 'private_service', 'background_worker', 'cron_job'\n- Pagination uses cursor-based approach; follow `cursor` until absent\n- Name filter is substring-based, not exact match\n- Service IDs follow the format 'srv-xxxxxxxxxxxx'\n- Default limit is 20; set higher for comprehensive listing\n\n### 2. Trigger Deployments\n\n**When to use**: User wants to manually deploy or redeploy a service\n\n**Tool sequence**:\n1. `RENDER_LIST_SERVICES` - Find the service to deploy [Prerequisite]\n2. `RENDER_TRIGGER_DEPLOY` - Trigger a new deployment [Required]\n3. `RENDER_RETRIEVE_DEPLOY` - Monitor deployment progress [Optional]\n\n**Key parameters**:\n- For TRIGGER_DEPLOY:\n  - `serviceId`: Service ID to deploy (required, format: 'srv-xxxxxxxxxxxx')\n  - `clearCache`: Set `true` to clear build cache before deploying\n- For RETRIEVE_DEPLOY:\n  - `serviceId`: Service ID\n  - `deployId`: Deploy ID from trigger response (format: 'dep-xxxxxxxxxxxx')\n\n**Pitfalls**:\n- `serviceId` is required; resolve via LIST_SERVICES first\n- Service IDs start with 'srv-' prefix\n- Deploy IDs start with 'dep-' prefix\n- `clearCache: true` forces a clean build; takes longer but resolves cache-related issues\n- Deployment is asynchronous; use RETRIEVE_DEPLOY to poll status\n- Triggering a deploy while another is in progress may queue the new one\n\n### 3. Monitor Deployment Status\n\n**When to use**: User wants to check the progress or result of a deployment\n\n**Tool sequence**:\n1. `RENDER_RETRIEVE_DEPLOY` - Get deployment details and status [Required]\n\n**Key parameters**:\n- `serviceId`: Service ID (required)\n- `deployId`: Deployment ID (required)\n- Response includes `status`, `createdAt`, `updatedAt`, `finishedAt`, `commit`\n\n**Pitfalls**:\n- Both `serviceId` and `deployId` are required\n- Deploy statuses include: 'created', 'build_in_progress', 'update_in_progress', 'live', 'deactivated', 'build_failed', 'update_failed', 'canceled'\n- 'live' indicates successful deployment\n- 'build_failed' or 'update_failed' indicate deployment errors\n- Poll at reasonable intervals (10-30 seconds) to avoid rate limits\n\n### 4. Manage Projects\n\n**When to use**: User wants to list and organize Render projects\n\n**Tool sequence**:\n1. `RENDER_LIST_PROJECTS` - List all projects [Required]\n\n**Key parameters**:\n- `limit`: Maximum results per page (max 100)\n- `cursor`: Pagination cursor from previous response\n\n**Pitfalls**:\n- Projects group related services together\n- Pagination uses cursor-based approach\n- Project IDs are used for organizational purposes\n- Not all services may be assigned to a project\n\n## Common Patterns\n\n### ID Resolution\n\n**Service name -> Service ID**:\n```\n1. Call RENDER_LIST_SERVICES with name=service_name\n2. Find service by name in results\n3. Extract id (format: 'srv-xxxxxxxxxxxx')\n```\n\n**Deployment lookup**:\n```\n1. Store deployId from RENDER_TRIGGER_DEPLOY response\n2. Call RENDER_RETRIEVE_DEPLOY with serviceId and deployId\n3. Check status for completion\n```\n\n### Deploy and Monitor Pattern\n\n```\n1. RENDER_LIST_SERVICES -> find service by name -> get serviceId\n2. RENDER_TRIGGER_DEPLOY with serviceId -> get deployId\n3. Loop: RENDER_RETRIEVE_DEPLOY with serviceId + deployId\n4. Check status: 'live' = success, 'build_failed'\u002F'update_failed' = error\n5. Continue polling until terminal state reached\n```\n\n### Pagination\n\n- Use `cursor` from response for next page\n- Continue until `cursor` is absent or results are empty\n- Both LIST_SERVICES and LIST_PROJECTS use cursor-based pagination\n- Set `limit` to max (100) for fewer pagination rounds\n\n## Known Pitfalls\n\n**Service IDs**:\n- Always prefixed with 'srv-' (e.g., 'srv-abcd1234efgh')\n- Deploy IDs prefixed with 'dep-' (e.g., 'dep-d2mqkf9r0fns73bham1g')\n- Always resolve service names to IDs via LIST_SERVICES\n\n**Service Types**:\n- Must use exact enum values when filtering\n- Available types: web_service, static_site, private_service, background_worker, cron_job\n- Different service types have different deployment behaviors\n\n**Deployment Behavior**:\n- Deployments are asynchronous; always poll for completion\n- Clear cache deploys take longer but resolve stale cache issues\n- Failed deploys do not roll back automatically; the previous version stays live\n- Concurrent deploy triggers may be queued\n\n**Rate Limits**:\n- Render API has rate limits\n- Avoid rapid polling; use 10-30 second intervals\n- Bulk operations should be throttled\n\n**Response Parsing**:\n- Response data may be nested under `data` key\n- Timestamps use ISO 8601 format\n- Parse defensively with fallbacks for optional fields\n\n## Quick Reference\n\n| Task | Tool Slug | Key Params |\n|------|-----------|------------|\n| List services | RENDER_LIST_SERVICES | name, type, limit, cursor |\n| Trigger deploy | RENDER_TRIGGER_DEPLOY | serviceId, clearCache |\n| Get deploy status | RENDER_RETRIEVE_DEPLOY | serviceId, deployId |\n| List projects | RENDER_LIST_PROJECTS | limit, cursor |\n\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\n",{"name":5,"risk":44,"source":36,"requires":45,"description":7},"unknown",{"mcp":46},[47],"rube","master","dff58085da947e81e8418c922055644bf0082b1b","skills\u002Fautomation\u002Frender-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":57,"prompt":67,"zipAvailable":68},[58,61,64],{"tool":59,"command":60},"npx","npx skills add reikiplanet\u002Fdaoskills --skill render-automation",{"tool":62,"command":63},"bunx","bunx skills add reikiplanet\u002Fdaoskills --skill render-automation",{"tool":65,"command":66},"pnpm","pnpm dlx skills add reikiplanet\u002Fdaoskills --skill render-automation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fskills\u002Fautomation\u002Frender-automation\u002FSKILL.md",true,[],[71,97,109,123,143,166],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":39},"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",[],[78,79,80,81,82,83,36,84,85,86,87,88,89,90,91,92,93,94,95,96],"games","web games","web","grep","principles","selection","framework selection","edit","write","read","pwa","game","web browser","game development","Optimization","framework","browser","development","webgpu",{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":39},"01M6G611H2YGV0GZFP90D38ZMJ","vr-ar","VR\u002FAR development principles. Comfort, interaction, performance requirements.","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fvr-ar\u002FSKILL.md",[],[104,105,95,106,107,36,85,86,87,81,108,82],"ar","vr ar","interaction","requirements","performance",{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":39},"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",[],[111,116,117,118,119,120,36,121,87,33,122,81],"project scaffolding","From Scratch","tech","project","scaffolding","use","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":39},"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,36,135,136,137,138,121,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":39},"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,36,87,81,158,82,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":39},"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,121,181,182,183,36,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"]