[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-bda423c2-f210-4b5f-b8d9-c1cc8f7e3bc9":3,"$fXvUf8WDPrb00zu3frRK1mQo4SqxnUI8gRYIvknhNu2I":43},{"id":4,"title":5,"description":6,"categoryId":7,"moduleId":8,"tags":9,"prompt":10,"icon":11,"source":12,"sourceUrl":13,"authorId":14,"authorName":15,"isPublic":16,"stars":17,"runs":18,"createdAt":19,"updatedAt":19,"module":20,"category":27,"packages":34},"bda423c2-f210-4b5f-b8d9-c1cc8f7e3bc9","circleci-automation","通过Rube MCP（Composio）自动化CircleCI任务：触发管道、监控工作流程\u002F作业、检索工件和测试元数据。始终首先搜索工具以获取当前模式。","cat_prod_automation","mod_productivity","sickn33,productivity","---\nname: circleci-automation\ndescription: \"Automate CircleCI tasks via Rube MCP (Composio): trigger pipelines, monitor workflows\u002Fjobs, retrieve artifacts and test metadata. Always search tools first for current schemas.\"\nrisk: critical\nsource: community\ndate_added: \"2026-02-27\"\n---\n\n# CircleCI Automation via Rube MCP\n\nAutomate CircleCI CI\u002FCD operations through Composio's CircleCI toolkit via Rube MCP.\n\n## Prerequisites\n\n- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)\n- Active CircleCI connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `circleci`\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 `circleci`\n3. If connection is not ACTIVE, follow the returned auth link to complete CircleCI authentication\n4. Confirm connection status shows ACTIVE before running any workflows\n\n## Core Workflows\n\n### 1. Trigger a Pipeline\n\n**When to use**: User wants to start a new CI\u002FCD pipeline run\n\n**Tool sequence**:\n1. `CIRCLECI_TRIGGER_PIPELINE` - Trigger a new pipeline on a project [Required]\n2. `CIRCLECI_LIST_WORKFLOWS_BY_PIPELINE_ID` - Monitor resulting workflows [Optional]\n\n**Key parameters**:\n- `project_slug`: Project identifier in format `gh\u002Forg\u002Frepo` or `bb\u002Forg\u002Frepo`\n- `branch`: Git branch to run the pipeline on\n- `tag`: Git tag to run the pipeline on (mutually exclusive with branch)\n- `parameters`: Pipeline parameter key-value pairs\n\n**Pitfalls**:\n- `project_slug` format is `{vcs}\u002F{org}\u002F{repo}` (e.g., `gh\u002Fmyorg\u002Fmyrepo`)\n- `branch` and `tag` are mutually exclusive; providing both causes an error\n- Pipeline parameters must match those defined in `.circleci\u002Fconfig.yml`\n- Triggering returns a pipeline ID; workflows start asynchronously\n\n### 2. Monitor Pipelines and Workflows\n\n**When to use**: User wants to check the status of pipelines or workflows\n\n**Tool sequence**:\n1. `CIRCLECI_LIST_PIPELINES_FOR_PROJECT` - List recent pipelines for a project [Required]\n2. `CIRCLECI_LIST_WORKFLOWS_BY_PIPELINE_ID` - List workflows within a pipeline [Required]\n3. `CIRCLECI_GET_PIPELINE_CONFIG` - View the pipeline configuration used [Optional]\n\n**Key parameters**:\n- `project_slug`: Project identifier in `{vcs}\u002F{org}\u002F{repo}` format\n- `pipeline_id`: UUID of a specific pipeline\n- `branch`: Filter pipelines by branch name\n- `page_token`: Pagination cursor for next page of results\n\n**Pitfalls**:\n- Pipeline IDs are UUIDs, not numeric IDs\n- Workflows inherit the pipeline ID; a single pipeline can have multiple workflows\n- Workflow states include: success, running, not_run, failed, error, failing, on_hold, canceled, unauthorized\n- `page_token` is returned in responses for pagination; continue until absent\n\n### 3. Inspect Job Details\n\n**When to use**: User wants to drill into a specific job's execution details\n\n**Tool sequence**:\n1. `CIRCLECI_LIST_WORKFLOWS_BY_PIPELINE_ID` - Find workflow containing the job [Prerequisite]\n2. `CIRCLECI_GET_JOB_DETAILS` - Get detailed job information [Required]\n\n**Key parameters**:\n- `project_slug`: Project identifier\n- `job_number`: Numeric job number (not UUID)\n\n**Pitfalls**:\n- Job numbers are integers, not UUIDs (unlike pipeline and workflow IDs)\n- Job details include executor type, parallelism, start\u002Fstop times, and status\n- Job statuses: success, running, not_run, failed, retried, timedout, infrastructure_fail, canceled\n\n### 4. Retrieve Build Artifacts\n\n**When to use**: User wants to download or list artifacts produced by a job\n\n**Tool sequence**:\n1. `CIRCLECI_GET_JOB_DETAILS` - Confirm job completed successfully [Prerequisite]\n2. `CIRCLECI_GET_JOB_ARTIFACTS` - List all artifacts from the job [Required]\n\n**Key parameters**:\n- `project_slug`: Project identifier\n- `job_number`: Numeric job number\n\n**Pitfalls**:\n- Artifacts are only available after job completion\n- Each artifact has a `path` and `url` for download\n- Artifact URLs may require authentication headers to download\n- Large artifacts may have download size limits\n\n### 5. Review Test Results\n\n**When to use**: User wants to check test outcomes for a specific job\n\n**Tool sequence**:\n1. `CIRCLECI_GET_JOB_DETAILS` - Verify job ran tests [Prerequisite]\n2. `CIRCLECI_GET_TEST_METADATA` - Retrieve test results and metadata [Required]\n\n**Key parameters**:\n- `project_slug`: Project identifier\n- `job_number`: Numeric job number\n\n**Pitfalls**:\n- Test metadata requires the job to have uploaded test results (JUnit XML format)\n- If no test results were uploaded, the response will be empty\n- Test metadata includes classname, name, result, message, and run_time fields\n- Failed tests include failure messages in the `message` field\n\n## Common Patterns\n\n### Project Slug Format\n\n```\nFormat: {vcs_type}\u002F{org_name}\u002F{repo_name}\n- GitHub:    gh\u002Fmyorg\u002Fmyrepo\n- Bitbucket: bb\u002Fmyorg\u002Fmyrepo\n```\n\n### Pipeline -> Workflow -> Job Hierarchy\n\n```\n1. Call CIRCLECI_LIST_PIPELINES_FOR_PROJECT to get pipeline IDs\n2. Call CIRCLECI_LIST_WORKFLOWS_BY_PIPELINE_ID with pipeline_id\n3. Extract job numbers from workflow details\n4. Call CIRCLECI_GET_JOB_DETAILS with job_number\n```\n\n### Pagination\n\n- Check response for `next_page_token` field\n- Pass token as `page_token` in next request\n- Continue until `next_page_token` is absent or null\n\n## Known Pitfalls\n\n**ID Formats**:\n- Pipeline IDs: UUIDs (e.g., `5034460f-c7c4-4c43-9457-de07e2029e7b`)\n- Workflow IDs: UUIDs\n- Job numbers: Integers (e.g., `123`)\n- Do NOT mix up UUIDs and integers between different endpoints\n\n**Project Slugs**:\n- Must include VCS prefix: `gh\u002F` for GitHub, `bb\u002F` for Bitbucket\n- Organization and repo names are case-sensitive\n- Incorrect slug format causes 404 errors\n\n**Rate Limits**:\n- CircleCI API has per-endpoint rate limits\n- Implement exponential backoff on 429 responses\n- Avoid rapid polling; use reasonable intervals (5-10 seconds)\n\n## Quick Reference\n\n| Task | Tool Slug | Key Params |\n|------|-----------|------------|\n| Trigger pipeline | CIRCLECI_TRIGGER_PIPELINE | project_slug, branch, parameters |\n| List pipelines | CIRCLECI_LIST_PIPELINES_FOR_PROJECT | project_slug, branch |\n| List workflows | CIRCLECI_LIST_WORKFLOWS_BY_PIPELINE_ID | pipeline_id |\n| Get pipeline config | CIRCLECI_GET_PIPELINE_CONFIG | pipeline_id |\n| Get job details | CIRCLECI_GET_JOB_DETAILS | project_slug, job_number |\n| Get job artifacts | CIRCLECI_GET_JOB_ARTIFACTS | project_slug, job_number |\n| Get test metadata | CIRCLECI_GET_TEST_METADATA | project_slug, job_number |\n\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\n\n## Limitations\n- Use this skill only when the task clearly matches the scope described above.\n- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.\n- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.\n","","imported","https:\u002F\u002Fgithub.com\u002Fsickn33\u002Fantigravity-awesome-skills","user_system_seed","SkillOPIC",true,226,1283,"2026-05-16 13:10:36",{"id":8,"name":21,"slug":22,"icon":23,"description":24,"sort":25,"createdAt":26},"效率工具","productivity","mdi-lightning-bolt-outline","文档处理、数据分析、自动化工作流",4,"2026-05-16 12:53:40",{"id":7,"name":28,"slug":29,"icon":30,"description":31,"moduleId":8,"sort":32,"skillCount":33,"createdAt":26},"自动化","automation","mdi-robot-outline","工作流自动化、批处理",3,101,[35],{"id":36,"skillId":4,"version":37,"fileName":38,"fileSize":39,"filePath":40,"fileHash":41,"manifest":42,"createdAt":19},"2a877f67-a711-4b4f-bb4a-7c80cd7421db","1.0.0","circleci-automation.zip",2896,"uploads\u002Fskills\u002Fbda423c2-f210-4b5f-b8d9-c1cc8f7e3bc9\u002Fcircleci-automation.zip","c8f6756c8c65f11240e1c7649eec4fc834775d9bbc4b5045f0261c4b0b6d27c1","[{\"path\":\"SKILL.md\",\"isDirectory\":false,\"size\":7084}]",{"code":44,"message":45,"data":46},200,"success",{"items":47,"stats":48,"page":51},[],{"averageRating":49,"totalRatings":49,"ratingCounts":50},0,[49,49,49,49,49],{"limit":52,"offset":49,"hasMore":53,"nextOffset":52,"ratedOnly":16},15,false]