Content
63%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 well-structured with excellent progressive disclosure: a tight overview pointing to a single real one-level-deep reference. Its weaknesses are a known-concept intro paragraph redundant with the Explain section, and generic Check/Fix guidance that defers all executable detail to the reference.
Suggestions
Delete the opening benefits paragraph and fold the redundant "## Explain" content into it, or replace both with one line of non-obvious guidance — Claude already knows why unit tests matter.
Inline one short executable anchor in the body (e.g., a coverage-check command or a minimal test skeleton) so the Check/Fix steps are immediately actionable before jumping to references/rule.md.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The opening paragraph ("Unit tests catch bugs before they reach production, serve as documentation for expected behavior...") explains benefits Claude already knows, and the "## Explain" section ("Explain how unit tests catch bugs early and serve as documentation for expected behavior") duplicates it. The rest of the body is lean, so this is some unnecessary explanation rather than several padded sections, fitting anchor 3 rather than 2 or 4. | 3 / 5 |
Actionability | The Quick Reference gives concrete heuristics ("Test business logic, utilities, and edge cases", "Aim for 80%+ coverage on critical paths", "Mock external dependencies, not internal modules"), but the Check/Fix directives ("Write unit tests for untested functions and components") are high-level and all code and examples are deferred to the reference file. Some concrete guidance, incomplete in the body itself — anchor 3, below 4 (no executable code or commands present) and above 2 (more than vague hints). | 3 / 5 |
Workflow Clarity | The Check → Fix → Code Review sections form a clear, unambiguous sequence for a simple single-purpose skill, with "Run tests in CI to catch regressions early" hinting at the verification endpoint. Verification checkpoints (run the coverage tool, confirm new tests pass) remain implicit rather than explicit steps, which keeps it below anchor 5 while the simple-skill exception keeps it above anchor 3's validation-gap level. | 4 / 5 |
Progressive Disclosure | The body is a short, well-sectioned overview that defers all implementation detail via a single clearly signaled one-level-deep pointer: "For full implementation details, code examples, and framework-specific guidance, see `references/rule.md`" — a real file (484 lines) with no further nested references. This matches the anchor for a clear overview with well-signaled, appropriately split references and easy navigation. | 5 / 5 |
Total | 15 / 20 Passed |