tdd
Use when implementing any feature or bugfix, before writing implementation code
68
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillEvaluation — 100%
↑ 1.00xAgent success when using this skill
Validation for skill structure
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 explaining what the skill actually does. The vague scope ('any feature or bugfix') makes it indistinguishable from countless other development skills and provides no concrete actions or capabilities.
Suggestions
Add specific actions describing what this skill does (e.g., 'Creates implementation plans', 'Analyzes requirements', 'Designs architecture', 'Writes test cases first')
Narrow the scope to distinguish from other development skills - what specific pre-implementation activity does this skill perform?
Include natural trigger terms users would say when needing this skill (e.g., 'plan implementation', 'design approach', 'break down task', 'TDD')
| 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 indication of the skill's actual capabilities or actions. | 1 / 3 |
Trigger Term Quality | Contains some relevant keywords like 'feature', 'bugfix', and 'implementation code' that users might naturally say, but lacks variations and specific terms that would help distinguish this skill's purpose. | 2 / 3 |
Distinctiveness Conflict Risk | Extremely generic - 'any feature or bugfix' could apply to virtually any development-related skill. This would conflict with numerous coding, planning, testing, or documentation 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 main weakness is redundancy—the philosophical justifications and rationalizations sections overlap significantly, adding ~100 lines that could be consolidated. The core TDD cycle documentation is exemplary with explicit verification steps.
Suggestions
Consolidate 'Why Order Matters' and 'Common Rationalizations' sections into a single, leaner table to reduce redundancy
Consider moving the detailed rationalizations to a separate reference file since Claude understands TDD philosophy
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is well-organized but contains significant repetition—the 'Common Rationalizations' table largely duplicates the 'Why Order Matters' section. Some philosophical justifications could be trimmed since Claude understands TDD concepts. | 2 / 3 |
Actionability | Provides fully executable TypeScript examples with clear Good/Bad comparisons, specific bash commands for verification, and concrete code snippets for each TDD phase. Copy-paste ready. | 3 / 3 |
Workflow Clarity | Excellent multi-step workflow with explicit verification checkpoints after each phase (RED→verify→GREEN→verify→REFACTOR→verify). Clear feedback loops for error recovery and a comprehensive verification checklist. | 3 / 3 |
Progressive Disclosure | Well-structured with clear sections progressing from overview to detailed phases to troubleshooting. References external file (testing-anti-patterns.md) appropriately with one-level-deep navigation. | 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.
- 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.