Agent Skills
› openai/plugins
› circleci-cli
circleci-cli
GitHub通过 CircleCI CLI 执行认证、状态检查、配置验证、流水线重跑与触发等操作。遵循先只读诊断后安全变更的原则，确保权限合规并保护敏感信息。
Trigger Scenarios
用户需要检查 CI/CD 流水线或作业状态
用户请求本地验证 CircleCI 配置文件
用户要求重新运行或触发特定的流水线任务
用户询问如何配置或排查 CLI 认证问题
Install
npx skills add openai/plugins --skill circleci-cli -g -y
SKILL.md
Frontmatter
{
"name": "circleci-cli",
"description": "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
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
circleciis installed and version is available. - Confirm token/auth before issuing remote CircleCI commands.
- Confirm
- 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 unlesscircleci helpconfirms 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|runandcircleci 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.
Version History
- 11c74d6 Current 2026-07-19 09:31
