circleci-automation

Automate CircleCI pipeline triggers, workflow listing, job inspection, and artifact retrieval via Rube MCP.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/dr-code/beacon --skill circleci-automation-dr-code
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: circleci-automation
Source: https://github.com/dr-code/beacon/tree/main/plugins/all-skills/skills/circleci-automation
Command: npx skills add https://github.com/dr-code/beacon --skill circleci-automation-dr-code

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the manual work of calling CircleCI endpoints by enabling automated triggering, monitoring, and inspection of pipelines, workflows, jobs, artifacts, and test metadata via Composio's Rube MCP.

Core Features & Use Cases

  • Trigger pipelines: Start CI runs for a given project slug on a branch or tag with parameter support.
  • Monitor pipelines & workflows: List recent pipelines, enumerate workflows for a pipeline, and report workflow and job statuses.
  • Inspect jobs and artifacts: Retrieve job details, download or list artifacts, and fetch test metadata (JUnit) for diagnosis and reporting.
  • Use Case: Trigger a branch build, poll the resulting workflows until completion, then collect artifacts and test failures for a release candidate.

Quick Start

Trigger the main pipeline on project gh/myorg/myrepo for branch develop using the CircleCI toolkit via Rube MCP.

Frequently Asked Questions about circleci-automation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate triggering CircleCI pipelines for a specific branch?

You can automate triggering CircleCI pipelines by providing a project slug, target branch, and optional parameters. The Skill initiates CI runs on GitHub or Bitbucket projects through the Rube MCP toolkit without manual endpoint calls.

Can I retrieve CircleCI artifacts and test metadata after a workflow completes?

Yes, retrieving CircleCI artifacts and test metadata is supported. The Skill fetches JUnit test results and lists or downloads artifacts for completed jobs, enabling direct pipeline diagnosis and release reporting.

Does CircleCI automation work with both GitHub and Bitbucket projects?

CircleCI automation works with both GitHub and Bitbucket projects. You identify your repository using a project slug input, which allows the Skill to trigger pipelines and monitor workflows across both platforms.

How do I monitor CircleCI workflow and job statuses programmatically?

To monitor CircleCI workflows programmatically, the Skill lists recent pipelines, enumerates workflows for each pipeline, and reports current job statuses. This allows continuous polling until your pipeline reaches completion.

Do I need a Rube MCP connection to automate CircleCI operations?

An active Rube MCP connection with the CircleCI toolkit is required to automate operations. This integration manages pipeline triggers, handles pagination, and applies rate-limit backoff for reliable API communication.

What are the limitations when automating CircleCI pipelines via Rube MCP?

Limitations include dependency on an active Rube MCP connection and CircleCI API rate limits. The Skill manages these constraints by applying automatic rate-limit backoff and handling pagination during workflow listing and artifact retrieval.