test-driven-development
Use when implementing any feature or bugfix, before writing implementation code
66
50%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.claude/skills/test-driven-development/SKILL.mdQuality
Discovery
14%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is critically incomplete - it only specifies timing ('before writing implementation code') without ever explaining what the skill actually does. The vague scope ('any feature or bugfix') makes it indistinguishable from countless other development-related skills and provides no concrete actions or capabilities.
Suggestions
Add specific concrete actions the skill performs (e.g., 'Creates implementation plans', 'Analyzes requirements', 'Designs architecture', 'Writes pseudocode')
Narrow the scope to a specific type of pre-implementation activity rather than 'any feature or bugfix' to reduce conflict with other skills
Include distinctive trigger terms users would naturally say when needing this skill (e.g., 'plan implementation', 'design approach', 'break down task')
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions - it only states when to use the skill ('before writing implementation code') but never describes what the skill actually does. 'Implementing any feature or bugfix' is extremely vague. | 1 / 3 |
Completeness | The description only addresses 'when' (before writing implementation code) but completely fails to answer 'what does this do'. There is no explanation of the skill's actual capabilities or actions. | 1 / 3 |
Trigger Term Quality | Contains some natural terms like 'feature', 'bugfix', and 'implementation code' that users might say, but lacks specificity about what kind of implementation or what actions are involved. Missing common variations and concrete trigger terms. | 2 / 3 |
Distinctiveness Conflict Risk | 'Any feature or bugfix' and 'implementation code' are extremely generic terms that would apply to virtually any coding-related skill. This would conflict with numerous other development skills. | 1 / 3 |
Total | 5 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, actionable TDD skill with excellent workflow clarity and concrete examples. The verification checkpoints are explicit and mandatory, which is critical for a discipline-focused skill. The main weakness is some redundancy between sections explaining why TDD matters and common rationalizations, which could be consolidated to improve token efficiency.
Suggestions
Consolidate the 'Why Order Matters' section and 'Common Rationalizations' table to eliminate redundancy—the table could replace the prose explanations
Trim explanations of why tests-after are problematic; Claude understands software testing principles and needs the 'what to do' more than the 'why it matters'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient but includes some redundancy—the 'Common Rationalizations' table repeats content from the 'Why Order Matters' section, and the 'Red Flags' list overlaps with rationalizations. Some explanations of why TDD matters could be trimmed since Claude understands software development principles. | 2 / 3 |
Actionability | Provides fully executable TypeScript code examples, specific bash commands for verification, and concrete Good/Bad comparisons. The bug fix example walks through a complete TDD cycle with copy-paste ready code. | 3 / 3 |
Workflow Clarity | The Red-Green-Refactor cycle is explicitly sequenced with mandatory verification steps at each stage. The graphviz diagram, explicit 'MANDATORY' callouts, and verification checklist provide clear feedback loops for error recovery. | 3 / 3 |
Progressive Disclosure | Well-structured with clear sections progressing from overview to detailed workflow to troubleshooting. References external file (@testing-anti-patterns.md) appropriately for related but separate content. Content is appropriately organized without deep nesting. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- vgeshel/local-skills
- Commit
c10c616
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.