gold-audit
Skill0 starsChanged 58 days agoApache-2.0View on GitHub
Use when the user wants to measure how close the project is to gold-standard quality — runs the deterministic `arbiter audit readiness` engine and reports the level band plus a prioritized list of what is missing. Read-only; never changes code.
In this repository23 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .claude/CLAUDE.mdCLAUDE.md
- llms.txtllms.txt
- architect-reviewSkill
- brainstormingSkill
- clean-codeSkill
- close-gold-gapSkill
- codebase-auditSkill
- configureSkill
- context-rot-managementSkill
- epic-decomposeSkill
- impactSkill
- levelupSkill
- product-acceptanceSkill
- refutationSkill
- senior-surveySkill
- ssot-navigationSkill
- tabletopSkill
- tddSkill
- understand-codeSkill
- verificationSkill
- visual-verificationSkill
- wave-drainSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 54
When stdout is JSON, parse it and read these fields as-is (no re-scoring):
- Very specific: line 77
If gaps[] is empty, report that every applicable check is Y.
- Very specific: line 90
Graceful when absent: No registry ⇒ point at arbiter init / arbiter update, never a fabricated score.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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
Gold Audit (measure)
Goal: tell the user where the project sits against the gold-standard registry —
its level band (L0–L3), its score, and a prioritized "what's missing" list — so
they know exactly what to close next.
Read-only. This skill MEASURES; it never changes a single file. It runs the existing deterministic engine and presents the result. It does NOT re-score, re-rank, or "estimate" anything with the model — the verdicts come straight from the engine.
Step 1 — Run the engine
npx @getarbiter/cli audit readiness --jsonThe CLI auto-detects the project's brownfield class and degrades gracefully when no registry is installed. Capture stdout as the payload.
Step 2 — Handle the graceful fallback
The engine prints a non-JSON SKIP line (it does not start with {) when there is no
registry/engine installed. In that case do NOT invent a score. Tell the user the
gold registry isn't wired up yet and point them at:
npx @getarbiter/cli init # new project — sets up the registry + gates
npx @getarbiter/cli update # existing arbiter project — refreshes the generated kitThen stop.
Step 3 — Read the payload verbatim
When stdout is JSON, parse it and read these fields as-is (no re-scoring):
| Field | Use |
level.level | Current band: L0 / L1 / L2 / L3 |
level.nextLevel / level.toNextLevel | Next band + how many points away |
level.brownfieldClass | The detected class the band is keyed to |
score | Overall score |
yCount / totals.checks | Checks fully satisfied vs total |
riskyCount | Count of risky (N/P on high-risk) checks |
checks[] | Per-check id / dimension / title / type / verdict / weight / evidence |
gaps[] | The "what's missing" families: N/P checks grouped by dimension |
Step 4 — Present the level band + prioritized gaps
Lead with the band, then the gap list grouped by family (dimension):
- Level line —
<level> (<brownfieldClass>) · score <score> · <toNextLevel> to <nextLevel> · Y <yCount>/<totals.checks> · RISKY <riskyCount>. - What's missing — iterate
gaps[]. For eachdimensionfamily, list its N/P checks as<verdict> <id> <title>with theevidence.file/evidence.detailwhen present. These are the concrete, deterministic next actions. - If
gaps[]is empty, report that every applicable check isY.
Prioritize the families with the most N (missing entirely) and highest-risk checks
first — but the ordering reflects the engine's verdicts, not a model opinion.
Hard rules
- Deterministic, no AI scoring. Same repo + same registry ⇒ identical output. The level and every verdict come from the engine payload; never substitute a guess.
- Read-only. Measure and report. Closing a gap is a separate, explicit action — this skill never edits code, config, or docs.
- Graceful when absent. No registry ⇒ point at
arbiter init/arbiter update, never a fabricated score.
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.

