ci-audit SKILL.md skillA
ci-audit from coreyhaines31/makerskills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add coreyhaines31/makerskills/ci-audit@v0.1.0Pins v0.1.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- coreyhaines31/makerskills
- Path
skills/ci-audit/SKILL.md- Versions recorded
- 2
- Latest version
- v0.1.0, committed Nov 9, 2026
- First version recorded
- Nov 5, 2026
- Size
- 7,730 bytes
- Repository stars
- 919
- License
- MIT
When you want to cut GitHub Actions minutes and wait time across one repo or a whole portfolio. Measures queue, setup and run time per job, billed minutes with per-job minute rounding and the macOS 10× multiplier, and cron runs per month. Finds pipelines that have been failing quietly, ranks fixes by minutes saved, then ships them as small PRs with warm-cache before/after numbers. Triggers on "/ci-audit," "audit our CI," "why is CI so slow," "cut Actions minutes…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# /ci-audit — Find and fix wasted GitHub Actions time Measure first, then fix the few things that matter. In real audits the biggest win was rarely a slow test suite. It was a scheduled pipeline that had failed every day for months, a 30-second hourly cron billed as 730 minutes a month, or an SDK silently retrying a dead request three times. A stdlib script, `scripts/ci_audit.py` in this skill's folder, does the measuring. You read its output, decide what's worth fixing, and ship it. ```bash python3 <skill-dir>/scripts/ci_audit.py inventory <owner> # which repos run Actions, private vs public python3 <skill-dir>/scripts/ci_audit.py month <owner/repo> # billable minutes by workflow, 30 days python3 <skill-dir>/scripts/ci_audit.py jobs <owner/repo> --runs 150 # queue / setup / run per job python3 <skill-dir>/scripts/ci_audit.py steps <owner/repo> <run-id> # per-step seconds for one run python3 <skill-dir>/scripts/ci_audit.py schedules <owner/repo> # every cron as runs per month ``` It needs the GitHub CLI (`gh`) logged in. `month` and `jobs` make one API call per run, so a busy repo takes a minute or two. Run them in the background. …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_ncfmggbeb4gnh4ww/809551a03ba3c94ce199181753bff28e800abc8a539cbdc1623995c8074e9d35.json
Then /plugin install ci-audit@markdownregistry-ncfmggbeb4gnh4ww in Claude Code. It installs v0.1.0, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add coreyhaines31/makerskills/ci-audit@sha256:809551a03ba3c94cThe line at the top of this page pins the label v0.1.0, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_ncfmggbeb4gnh4ww)
4 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in coreyhaines31/makerskills/ci-audit since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of ci-audit from somewhere else? Ask it: where did my ci-audit come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 2 versions of this file, between Nov 5, 2026 and Nov 9, 2026, about one every 5 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v0.1.0 latest | 2026-11-09 | 2079c09 | 7,730 B | A | view · diff |
| v0.1.0 | 2026-11-05 | 41230b0 | 7,717 B | A | view |
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/ci-audit/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (7730 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
coreyhaines31/makerskills · 919 stars · license MIT · pushed 2026-11-11 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ncfmggbeb4gnh4ww GET https://markdownregistry.com/api/v1/resolve?ref=coreyhaines31/makerskills/ci-audit GET https://markdownregistry.com/api/v1/blob/809551a03ba3c94ce199181753bff28e800abc8a539cbdc1623995c8074e9d35
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from coreyhaines31/makerskills
Every file in coreyhaines31/makerskills