[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F40VV327WST3FEXQCW9C38":3,"skill-same:01M7F40VV327WST3FEXQCW9C38":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},"01M7F40VV327WST3FEXQCW9C38","render-automation",null,"Automate Render tasks via Rube MCP (Composio): services, deployments, projects. 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-技能与代理开发\u002Frender-automation-antigravity-awesome-skills-main\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: render-automation\ndescription: \"Automate Render tasks via Rube MCP (Composio): services, deployments, projects. Always search tools first for current schemas.\"\nrisk: unknown\nsource: community\ndate_added: \"2026-02-27\"\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":24,"source":25,"date_added":26,"description":7},"unknown","community","2026-02-27","main","d69096e239f2a89aabc2cd078c47664a9d3b1e11","05-技能与代理开发\u002Frender-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 render-automation",{"tool":41,"command":42},"bunx","bunx skills add lza6\u002FArmor-piercing-system-prompts --skill render-automation",{"tool":44,"command":45},"pnpm","pnpm dlx skills add lza6\u002FArmor-piercing-system-prompts --skill render-automation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Frender-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",[],[]]