Skills circleci-automation
📦

circleci-automation

Safe 🌐 Network access

Automate CircleCI pipelines and workflows

Streamline your CI/CD operations by triggering CircleCI pipelines, monitoring workflow status, and retrieving build artifacts through natural language. Eliminate manual dashboard navigation and accelerate your development feedback loop.

Supports: Claude Codex Code(CC)
📊 71 Adequate
1

Download the skill ZIP

2

Upload in Claude

Go to Settings → Capabilities → Skills → Upload skill

3

Toggle on and start using

Test it

Using "circleci-automation". Trigger a pipeline for gh/myorg/myrepo on the develop branch

Expected outcome:

Pipeline triggered successfully. Pipeline ID: 5034460f-c7c4-4c43-9457-de07e2029e7b. The workflow is now running. You can monitor its progress by asking me to check the workflow status.

Using "circleci-automation". What is the status of pipeline 5034460f-c7c4-4c43-9457-de07e2029e7b?

Expected outcome:

Pipeline status: Running. Contains 2 workflows: build (running) and deploy (pending). The build workflow has 3 jobs: test (success), lint (running), security-scan (pending).

Using "circleci-automation". Get artifacts from job 123

Expected outcome:

Job 123 produced 5 artifacts: coverage-report.html (2.3 MB), test-results.xml (156 KB), build.log (45 KB), app-binary.zip (12 MB), documentation.pdf (1.8 MB). All artifacts are available for download.

Security Audit

Safe
v1 • 2/25/2026

Static analysis detected 64 patterns but all are false positives. The SKILL.md file is Markdown documentation, not executable code. Backtick patterns are code formatting syntax, not Ruby execution. The network reference is a legitimate MCP endpoint configuration. No security concerns identified after manual review.

1
Files scanned
183
Lines analyzed
1
findings
1
Total audits

Risk Factors

🌐 Network access (1)
SKILL.md:22
Audited by: claude

Quality Score

38
Architecture
100
Maintainability
87
Content
32
Community
100
Security
91
Spec Compliance

What You Can Build

CI/CD Pipeline Management

Trigger new pipeline runs when code changes are pushed, monitor execution progress, and receive notifications when workflows complete or fail.

Build Debugging and Analysis

Investigate failed builds by retrieving job logs, examining test failure details, and downloading artifacts for local analysis.

Release Automation

Automate release pipeline triggering with specific parameters, track deployment workflows, and collect build artifacts for distribution.

Try These Prompts

Basic Pipeline Trigger 
Trigger a CircleCI pipeline for the repository gh/myorg/myrepo on the main branch.
Workflow Status Check 
Check the status of all workflows for the most recent pipeline of gh/myorg/myrepo and tell me which jobs have failed.
Artifact Retrieval 
Get the list of artifacts produced by job number 123 in gh/myorg/myrepo and provide the download URLs for any PDF files.
Test Results Analysis 
Retrieve test metadata for job 456 in gh/myorg/myrepo, summarize the test results, and list all failed tests with their error messages.

Best Practices

  • Always search for available tools using RUBE_SEARCH_TOOLS before executing any CircleCI operations to ensure you have current schemas.
  • Use pagination tokens when retrieving large result sets to avoid missing data from API responses.
  • Verify job completion status before attempting to retrieve artifacts or test metadata to ensure data is available.

Avoid

  • Do not rapidly poll workflow status in quick succession. Use 5-10 second intervals to respect API rate limits.
  • Do not provide both branch and tag parameters when triggering a pipeline. They are mutually exclusive and will cause an error.
  • Do not assume job numbers are UUIDs. Job numbers are integers, unlike pipeline and workflow IDs which are UUIDs.

Frequently Asked Questions

What do I need before using this skill?
You need Rube MCP configured in your client and an active CircleCI connection. Use RUBE_MANAGE_CONNECTIONS with toolkit 'circleci' to authenticate if not already connected.
What is the correct format for project slugs?
Project slugs must include the VCS prefix: 'gh/org/repo' for GitHub repositories or 'bb/org/repo' for Bitbucket. Organization and repository names are case-sensitive.
Why can't I retrieve test results for a job?
Test metadata is only available if the job uploaded JUnit XML format results. If no test results were uploaded during job execution, the response will be empty.
What is the difference between pipeline IDs, workflow IDs, and job numbers?
Pipeline IDs and workflow IDs are UUIDs (e.g., 5034460f-c7c4-4c43-9457-de07e2029e7b). Job numbers are integers (e.g., 123). Use the correct format for each API endpoint.
How do I handle paginated responses?
Check API responses for a 'next_page_token' field. Pass this token as the 'page_token' parameter in your next request. Continue until the token is absent or null.
Can this skill modify CircleCI configuration files?
No. This skill can only read data and trigger pipelines through the CircleCI API. It cannot create, edit, or delete .circleci/config.yml files or other repository content.

Developer Details

Author

sickn33

License

MIT

Repository

https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/circleci-automation

Ref

main

File structure

📄 SKILL.md