Content
62%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 core TDD workflow (Steps 0–8) is exceptionally well specified with rigorous validation gates and evidence reporting, and the guidance is largely executable. However, the file is bloated with generic testing knowledge Claude already possesses, and nothing is offloaded to reference files despite the length.
Suggestions
Delete or drastically compress the generic sections Claude already knows: "Best Practices", "Common Testing Mistakes to Avoid", the Button unit-test pattern, and the long generic Playwright example — keep only project-specific conventions.
Move the test patterns (unit/integration/E2E), mocking recipes (Supabase/Redis/OpenAI), and CI/CD examples into reference files (e.g., references/patterns.md, references/mocking.md) and link them from the body, turning SKILL.md into a lean workflow overview.
Complete or remove stub examples like "// Test implementation" and the unfinished database-error integration test so every code example is executable as written.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Large sections restate testing knowledge Claude already has — the "Best Practices" list ("Write Tests First", "Arrange-Act-Assert", "Mock External Dependencies"), "Common Testing Mistakes to Avoid", a generic Button unit-test pattern, and a ~50-line generic Playwright example — so several padded sections dilute the genuinely non-obvious workflow steps. | 2 / 5 |
Actionability | Mostly executable: a runner command matrix, an executable package-manager detector script with failure handling, exact commit message formats, and an evidence-report table template; minor gaps remain in stub examples like "// Test implementation" and the unfinished "handles database errors gracefully" test body. | 4 / 5 |
Workflow Clarity | Steps 0–8 are explicitly sequenced with hard validation gates — the RED gate with runtime/compile-time paths and "Do not edit production code until this RED state is confirmed", the GREEN rerun, coverage verification — plus a plan-safety checklist, error-recovery loops, and per-stage checkpoint commit verification. | 5 / 5 |
Progressive Disclosure | The single ~590-line file has clear section headers, but all reference material (test patterns, mocking recipes, mistake catalog, CI examples) is inlined rather than split into separate files, and no bundle files exist to offload it. | 3 / 5 |
Total | 14 / 20 Passed |