circleci-automation — Claude Code skill: run pipelines and monitor jobs
circleci-automation is a Claude Code skill for CircleCI via Rube MCP: trigger pipelines, check workflow and job status, and download artifacts and test results. Requires an active CircleCI connection via Composio.
MIT 122 installs ★ 3,785 updated 2026-10-25
npx skills add davepoon/buildwithclaude --skill circleci-automation -a claude-codeWhat circleci-automation does
This skill exposes CircleCI's toolkit via Rube MCP, letting you automate CI/CD tasks from your code editor. You can start a new pipeline on a branch or tag, list recent pipelines, drill into workflows and jobs, retrieve execution details, fetch artifacts, and review test outcomes.
Setup requires Rube MCP connected (endpoint https://rube.app/mcp in your client config) and CircleCI authenticated through RUBE_MANAGE_CONNECTIONS. The skill calls Composio tools like CIRCLECI_TRIGGER_PIPELINE, CIRCLECI_LIST_PIPELINES_FOR_PROJECT, CIRCLECI_LIST_WORKFLOWS_BY_PIPELINE_ID, CIRCLECI_GET_JOB_DETAILS, CIRCLECI_GET_JOB_ARTIFACTS, and CIRCLECI_GET_TEST_METADATA. Key details: projects use slugs like gh/org/repo (GitHub) or bb/org/repo (Bitbucket); branch and tag are mutually exclusive; job IDs are integers, while pipeline and workflow IDs are UUIDs.
CircleCI API rate limits apply; use 5–10 second intervals between requests to avoid throttling. Artifacts only appear after job completion, and test metadata requires the job to have uploaded JUnit XML results.
What it helps with
- trigger a pipeline on a branch or tag with parameters
- fetch the status and list workflows in a pipeline
- check job execution time and test results
- download build artifacts from a completed job
- review test failures and error messages
Example prompts for the agent
- Trigger the pipeline on
mainwithDEPLOY_ENV=staging - List the latest pipelines for
gh/myorg/myrepoand their status - Get details for job 456 and retrieve artifacts if the build passed
How to install circleci-automation
1Skills CLI (Vercel)
npx skills add davepoon/buildwithclaude --skill circleci-automation -a claude-code2Manually: put the files in place
~/.claude/skills/circleci-automation/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/circleci-automation/
1Skills CLI (Vercel)
npx skills add davepoon/buildwithclaude --skill circleci-automation -a codex2Manually: put the files in place
.agents/skills/circleci-automation/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add davepoon/buildwithclaude --skill circleci-automation -a cursor2Manually: put the files in place
.cursor/skills/circleci-automation/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install davepoon/buildwithclaude plugins/all-skills/skills/circleci-automation2Manually: put the files in place
.github/skills/circleci-automation/SKILL.md1Skills CLI (Vercel)
npx skills add davepoon/buildwithclaude --skill circleci-automation -a gemini-cli2Platform CLI
gemini skills install https://github.com/davepoon/buildwithclaude --path plugins/all-skills/skills/circleci-automationManually: put the files in place
.devin/skills/circleci-automation/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add davepoon/buildwithclaude --skill circleci-automation -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about circleci-automation
How do I install circleci-automation for Claude Code?
Run npx skills add davepoon/buildwithclaude --skill circleci-automation -a claude-code in your terminal, then open ~/.claude/skills/circleci-automation/SKILL.md and follow the steps. Verify Rube MCP is connected and CircleCI is authorized.
What does circleci-automation do?
It connects you to CircleCI's API via Rube MCP, so you can trigger pipelines, track workflow and job progress, fetch execution details, download build artifacts, and check test results.
What is the correct project_slug format?
The slug must include the VCS prefix: gh/org/repo for GitHub or bb/org/repo for Bitbucket. Organization and repository names are case-sensitive; a malformed slug will return a 404 error.
Source text
SKILL.md · MIT
---
name: 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](https://composio.dev/toolkits/circleci)
## Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active CircleCI connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `circleci`
- Always call `RUBE_SEARCH_TOOLS` first 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.
1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `circleci`
3. If connection is not ACTIVE, follow the returned auth link to complete CircleCI authentication
4. 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**:
1. `CIRCLECI_TRIGGER_PIPELINE` - Trigger a new pipeline on a project [Required]
2. `CIRCLECI_LIST_WORKFLOWS_BY_PIPELINE_ID` - Monitor resulting workflows [Optional]
**Key parameters**:
- `project_slug`: Project identifier in format `gh/org/repo` or `bb/org/repo`
- `branch`: Git branch to run the pipeline on
- `tag`: Git tag to run the pipeline on (mutually exclusive with branch)
- `parameters`: Pipeline parameter key-value pairs
**Pitfalls**:
- `project_slug` format is `{vcs}/{org}/{repo}` (e.g., `gh/myorg/myrepo`)
- `branch` and `tag` are 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**:
1. `CIRCLECI_LIST_PIPELINES_FOR_PROJECT` - List recent pipelines for a project [Required]
2. `CIRCLECI_LIST_WORKFLOWS_BY_PIPELINE_ID` - List workflows within a pipeline [Required]
3. `CIRCLECI_GET_PIPELINE_CONFIG` - View the pipeline configuration used [Optional]
**Key parameters**:
- `project_slug`: Project identifier in `{vcs}/{org}/{repo}` format
- `pipeline_id`: UUID of a specific pipeline
- `branch`: Filter pipelines by branch name
- `page_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_token` is 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**:
1. `CIRCLECI_LIST_WORKFLOWS_BY_PIPELINE_ID` - Find workflow containing the job [Prerequisite]
2. `CIRCLECI_GET_JOB_DETAILS` - Get detailed job information [Required]
**Key parameters**:
- `project_slug`: Project identifier
- `job_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**:
1. `CIRCLECI_GET_JOB_DETAILS` - Confirm job completed successfully [Prerequisite]
2. `CIRCLECI_GET_JOB_ARTIFACTS` - List all artifacts from the job [Required]
**Key parameters**:
- `project_slug`: Project identifier
- `job_number`: Numeric job number
**Pitfalls**:
- Artifacts are only available after job completion
- Each artifact has a `path` and `url` for 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**:
1. `CIRCLECI_GET_JOB_DETAILS` - Verify job ran tests [Prerequisite]
2. `CIRCLECI_GET_TEST_METADATA` - Retrieve test results and metadata [Required]
**Key parameters**:
- `project_slug`: Project identifier
- `job_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 `message` field
## 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_token` field
- Pass token as `page_token` in next request
- Continue until `next_page_token` is 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](https://composio.dev)*
© davepoon · MIT · davepoon/buildwithclaude