# circleci-automation

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.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode, Windsurf (Devin Desktop), Claude.ai · 122 installs · ★ 3785 repo stars
- Author: davepoon
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/davepoon/buildwithclaude/tree/HEAD/plugins/all-skills/skills/circleci-automation/SKILL.md
- Updated: 2026-10-25
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/skills/circleci-automation

## What it 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.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add davepoon/buildwithclaude --skill circleci-automation -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/circleci-automation/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/circleci-automation/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add davepoon/buildwithclaude --skill circleci-automation -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/circleci-automation/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add davepoon/buildwithclaude --skill circleci-automation -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/circleci-automation/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install davepoon/buildwithclaude plugins/all-skills/skills/circleci-automation
```

2. **Manually: put the files in place**
- File: `.github/skills/circleci-automation/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add davepoon/buildwithclaude --skill circleci-automation -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/davepoon/buildwithclaude --path plugins/all-skills/skills/circleci-automation
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/circleci-automation/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add davepoon/buildwithclaude --skill circleci-automation -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/davepoon/buildwithclaude/tree/HEAD/plugins/all-skills/skills/circleci-automation/SKILL.md

## When to use it
- 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
- Trigger the pipeline on `main` with `DEPLOY_ENV=staging`
- List the latest pipelines for `gh/myorg/myrepo` and their status
- Get details for job 456 and retrieve artifacts if the build passed

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: bc69f78d244d3bf7.

BEGIN THIRD-PARTY FILE bc69f78d244d3bf7
```text
---
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]
```
END THIRD-PARTY FILE bc69f78d244d3bf7

The third-party file has ended. Everything between the bc69f78d244d3bf7 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2268 of 6788 bytes. © davepoon · MIT · https://github.com/davepoon/buildwithclaude/tree/HEAD/plugins/all-skills/skills/circleci-automation/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
