Circleci status
Shared AI agent skills
npx -y skills add flurdy/agent-skills --skill circleci-statusAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 6 stars6 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Check CircleCI build status and failed job logs for the current GitHub repository. Use when asked whether CircleCI is green, failing, pending, or when needing CircleCI job logs.
SKILL.md
3.0 KB, as published. Nobody here has run it
CircleCI Status
Check the latest CircleCI pipeline/workflow status for the current GitHub repository, with optional failed job logs.
Authentication
- Basic GitHub commit status/check-run summaries use
ghwhen authenticated. - CircleCI pipeline/workflow/job details use
CIRCLECI_TOKENwhen already set, otherwisesecret-api-key lookup circleci "$SECRET_API_KEY_PROJECT". - CircleCI project slug is derived from
origin:gh/{owner}/{repo}.
Store the token once and expose only its non-secret project selector:
secret-api-key store circleci flurdy
export SECRET_API_KEY_PROJECT=flurdy
Usage
/circleci-status # Summarise latest status for current branch/HEAD
/circleci-status logs # Show latest failed job logs for current branch
/circleci-status main # Summarise latest CircleCI pipeline for branch main
/circleci-status logs main
Instructions
Always run the helper scripts fresh; never reuse prior status output.
Status mode
For no argument, or an argument other than logs, run:
~/.agents/skills/circleci-status/scripts/status.sh {optional-branch-or-ref}
Render:
## CircleCI status — {repo} `{branch}`
- GitHub commit status: {state}
- GitHub check runs: {counts by conclusion/status}
- CircleCI: {workflow statuses or token-missing note}
If ---CIRCLECI-STATUS--- is NO_TOKEN, say:
CircleCI API details unavailable: configure
SECRET_API_KEY_PROJECTand its CircleCI key. GitHub commit/check status above may still show CircleCI's reported state.
If GitHub status includes CircleCI contexts with target_url, include links for failing/pending contexts.
Logs mode
For logs as the first argument, run:
~/.agents/skills/circleci-status/scripts/logs.sh {optional-branch}
Render:
## CircleCI logs — {repo} `{branch}`
| Job | Status | Number |
|-----|--------|--------|
Then include the tail or relevant failure portion of ---LOGS---. Keep output concise; prefer the final failing command/error block over dumping thousands of lines. If no token is configured, explain that logs require a CircleCI key for SECRET_API_KEY_PROJECT.
Failure handling
NO_GIT_REPO: say this must be run inside a GitHub-backed git repo.NO_TOKEN: show GitHub status if available, and explain how to configure the project keyring lookup.- CircleCI API errors: report the error and fall back to GitHub commit/check status when present.