Update to CircleCI

{
  "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.",
  "included_files": [],
  "skill_md_contents": "---\nname: circleci-cli\ndescription: 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.\n---\n\n# CircleCI CLI\n\n## Overview\n\nUse 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.\n\n## Inputs To Gather\n\n- Repository path and target branch\n- CircleCI project slug (if needed)\n- Whether objective is inspect, rerun, trigger, or validate\n- Required token/auth state and org permissions\n\n## Workflow\n\n1. Verify CLI and auth state.\n   - Confirm `circleci` is installed and version is available.\n   - Confirm token/auth before issuing remote CircleCI commands.\n2. Run read-only diagnostics first.\n   - Inspect available pipeline/project/trigger state and capture concrete identifiers.\n   - Extract first failing scope and step details from supported command output before rerun/trigger actions.\n3. Validate config locally when relevant.\n   - Run config validation/processing commands before committing risky edits.\n4. Run targeted mutation commands.\n   - Rerun only required workflow/job scope.\n   - Trigger pipelines with explicit parameters and branch context.\n5. Report results and next action.\n   - Provide exact command results, remaining blockers, and safest follow-up.\n\n## Guardrails\n\n- Prefer read-only commands before rerun/trigger/cancel operations.\n- Confirm organization/project scope before mutating pipeline state.\n- Never print raw secret values from environment variables or tokens.\n- If permissions fail, report exact auth/scope gap and safest remediation.\n- Respect installed CLI capabilities and avoid inventing commands.\n- Do not use `circleci api`, `circleci workflow`, or other unavailable legacy commands unless `circleci help` confirms they exist.\n\n## Installed CLI Compatibility\n\nFor newer `circleci` builds that expose domain subcommands (for example `pipeline`, `project`, `trigger`) but not `api`:\n\n- Verify available commands first with `circleci help`.\n- Use only discovered subcommands from help output.\n- Prefer `circleci pipeline list|create|run` and `circleci trigger ...` for pipeline operations.\n- 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.\n\n## Output Contract\n\nProvide:\n\n1. Commands run and purpose.\n2. Key outputs (pipeline/workflow/job ids, status, failing step).\n3. Actions taken (rerun/trigger/validate) and why.\n4. Remaining blockers and next recommended CLI command.\n"
}