Content
100%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 exemplary process skill: a clearly gated six-phase workflow where every phase carries specific, non-obvious discipline rather than generic debugging advice. Validation checkpoints, checklists, and feedback loops are all explicit, and the one bundle reference is real, well-placed, and one level deep.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and assumes Claude's competence throughout — it spends its tokens exclusively on non-obvious discipline (tag every debug log with '[DEBUG-a4f2]', falsifiable hypothesis format, 'correct seam' test rule) and never explains concepts Claude already knows. Every section earns its place; the rhetorical emphasis lines ('Be aggressive. Be creative. Refuse to give up.') serve prioritization rather than padding. | 5 / 5 |
Actionability | Guidance is highly concrete for an instruction-only skill: ten loop-construction strategies in ranked order, a quoted hypothesis template ('If <X> is the cause, then <changing Y> will make the bug disappear'), a copy-paste-ready script path for the human-in-the-loop case, and explicit checklists — Claude knows exactly what to do at every phase. | 5 / 5 |
Workflow Clarity | The six phases are clearly sequenced with hard gates ('Do not proceed to Phase 2 until you have a loop you believe in', 'Do not proceed until you reproduce the bug'), validation checklists in Phases 2 and 6, and a full fail→fix→pass→re-run feedback loop in Phase 5 that re-verifies against the original un-minimised scenario. | 5 / 5 |
Progressive Disclosure | Content is well-organized in clearly-headed sections, and the single bundle file (scripts/hitl-loop.template.sh — verified to exist) is referenced one level deep, exactly at its point of use in strategy #10. Nothing that belongs in a separate file is inlined, and the external skill/doc pointers (/improve-codebase-architecture, docs/adr/) are clearly signaled hand-offs rather than buried references. | 5 / 5 |
Total | 20 / 20 Passed |