Content
72%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.
The body is exceptionally concise and well-structured with appropriately split, real script references. Its weaknesses are instructional: it lacks concrete usage examples or a sequenced workflow that would let Claude execute the commands with confidence.
Suggestions
Add a brief usage example per command (e.g., sample '/spec src/auth.py' input→output) to lift actionability toward executable guidance.
Include a short sequenced workflow for handling a user query (retrieve → assemble context → answer with citations) with an explicit verification step that citations resolve to real paths/lines.
Optionally show the search_codebase tool call signature so the retrieval step is concrete rather than implied.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and efficient (~24 lines) with no padding or explanations of concepts Claude already knows; the one-line intro and capability/script lists all earn their place, matching the 'lean and efficient; every token earns its place' anchor. | 5 / 5 |
Actionability | Provides some concrete guidance (command syntax '/spec [filepath]' and '/gaps' with described outputs, plus a script→class map) but no runnable code, example invocations, or specific execution steps; fits 'some concrete guidance but incomplete; missing key details' and below 4 which requires mostly-executable guidance. | 3 / 5 |
Workflow Clarity | States one clear behavioral rule ('always retrieves before answering — never from memory alone') but lays out no sequenced multi-step workflow or validation checkpoints for the three command modes; the rule is cleaner than anchor 2's 'rough sequence, many gaps' yet lacks the explicit sequence of anchor 4. | 3 / 5 |
Progressive Disclosure | Under 50 lines with well-organized sections (Capabilities, Scripts) and clearly-signaled, one-level-deep references to real bundle files (retriever.py, agent.py, spec.py, gaps.py, each mapped to its responsibility); per the simple-skill note this warrants 5 for clear, well-organized structure. | 5 / 5 |
Total | 16 / 20 Passed |