Content
88%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A tight, highly actionable policy skill: concrete commands, an explicit feedback loop, a well-specified escalation path, and exhaustive forbidden-action lists. Its only weakness is redundancy — the never-rules are restated across three sections (most notably the closing "Hard nevers" section), which costs tokens without adding guidance.
Suggestions
Merge the "Hard nevers" section into the earlier "You may NEVER silence a check" section and skip rule, which already state the same constraints — one authoritative list would cut ~15 lines with no loss of guidance.
Trim the motivational framing in "This is the whole reason you exist as a separate, constrained skill" and "A check passing is a proxy..." to a single rule statement; the constraint is clear without the justification prose.
Consider moving the dispatcher contract details (invocation mechanics, counter file path, tick/STUCK lifecycle) into a short reference file, keeping the SKILL.md body focused on the fix workflow itself.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is efficient and assumes Claude's competence (no explanation of what linting or typechecking is), but the "never" rules are stated three times: the "You may NEVER silence a check" section, the skip rule's restatement, and the closing "Hard nevers" section which nearly duplicates prior content ("Never silence a check... Never add a test-skip marker... Never touch the check machinery"). Not 5 because the Hard nevers section is redundancy that could be trimmed; not 3 because the padding is minor and deliberate (load-bearing constraints) rather than unnecessary explanation. | 4 / 5 |
Actionability | Fully concrete guidance: exact commands (`./scripts/local-checks.sh`, `claude -p "/fix-local-checks <feature>"`), a specific commit message example (`fix(local-checks): trim query whitespace`), an exhaustive catalog of forbidden suppression directives (eslint-disable, @ts-ignore, # noqa, #[allow(...)]), and the exact counter file path (.harness/local-check-attempts-<f>). Not 4 because the common cases are covered copy-paste ready with no gaps. | 5 / 5 |
Workflow Clarity | Clear 5-step sequence (read failures → triage → fix cause → re-verify → commit/push) with an explicit validation checkpoint ("Re-run `./scripts/local-checks.sh`" before commit), a feedback loop (commit only honestly green or honest partial progress so attempts compound), and a well-defined error-recovery path (step 5: stop, commit partial progress, let the dispatcher STUCK). Not 4 because validation and recovery are explicit, not implicit. | 5 / 5 |
Progressive Disclosure | No bundle files exist, so the skill is appropriately self-contained: nothing (API reference, catalogs) is bulk-inlined that clearly belongs in a separate file, and sections are well-organized with clear headers. Not 5 because at ~105 lines the supporting detail (dispatcher contract mechanics, the suppression-directive catalog) could be externalized to references to keep the core workflow lean; not 3 because structure and navigation are good with no buried content. | 4 / 5 |
Total | 18 / 20 Passed |