agentleFS
LucaDominiciLucaDominici/arbiter/.claude/skills/close-gold-gap/SKILL.md

close-gold-gap

Skill0 starsChanged 58 days agoApache-2.0View on GitHub

Use when the gold-audit reports an N/P gap (or a manual check) and you want the deterministic remediation recipe — scaffold/test/config/process — that closes it for a REAL reason, never by faking it.

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
  1. Very specific:

    After arbiter audit readiness reports a gap (an N or P check, or a manual check that a human must attest).

    line 21
  2. Distinctive:

    Run the audit to list the gaps:

    line 26
  3. Very specific:

    After executing a recipe, re-run npx @getarbiter/cli audit readiness and confirm the gap flipped for a real reason — the genuine metric …

    line 56

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Close Gold Gap

Turn one gold-audit gap into a concrete, deterministic remediation recipe — then carry it out. This skill never fakes a close: a recipe is a plan of real work, not a shortcut to flip a verdict.

When to use

After arbiter audit readiness reports a gap (an N or P check, or a manual check that a human must attest). Pick the gap's id and ask for its recipe.

Workflow

  1. Run the audit to list the gaps:
npx @getarbiter/cli audit readiness
  1. Classify the gap by category — what does the failed check actually verify? There is no separate recipe engine; the category table below is the recipe.
  2. Execute the recipe's steps yourself. Each step is typed by category:
CategoryWhat the recipe doesHonest outcome
doc-setScaffold the missing doc (check-doc-set --generate) then fill real contentP → Y only after real content
testWrite the missing test(s) TDD-first (loads the tdd skill)Y when the real metric meets the bar
configWire the real tool/config the check verifiesY when the tool genuinely runs
processHuman-only action for a manual check — no code recipeNV (code cannot verify it)

Anti-fake-green (hard rules)

  • A doc stub proves presence, not closure — a scaffold-only step is P, never Y. Fill it with real content before claiming the check.
  • A manual check is NV: code cannot verify it. There is no code recipe — a human performs and records the real-world action. Never try to make code "pass" a manual check.
  • No suppression — a recipe never contains --no-verify, eslint-disable, skip, or ignore.
  • No marker-stuffing — never write the matched pattern/equals literal as the sole action; wire the behavior the check is verifying.

Re-audit

After executing a recipe, re-run npx @getarbiter/cli audit readiness and confirm the gap flipped for a real reason — the genuine metric improved or real content/config now exists. If it only flipped because a threshold moved or a literal was pasted in, that is fake-green: revert and do the real work.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.