Content
27%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is comprehensive in coverage but severely bloated, explaining many concepts Claude already knows (TDD basics, test isolation, AAA pattern) while inlining content that should be in separate reference files. The code examples are a strength but several are incomplete stubs. The workflow is reasonably clear but lacks error recovery feedback loops.
Suggestions
Cut the content by at least 50%: remove 'Core Principles' explanations of test types, 'Best Practices' list, 'Common Testing Mistakes' section, and 'Success Metrics' — these are generic testing knowledge Claude already has.
Split mocking patterns, E2E test patterns, and CI/CD configuration into separate referenced files (e.g., MOCKING.md, E2E_PATTERNS.md) to improve progressive disclosure.
Complete the stub code examples — Step 4's implementation and the database error test case should have actual executable code, not placeholder comments.
Add explicit feedback loops to the workflow: 'If coverage < 80%, run coverage report to identify gaps → add tests for uncovered paths → re-run coverage check.'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~300+ lines. Explains basic TDD concepts Claude already knows (what unit/integration/E2E tests are, Arrange-Act-Assert, test isolation). The 'Best Practices' and 'Common Testing Mistakes' sections are generic testing knowledge. The 'When to Activate' section restates the obvious. Much of this could be cut by 60%+ without losing actionable value. | 1 / 3 |
Actionability | Provides concrete, executable code examples for unit tests, integration tests, E2E tests, and mocking patterns, which is good. However, many examples are incomplete (e.g., Step 4's implementation is just a stub with '// Implementation here', the database error test has '// Test error handling' placeholder). The workflow steps mix concrete commands with vague instructions like 'Write minimal code to make tests pass.' | 2 / 3 |
Workflow Clarity | The 7-step TDD workflow is clearly sequenced and includes a validation checkpoint (Step 7: verify coverage). However, there's no feedback loop for when coverage falls below 80% — no explicit 'if coverage < 80%, identify gaps and add tests' step. The workflow also lacks validation between steps (e.g., what to do when tests fail unexpectedly in Step 5). | 2 / 3 |
Progressive Disclosure | This is a monolithic wall of text with no references to external files. All content — mocking patterns, E2E patterns, CI/CD config, best practices, file organization — is inlined in a single massive document. The mocking examples, testing patterns, and CI/CD integration could easily be split into separate reference files with links from the main skill. | 1 / 3 |
Total | 6 / 12 Passed |