← ClaudeAtlas

gold-auditlisted

Use when the user wants to measure how close the project is to gold-standard quality — runs the deterministic `arbiter gold-audit` engine and reports the level band plus a prioritized list of what is missing. Read-only; never changes code.
LucaDominici/arbiter · ★ 0 · AI & Automation · score 72
Install: claude install-skill LucaDominici/arbiter
# 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 ```bash npx @arbiter/cli gold-audit --json ``` The 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: ```bash npx @arbiter/cli init # new project — sets up the registry + gates npx @arbiter/cli update # existing arbiter project — refreshes the generated kit ``` Then 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`