Content
37%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill reads as a textbook summary of well-known testing concepts rather than actionable guidance that adds value beyond Claude's existing knowledge. The content is mostly descriptive, lacking executable code examples and clear workflows. The progressive disclosure structure is reasonable in intent but unsupported by actual bundle files, and the inline content is too verbose for concepts Claude already understands.
Suggestions
Remove or drastically condense explanations of concepts Claude already knows (test pyramid, test doubles definitions, AAA pattern) and focus on project-specific conventions or non-obvious patterns.
Add a clear decision workflow: 'When writing tests for this project, follow these steps: 1. Determine test type needed → 2. Set up isolation → 3. Write test → 4. Verify coverage threshold' with validation checkpoints.
Replace descriptive text blocks with executable code examples for each test type and isolation strategy, showing concrete implementations rather than abstract descriptions.
Either provide the referenced bundle files (tdd-workflow.md, mocking-strategies.md, etc.) or remove the references to avoid broken links.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably organized but includes information Claude already knows well—test pyramid concepts, AAA pattern, test double definitions, and what to test/avoid are all standard testing knowledge. The ASCII art pyramid and the descriptive tables add tokens without providing novel, actionable guidance. | 2 / 3 |
Actionability | There is one concrete Python code example (AAA pattern) and a naming convention template, but most content is descriptive rather than executable. Database isolation strategies, external service isolation, and test doubles are described abstractly without concrete, copy-paste-ready code. The test types section uses plain text blocks rather than executable examples. | 2 / 3 |
Workflow Clarity | There is no clear multi-step workflow or sequenced process. The content is a reference catalog of testing concepts rather than a guide for how to approach testing a codebase. There are no validation checkpoints, feedback loops, or decision trees for choosing between strategies. | 1 / 3 |
Progressive Disclosure | The skill references four files under ./references/ and one script, which is good structure for progressive disclosure. However, no bundle files are provided, meaning these references are broken/unverifiable. The main file also contains substantial inline content that could be better distributed to those reference files. | 2 / 3 |
Total | 7 / 12 Passed |