Content
92%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 lean, well-structured instruction skill: unambiguous mode dispatch, concrete per-mode outputs, explicit done-criteria and idempotency validation, and clean one-level references to a real pattern catalog and terminology guide. The main defect is one garbled boundary sentence about where the pattern catalog applies.
Suggestions
Rewrite the sentence "Note that the pattern catalog did not apply inside detect findings or inside a change line the caller asked for, and nowhere else." — its meaning is ambiguous; state plainly where pattern findings may and may not appear.
Add one short before/after sentence pair under 'The tests' showing a failing sentence and its fix, so the checks are executable without opening references/patterns.md.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The ~46-line body is lean throughout: no concept explanations Claude already knows, no padding, and every rule earns its place (e.g. "A sentence that passes stays as written, so a second pass on the returned text changes nothing"). It matches the 'every token earns its place' anchor. | 5 / 5 |
Actionability | Concrete, executable guidance for an instruction-only skill: an unambiguous mode-dispatch rule ("no draft means author; an imperative on a draft means edit; a question about a draft means detect"), per-mode outputs, and seven named checks. Not 5 because one sentence is hard to parse ("Note that the pattern catalog did not apply inside detect findings or inside a change line the caller asked for, and nowhere else.") and no pass/fail sentence examples are given, leaving minor execution gaps. | 4 / 5 |
Workflow Clarity | Clear sequence (dispatch mode → apply tests → edit or detect → return), with explicit validation checkpoints: a "Done:" definition acting as a completion checklist ("every fact, number, name, quote, and citation in the input survives") and an idempotency check for edit mode ("a second pass on the returned text changes nothing"). Not destructive or batch, so no cap applies. | 5 / 5 |
Progressive Disclosure | The body is a well-organized overview with two clearly signaled, real, one-level-deep references ("read `references/patterns.md`", "read `references/terminology.md`"), each loaded only when the inline tests do not settle a case; both files exist and are appropriately split out of the main body. | 5 / 5 |
Total | 19 / 20 Passed |