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.
An exceptionally actionable, well-sequenced protocol skill: concrete commands, explicit validation checkpoints, and genuine error-recovery loops in both the orientation and handoff workflows. The only deductions are minor rhetorical padding and a single-file structure that could offload detail to reference files.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense and imperative and assumes Claude's competence ("never trust a summary's paraphrase of it", "A timeout is not a failure signal"), with only minor rhetorical flourishes like "A past session that did work without updating these stole from you" that could be trimmed. It is not 5 because a few motivational asides don't strictly earn their tokens, and not 3 because the padding is minor and mostly load-bearing rationale. | 4 / 5 |
Actionability | Guidance is copy-paste concrete throughout: "git status + git log --oneline -10", "./scripts/trace-audit.bb", "rg 'REQ-<ID>'", "br ready --json", and the scoped commit format "<scope>: <description>" with REQ ID in the body. Per the rubric's scoring note, this instruction-only skill is fully actionable without code examples. | 5 / 5 |
Workflow Clarity | Both the orientation protocol (steps 1–8) and handoff protocol (steps 1–5) are clearly sequenced with explicit validation checkpoints ("Run the baseline green", "Never end mid-red", run gates before ending) and error-recovery feedback loops (dirty tree → stop and report; timeout → extend the clock, don't relaunch). This matches the top anchor including checklists and recovery loops. | 5 / 5 |
Progressive Disclosure | The single file is well-organized with clear sections (First steps, Environment hazards, After compaction, Last steps, Work loop, Exploiting the clean state) and no nested references, but at ~150 lines with no bundle files, content like the work-loop and tracker-discipline details could be split into a one-level-deep reference. Good structure with minor organization gaps fits anchor 4. | 4 / 5 |
Total | 18 / 20 Passed |