circleci-automation
Automate CircleCI tasks via Rube MCP (Composio): trigger pipelines, monitor workflows/jobs, retrieve artifacts and test metadata. Always search tools first for current schemas.
Install / Use
npx skills add davepoon/buildwithclaude --skill circleci-automationInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
AutomationSupported Platforms
Our assessment of circleci-automation
circleci-automation scores 92/100 on our quality scale, 796th of 2,790 Automation skills we index (top 29%).
Its SKILL.md is 6.6 KB long, well organised into 15 sections with 2 code examples: a thorough specification that gives an agent plenty to work with.
With 3,752 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated today, so circleci-automation is actively maintained.
- Our last check on 2026-10-27 found the source still online.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-10-02. Automated pattern scan on 2026-10-02. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
circleci-automation compared with similar skills
All 4 of these similar skills score higher than circleci-automation; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| circleci-automation (this skill)by davepoon | 92 | 3.8k | today | SKILL.md |
| Agent-Reachby Panniantong | 100 | 112.3k | 8d ago | CLAUDE.md |
| rufloby ruvnet | 100 | 81.9k | today | CLAUDE.md |
| headroomby headroomlabs-ai | 100 | 79.8k | today | CLAUDE.md |
| CowAgentby zhayujie | 100 | 48.0k | today | CLAUDE.md |
Frequently asked questions
- How do I install circleci-automation?
- Run
npx skills add davepoon/buildwithclaude --skill circleci-automation. The install tabs above show the steps for each supported agent. - Which AI agents does circleci-automation work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is circleci-automation safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is circleci-automation still maintained?
- The repository was last updated today, so circleci-automation is actively maintained.
Skill content
View source on GitHubname: circleci-automation description: "Automate CircleCI tasks via Rube MCP (Composio): trigger pipelines, monitor workflows/jobs, retrieve artifacts and test metadata. Always search tools first for current schemas." requires: mcp: [rube] category: devops
CircleCI Automation via Rube MCP
Automate CircleCI CI/CD operations through Composio's CircleCI toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/circleci
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active CircleCI connection via
RUBE_MANAGE_CONNECTIONSwith toolkitcircleci - Always call
RUBE_SEARCH_TOOLSfirst to get current tool schemas
Setup
Get Rube MCP: Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
- Verify Rube MCP is available by confirming
RUBE_SEARCH_TOOLSresponds - Call
RUBE_MANAGE_CONNECTIONSwith toolkitcircleci - If connection is not ACTIVE, follow the returned auth link to complete CircleCI authentication
- Confirm connection status shows ACTIVE before running any workflows
Core Workflows
1. Trigger a Pipeline
When to use: User wants to start a new CI/CD pipeline run
Tool sequence:
CIRCLECI_TRIGGER_PIPELINE- Trigger a new pipeline on a project [Required]CIRCLECI_LIST_WORKFLOWS_BY_PIPELINE_ID- Monitor resulting workflows [Optional]
Key parameters:
project_slug: Project identifier in formatgh/org/repoorbb/org/repobranch: Git branch to run the pipeline ontag: Git tag to run the pipeline on (mutually exclusive with branch)parameters: Pipeline parameter key-value pairs
Pitfalls:
project_slugformat is{vcs}/{org}/{repo}(e.g.,gh/myorg/myrepo)branchandtagare mutually exclusive; providing both causes an error- Pipeline parameters must match those defined in
.circleci/config.yml - Triggering returns a pipeline ID; workflows start asynchronously
2. Monitor Pipelines and Workflows
When to use: User wants to check the status of pipelines or workflows
Tool sequence:
CIRCLECI_LIST_PIPELINES_FOR_PROJECT- List recent pipelines for a project [Required]CIRCLECI_LIST_WORKFLOWS_BY_PIPELINE_ID- List workflows within a pipeline [Required]CIRCLECI_GET_PIPELINE_CONFIG- View the pipeline configuration used [Optional]
Key parameters:
project_slug: Project identifier in{vcs}/{org}/{repo}formatpipeline_id: UUID of a specific pipelinebranch: Filter pipelines by branch namepage_token: Pagination cursor for next page of results
Pitfalls:
- Pipeline IDs are UUIDs, not numeric IDs
- Workflows inherit the pipeline ID; a single pipeline can have multiple workflows
- Workflow states include: success, running, not_run, failed, error, failing, on_hold, canceled, unauthorized
page_tokenis returned in responses for pagination; continue until absent
3. Inspect Job Details
When to use: User wants to drill into a specific job's execution details
Tool sequence:
CIRCLECI_LIST_WORKFLOWS_BY_PIPELINE_ID- Find workflow containing the job [Prerequisite]CIRCLECI_GET_JOB_DETAILS- Get detailed job information [Required]
Key parameters:
project_slug: Project identifierjob_number: Numeric job number (not UUID)
Pitfalls:
- Job numbers are integers, not UUIDs (unlike pipeline and workflow IDs)
- Job details include executor type, parallelism, start/stop times, and status
- Job statuses: success, running, not_run, failed, retried, timedout, infrastructure_fail, canceled
4. Retrieve Build Artifacts
When to use: User wants to download or list artifacts produced by a job
Tool sequence:
CIRCLECI_GET_JOB_DETAILS- Confirm job completed successfully [Prerequisite]CIRCLECI_GET_JOB_ARTIFACTS- List all artifacts from the job [Required]
Key parameters:
project_slug: Project identifierjob_number: Numeric job number
Pitfalls:
- Artifacts are only available after job completion
- Each artifact has a
pathandurlfor download - Artifact URLs may require authentication headers to download
- Large artifacts may have download size limits
5. Review Test Results
When to use: User wants to check test outcomes for a specific job
Tool sequence:
CIRCLECI_GET_JOB_DETAILS- Verify job ran tests [Prerequisite]CIRCLECI_GET_TEST_METADATA- Retrieve test results and metadata [Required]
Key parameters:
project_slug: Project identifierjob_number: Numeric job number
Pitfalls:
- Test metadata requires the job to have uploaded test results (JUnit XML format)
- If no test results were uploaded, the response will be empty
- Test metadata includes classname, name, result, message, and run_time fields
- Failed tests include failure messages in the
messagefield
Common Patterns
Project Slug Format
Format: {vcs_type}/{org_name}/{repo_name}
- GitHub: gh/myorg/myrepo
- Bitbucket: bb/myorg/myrepo
Pipeline -> Workflow -> Job Hierarchy
1. Call CIRCLECI_LIST_PIPELINES_FOR_PROJECT to get pipeline IDs
2. Call CIRCLECI_LIST_WORKFLOWS_BY_PIPELINE_ID with pipeline_id
3. Extract job numbers from workflow details
4. Call CIRCLECI_GET_JOB_DETAILS with job_number
Pagination
- Check response for
next_page_tokenfield - Pass token as
page_tokenin next request - Continue until
next_page_tokenis absent or null
Known Pitfalls
ID Formats:
- Pipeline IDs: UUIDs (e.g.,
5034460f-c7c4-4c43-9457-de07e2029e7b) - Workflow IDs: UUIDs
- Job numbers: Integers (e.g.,
123) - Do NOT mix up UUIDs and integers between different endpoints
Project Slugs:
- Must include VCS prefix:
gh/for GitHub,bb/for Bitbucket - Organization and repo names are case-sensitive
- Incorrect slug format causes 404 errors
Rate Limits:
- CircleCI API has per-endpoint rate limits
- Implement exponential backoff on 429 responses
- Avoid rapid polling; use reasonable intervals (5-10 seconds)
Quick Reference
| Task | Tool Slug | Key Params | |------|-----------|------------| | Trigger pipeline | CIRCLECI_TRIGGER_PIPELINE | project_slug, branch, parameters | | List pipelines | CIRCLECI_LIST_PIPELINES_FOR_PROJECT | project_slug, branch | | List workflows | CIRCLECI_LIST_WORKFLOWS_BY_PIPELINE_ID | pipeline_id | | Get pipeline config | CIRCLECI_GET_PIPELINE_CONFIG | pipeline_id | | Get job details | CIRCLECI_GET_JOB_DETAILS | project_slug, job_number | | Get job artifacts | CIRCLECI_GET_JOB_ARTIFACTS | project_slug, job_number | | Get test metadata | CIRCLECI_GET_TEST_METADATA | project_slug, job_number |
Powered by Composio
Related Skills
Agent-Reach
112.3kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
ruflo
81.9k🌊 The original agent harness. Deploy intelligent multi-player swarms, coordinate autonomous workflows, and build conversational AI systems. Features adaptive memory, self-learning intelligence, federation, vector RAG integration, and native Claude Code / Codex / Hermes and many more Integrated
headroom
79.8kCompress tool outputs, logs, files, and RAG chunks before they reach the LLM. 20% fewer tokens for coding agents, 60-95% fewer tokens for JSON, same answers. Library, proxy, MCP server.
CowAgent
48.0kOpen-source personal AI assistant & Agent Harness. Plans tasks, runs tools and skills, self-evolves with memory and knowledge. Multi-agent, multi-model, multi-channel. Lightweight, extensible, one-line install.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
