How do I install the Circleci CLI skill?

Run npx skillmds@latest add concertonotes/circleci-cli in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Circleci CLI safe to use?

SkillMD's automated safety review verdict for this skill is PASS. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Circleci CLI?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Circleci CLI free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Circleci CLI?

ConcertoNotes (@concertonotes) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Circleci CLI by concertonotes — Agent Skill

Name: Circleci CLI
Rating: 4.666666666666667 (3 reviews)
Author: ConcertoNotes

Circleci CLI

Operate and troubleshoot CircleCI using the CircleCI CLI. Use when users ask to authenticate CLI access, inspect pipeline/workflow/job status, validate configuration locally, rerun pipelines/jobs, trigger pipelines, or gather actionable diagnostics from CLI outputs.

ConcertoNotes Updated Aug 19, 2026 0 repo stars

File contents

CircleCI CLI

Overview

Use this skill when the fastest path is CircleCI CLI-driven operations rather than editing config first. Prioritize safe, read-first diagnostics, then run targeted mutating commands only after confirming scope.

Inputs To Gather

Repository path and target branch
CircleCI project slug (if needed)
Whether objective is inspect, rerun, trigger, or validate
Required token/auth state and org permissions

Workflow

Verify CLI and auth state.
- Confirm circleci is installed and version is available.
- Confirm token/auth before issuing remote CircleCI commands.
Run read-only diagnostics first.
- Inspect available pipeline/project/trigger state and capture concrete identifiers.
- Extract first failing scope and step details from supported command output before rerun/trigger actions.
Validate config locally when relevant.
- Run config validation/processing commands before committing risky edits.
Run targeted mutation commands.
- Rerun only required workflow/job scope.
- Trigger pipelines with explicit parameters and branch context.
Report results and next action.
- Provide exact command results, remaining blockers, and safest follow-up.

Guardrails

Prefer read-only commands before rerun/trigger/cancel operations.
Confirm organization/project scope before mutating pipeline state.
Never print raw secret values from environment variables or tokens.
If permissions fail, report exact auth/scope gap and safest remediation.
Respect installed CLI capabilities and avoid inventing commands.
Do not use circleci api, circleci workflow, or other unavailable legacy commands unless circleci help confirms they exist.

Installed CLI Compatibility

For newer circleci builds that expose domain subcommands (for example pipeline, project, trigger) but not api:

Verify available commands first with circleci help.
Use only discovered subcommands from help output.
Prefer circleci pipeline list|create|run and circleci trigger ... for pipeline operations.
For cloud job logs, use supported platform tools (CircleCI app/UI or connected CircleCI MCP tooling) if the CLI does not expose a logs command.

Output Contract

Provide:

Commands run and purpose.
Key outputs (pipeline/workflow/job ids, status, failing step).
Actions taken (rerun/trigger/validate) and why.
Remaining blockers and next recommended CLI command.

---name: circleci-clidescription: Operate and troubleshoot CircleCI using the CircleCI CLI. Use when users ask to authenticate CLI access, inspect pipeline/workflow/job status, validate configuration locally, rerun pipelines/jobs, trigger pipelines, or gather actionable diagnostics from CLI outputs.---# CircleCI CLI## OverviewUse this skill when the fastest path is CircleCI CLI-driven operations rather than editing config first. Prioritize safe, read-first diagnostics, then run targeted mutating commands only after confirming scope.## Inputs To Gather- Repository path and target branch- CircleCI project slug (if needed)- Whether objective is inspect, rerun, trigger, or validate- Required token/auth state and org permissions## Workflow1. Verify CLI and auth state. - Confirm `circleci` is installed and version is available. - Confirm token/auth before issuing remote CircleCI commands.2. Run read-only diagnostics first. - Inspect available pipeline/project/trigger state and capture concrete identifiers. - Extract first failing scope and step details from supported command output before rerun/trigger actions.3. Validate config locally when relevant. - Run config validation/processing commands before committing risky edits.4. Run targeted mutation commands. - Rerun only required workflow/job scope. - Trigger pipelines with explicit parameters and branch context.5. Report results and next action. - Provide exact command results, remaining blockers, and safest follow-up.## Guardrails- Prefer read-only commands before rerun/trigger/cancel operations.- Confirm organization/project scope before mutating pipeline state.- Never print raw secret values from environment variables or tokens.- If permissions fail, report exact auth/scope gap and safest remediation.- Respect installed CLI capabilities and avoid inventing commands.- Do not use `circleci api`, `circleci workflow`, or other unavailable legacy commands unless `circleci help` confirms they exist.## Installed CLI CompatibilityFor newer `circleci` builds that expose domain subcommands (for example `pipeline`, `project`, `trigger`) but not `api`:- Verify available commands first with `circleci help`.- Use only discovered subcommands from help output.- Prefer `circleci pipeline list|create|run` and `circleci trigger ...` for pipeline operations.- For cloud job logs, use supported platform tools (CircleCI app/UI or connected CircleCI MCP tooling) if the CLI does not expose a logs command.## Output ContractProvide:1. Commands run and purpose.2. Key outputs (pipeline/workflow/job ids, status, failing step).3. Actions taken (rerun/trigger/validate) and why.4. Remaining blockers and next recommended CLI command.

Frequently asked questions