CircleCI agent skills for Claude Code, Cursor and RevampKey

6 ready-made playbooks that teach an AI agent how to do real CircleCI work: which tools to call, what to check first, and when to stop and ask you.

Download RevampKey, free I have it: connect CircleCI

Connect CircleCI once and all 6 skills install themselves and stay up to date. Mac, Windows and Linux.

All 6 CircleCI skills

Each skill is one job. You ask in plain words and the agent loads the skill that matches, then follows its steps.

Start hereAsks before writing21 CircleCI tools

Use CircleCI with AI safely

Sets the ground rules for working with CircleCI from an AI assistant: confirm the org and project first, pick the right tool for runs, workflows, jobs and logs, and ask before any rerun, cancel or rollback.

Use it when

You have just connected CircleCI and want to know what the assistant can do
You are not sure which CircleCI tool fits your question
You want the assistant to rerun or cancel something and need the approval rules

Tools it uses

get_me
list_runs
get_run
list_run_workflows
get_workflow
list_workflow_jobs
get_job
get_job_logs
list_job_artifacts
list_job_tests
get_job_resource_usage
validate_config
get_orb
get_orb_source
list_deployments
list_deploy_environments
list_deploy_components
download_usage_data
rerun_workflow
cancel_workflow
rollback_deploy_component

Example

Show me the last five runs on main for gh/acme/payments and tell me which failed.

Confirmed the account as acme-ci and the project as gh/acme/payments. Of the last 5 runs on main, 4 succeeded and 1 failed. The failed run's build-and-test workflow failed in job unit-tests at step 3 with exit code 1. I have not rerun anything; say the word if you want a failed-only rerun.

Use in RevampKeyRead the full skill →

Read-only8 CircleCI tools

Diagnose a failed CircleCI run with AI

Walks back from a failed CircleCI workflow to the first real failing step and separates code bugs from flaky tests and infrastructure problems. It checks run history before naming a cause and does not rerun anything without asking.

Use it when

A pipeline turned red and the last log line does not explain why
You need to know whether a failure is a real regression or a flaky test
A build failed on one branch but was green on the default branch

Tools it uses

list_runs
get_run
get_workflow
get_job
get_job_logs
list_job_tests
list_job_artifacts
rerun_workflow

Example

Why did the last run on my feature branch fail? Is it my change or something flaky?

The first failing job is integration-tests, step "run api tests", exit 1. The decisive log line is a timeout connecting to the staging database, and the same job was green on the previous two runs. The commit range adds no database code, so this looks like infrastructure, not your change. Retrying is reasonable. I have not rerun the workflow; say the word if you want that.

Use in RevampKeyRead the full skill →

Asks before writing10 CircleCI tools

Check a CircleCI deploy before you roll it back

Works out which version is live, what it replaced and whether the previous build is healthy, then asks for your explicit yes before any rollback runs.

Use it when

A deploy went out and errors started right after it
You want to know which version is live in production
You need to roll a component back to its last good version

Tools it uses

get_deploy_environment
list_deploy_environments
list_deploy_components
get_deploy_component
list_deployments
list_deploy_component_versions
get_run
list_run_workflows
get_job_logs
rollback_deploy_component

Example

Should we roll back the checkout component in production? Errors started after the 3pm deploy.

The live checkout version is 2.14.3, deployed at 15:02 by the main-branch workflow. It replaced 2.14.1, which ran cleanly for about 9 hours. The 2.14.2 build failed its integration job, so it never went live. I'd recommend rolling back to 2.14.1. Reply yes to proceed.

Use in RevampKeyRead the full skill →

Read-only5 CircleCI tools

Review CircleCI pipeline health with AI

Reviews recent CircleCI runs on a branch or project to measure failure rate, duration and repeated failures, then ranks the bottleneck and the fix with the best payback. It reports trends across runs and does not change anything in your CI.

Use it when

A team asks why CI feels slow this month
You want to know which job costs the most time across a week of runs
Failures keep returning and you need to see which ones repeat

Tools it uses

list_runs
get_run
list_run_workflows
list_workflow_jobs
list_job_tests

Example

How healthy is our CI on main over the last two weeks, and what should we fix first?

Over the last 30 completed runs on main, the failure rate is 17%, median duration is 14 minutes and p90 is 31 minutes, with the tail getting worse since Tuesday. The integration-tests job takes 41% of consumed minutes and runs on docs-only commits too. Top recommendation: skip it for paths that do not touch the app, which removes about 90 minutes a week. Two failures repeat in the same test, so they look like a real defect rather than flakiness.

Use in RevampKeyRead the full skill →

Asks before writing7 CircleCI tools

Rerun a failed CircleCI workflow, safely

Decides whether a failed or stuck CircleCI workflow is worth rerunning, and whether to rerun only the failed jobs or everything. It checks state and history first and asks before rerunning or cancelling.

Use it when

A workflow failed on a transient-looking error and you want to retry it
A run has been stuck with no progress and you need to cancel and restart it
You are unsure whether a rerun will just fail again

Tools it uses

list_runs
list_run_workflows
get_workflow
list_workflow_jobs
cancel_workflow
get_run
rerun_workflow

Example

The workflow for my feature branch failed in the integration job. Should I rerun it?

The integration job failed with a runner timeout, and the same branch passed on its last two runs, so this looks transient. I recommend rerunning only the 2 failed jobs and their downstream jobs, not from the start. Nothing has been rerun yet. Shall I rerun it in failed-only mode?

Use in RevampKeyRead the full skill →

Read-only4 CircleCI tools

Triage CircleCI test failures

Turns the failing tests in a CircleCI job into a ranked list: new failures that block the branch, probably flaky tests, skipped-test drift and pre-existing debt. It asks before changing any test or project settings.

Use it when

A job is red and you want to know which tests broke because of your change
A test keeps failing intermittently and you need to know if it is flaky
Test counts dropped after a merge and you want to check for silently skipped tests

Tools it uses

list_workflow_jobs
get_job
list_runs
list_job_tests

Example

Which tests failed in the last build on my feature branch, and which of them are new?

The job failed 6 of 412 tests, with 3 skipped that ran on main last week. Two failures are new and block the merge: test checkout_applies_discount broke in the pricing change, and test order_export_csv fails on a missing column. Three failures already fail on main, so they are not from this change. One test, login_redirects_after_timeout, passed on its last two reruns and looks flaky.

Use in RevampKeyRead the full skill →

Get all 6 without copying a file

RevampKey adds the skills when you connect CircleCI, updates them for you and removes them when you disconnect.

Download RevampKey

How CircleCI skills work

Connect CircleCI
The CircleCI MCP server gives the agent its tools.
Ask in plain words
“Why did the last run on my feature branch fail? Is it my change or something flaky?” Each SKILL.md says when it applies, so only the one that fits is loaded.
Approve any change
The agent calls the tools in order, checks its work, and shows you any change before it makes it.

How to install CircleCI skills

In RevampKey the skills install themselves when you connect CircleCI. In other tools each skill is one folder with a SKILL.md file, and you also need the CircleCI MCP server connected there.

About 1 minute · nothing to copy

Download RevampKey for Mac, Windows or Linux and sign in.
Open Connectors and connect CircleCI. All 6 skills come with it and stay up to date; they go away when you remove the connector.
Ask in plain language, for example “Why did the last run on my feature branch fail? Is it my change or something flaky?”
Download RevampKeyConnect CircleCI · 1 click
Get RevampKey to connect CircleCI
RevampKey is a free desktop app for Mac, Windows and Linux. Install it, sign in, and CircleCI is one click away with its skills already attached.
Download RevampKey
Not now? Use the skills in your current tool
for s in essentials ci-failure-diagnosis deploy-rollback-check pipeline-health-review rerun-failed-workflow test-failure-triage; do curl -fsSL --create-dirs -o .claude/skills/circleci-$s/SKILL.md https://revampkey.com/marketplace/circleci/skills/$s/SKILL.md done
Other tools

Into this project’s .claude/skills folder

Connect the CircleCI MCP server in Claude Code.

Run this in your project folder to add all 6 skills:

for s in essentials ci-failure-diagnosis deploy-rollback-check pipeline-health-review rerun-failed-workflow test-failure-triage; do
  curl -fsSL --create-dirs -o .claude/skills/circleci-$s/SKILL.md https://revampkey.com/marketplace/circleci/skills/$s/SKILL.md
done

Ask in plain language, for example “Why did the last run on my feature branch fail? Is it my change or something flaky?”

Into the shared .agents/skills folder

Connect the CircleCI MCP server in Cursor.

Run this in your project folder to add all 6 skills:

for s in essentials ci-failure-diagnosis deploy-rollback-check pipeline-health-review rerun-failed-workflow test-failure-triage; do
  curl -fsSL --create-dirs -o .agents/skills/circleci-$s/SKILL.md https://revampkey.com/marketplace/circleci/skills/$s/SKILL.md
done

Ask in plain language, for example “Why did the last run on my feature branch fail? Is it my change or something flaky?”

Into the shared .agents/skills folder

Connect the CircleCI MCP server in Codex.

Run this in your project folder to add all 6 skills:

for s in essentials ci-failure-diagnosis deploy-rollback-check pipeline-health-review rerun-failed-workflow test-failure-triage; do
  curl -fsSL --create-dirs -o .agents/skills/circleci-$s/SKILL.md https://revampkey.com/marketplace/circleci/skills/$s/SKILL.md
done

Ask in plain language, for example “Why did the last run on my feature branch fail? Is it my change or something flaky?”

Into the shared .agents/skills folder

Connect the CircleCI MCP server in VS Code.

Run this in your project folder to add all 6 skills:

for s in essentials ci-failure-diagnosis deploy-rollback-check pipeline-health-review rerun-failed-workflow test-failure-triage; do
  curl -fsSL --create-dirs -o .agents/skills/circleci-$s/SKILL.md https://revampkey.com/marketplace/circleci/skills/$s/SKILL.md
done

Ask in plain language, for example “Why did the last run on my feature branch fail? Is it my change or something flaky?”

RevampKey or copy the files?

In RevampKey

One click when you connect CircleCI
Updated for you when a skill improves
Removed when you disconnect
The MCP server is set up for you
800+ other connectors, same way

Download free

Copy into your project

One command per project
Run it again to get updates
You connect the CircleCI MCP server yourself
Works in Claude Code, Cursor, Codex and VS Code

See the command

CircleCI skills FAQ

What is a CircleCI agent skill?

A SKILL.md file: a short playbook an AI agent loads when your request matches it. Each CircleCI skill describes one job, which CircleCI tools to use in which order, what to check first and when to stop and ask you.

Do the CircleCI skills change anything on their own?

3 of the 6 only read. The others tell the agent to show you the change and wait for a yes before it creates, edits or deletes anything in CircleCI.

Which tools can use these skills?

Any agent that reads the open Agent Skills format: Claude Code, Cursor, Codex, VS Code with Copilot and RevampKey. In RevampKey they are attached when you connect CircleCI; elsewhere you copy the folders into your project or skills directory.

Do I need the CircleCI MCP server too?

Yes. The skills tell the agent how to do the work; the CircleCI MCP server gives it the tools to do it. The CircleCI MCP setup guide covers every client.

CircleCI MCP server setup · This page as Markdown

Put CircleCI’s best workflows in your agent

Download RevampKey, connect CircleCI and ask your first question in about a minute.

Download RevampKey Connect CircleCI · 1 click

All 6 CircleCI skills

Use CircleCI with AI safely

Use it when

Tools it uses

Diagnose a failed CircleCI run with AI

Use it when

Tools it uses

Check a CircleCI deploy before you roll it back

Use it when

Tools it uses

Review CircleCI pipeline health with AI

Use it when

Tools it uses

Rerun a failed CircleCI workflow, safely

Use it when

Tools it uses

Triage CircleCI test failures

Use it when

Tools it uses

Get all 6 without copying a file

How CircleCI skills work

How to install CircleCI skills

RevampKey or copy the files?

In RevampKey

Copy into your project

CircleCI skills FAQ

Put CircleCI’s best workflows in your agent

Skills for related tools