Conciseness

Mostly lean and imperative with no concept re-teaching, but the core prohibitions are stated three times: "**Every one of those is forbidden**" in the opening section, the full "You may NEVER silence a check" list, and then "Hard nevers" which restates "Never silence a check", "Never add a test-skip marker", and "Never touch the check machinery" already covered above. Roughly 15–20 lines could be cut without losing a single constraint. Not 2 because there is no padding or explanation of things Claude already knows; not 4 because the duplication is more than a minor trim — it is a structural restatement of the same list.

Actionability

Concrete commands throughout: `./scripts/local-checks.sh`, `./prds/<f>/run-prd-test.sh`, `claude -p "/fix-local-checks <feature>"`, a model commit message (`fix(local-checks): trim query whitespace`), and an exact enumeration of forbidden directives (eslint-disable*, @ts-ignore, # noqa, #[allow(...)]). Not 5 because some directions stay judgment-shaped ("Do the best **honest** fix you can", "Make whatever honest partial progress you can") without a worked example of triage in action; not 3 because everything runnable is spelled out exactly.

Workflow Clarity

Steps 1–5 are a clear, ordered sequence with an explicit validation checkpoint ("Re-run `./scripts/local-checks.sh`" before commit), a feedback loop (dispatcher re-runs the gate; partial-progress commits so attempts compound), and a defined stop/error-recovery path (step 5, STUCK escalation). Not 4 because validation is explicit at the commit boundary and both success and failure outcomes are fully specified.

Progressive Disclosure

Well-organized single-file skill with clear section headers and no bundle files, so nothing is mis-filed or nested; navigation is easy. Not 5 because at ~105 lines it exceeds the simple-skill (<50 lines) exception and some reference-shaped material (the exhaustive suppression-directive list, the dispatcher contract) could live in a references file with SKILL.md as overview; not 3 because the structure that is present is clean and nothing that belongs elsewhere is buried.

Specificity

Lists multiple concrete actions — "Reads the (remediation-rich) check failures, fixes the underlying cause, never silences a check, re-verifies, and commits" — comprehensively covering the skill's job in third-person imperative voice. Not level 4 because coverage of the what is complete rather than having minor gaps; not below because there is no vague or generic language.

Completeness

Explicitly answers what ("Patch the code so `scripts/local-checks.sh` passes", "fixes the underlying cause, never silences a check, re-verifies, and commits") and when ("after /implement-mainspec", "Invoked headless by the dispatcher's two-strike local-checks gate", plus an explicit "Triggers -" clause). Not 4 because the when is fully explicit with concrete trigger phrases rather than merely present.

Trigger Term Quality

"Triggers - fix-local-checks, fix lint, fix local checks, fix typecheck, make checks pass, post-implement polish" gives good natural-phrase coverage. Not 5 because common variations users would say are missing (e.g. "make lint pass", "fix the build", "fix tests", "make CI green"); not 3 because multiple natural synonyms are present, not just one or two generic keywords.

Distinctiveness Conflict Risk

"a narrow post-implement polish specialist" scoped to a named script (`scripts/local-checks.sh`), a named predecessor skill (/implement-mainspec), and the dispatcher's gate carves a clear niche with distinct triggers and minimal conflict risk. Not 4 because the unambiguous "fix-local-checks" / "fix local checks" anchors the niche beyond the mildly generic "fix lint" / "make checks pass" phrases.