circleci-job-results
Skill1 starsChanged 26 days agoApache-2.0View on GitHub
Read CircleCI pipeline, workflow, and job results through its API.
In this repository25 other files it gives its agents.
- AGENTS.mdAGENTS.md
- add-testSkill
- audit-fixissuesSkill
- autoresearchSkill
- benchmark-optimizeSkill
- citation-verifierSkill
- cli-designSkill
- codebase-auditSkill
- code-cleanupSkill
- deep-code-cleanupSkill
- doc-updateSkill
- emendSkill
- fix-issueSkill
- git-github-workflowSkill
- goal-modeSkill
- inspect-datasetSkill
- manage-pr-lifecycleSkill
- medcognetics-brandSkill
- notify-wakeSkill
- repo-maintenanceSkill
- review-fix-loopSkill
- standardize-ciSkill
- token-file-authSkill
- whats-nextSkill
- yeetSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Use $token-file-auth circleci for credentials, then the bundled scripts/fetch_circleci_job_results.sh.
- Distinctive: line 18
Use the exact requested pipeline or job.
- Distinctive: line 21
Never source a secret file, print its token, or pass it in command arguments.
- Distinctive: line 24
Read API examples only for queries outside the helper's modes, such as recent pipelines or custom workflow filters.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
CircleCI Job Results
Use $token-file-auth circleci for credentials, then the bundled
scripts/fetch_circleci_job_results.sh. Resolve paths relative to this skill.
Supported queries:
--pipeline-id <id>for workflows and jobs.--project-slug <slug> --job-number <number>for one job.--auth-smoke-testwhen authentication needs diagnosis.--format jsonfor machine-readable results.
Use the exact requested pipeline or job. Report its identity, status, and relevant failure details. A running result is not a successful result.
Never source a secret file, print its token, or pass it in command arguments. The helper supplies curl headers through stdin. Unset tokens after custom calls.
Read API examples only for queries outside the helper's modes, such as recent pipelines or custom workflow filters.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

