Labsco
openai logo

circleci-cli

✓ Official★ 4,081

by openai · part of openai/plugins

Drives a project's CircleCI builds from the command line — what a pipeline or job is doing, whether a configuration change is valid before you commit it, and rerunning only the part that failed. It reads before it changes anything.

🧩 One of 7 skills in the openai/plugins package — works on its own, and pairs well with its siblings.

This is the playbook your agent receives when the skill activates — you don't need to read it to use the skill, but it's here to audit before installing.

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

  1. 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.

Output Contract

Provide:

  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.