tdd-workflow
Use this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests.
Install with Tessl CLI
npx tessl i github:sc30gsw/claude-code-customes --skill tdd-workflow79
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 — 81%
↓ 0.90xAgent success when using this skill
Validation for skill structure
Discovery
67%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description has good structure with explicit 'Use when' guidance and clearly states the TDD enforcement purpose. However, the trigger conditions are overly broad (any coding task) which creates high conflict risk with other development skills, and the specific capabilities could be more concrete.
Suggestions
Narrow the trigger conditions to be more specific, e.g., 'Use when the user asks about testing, wants TDD workflow, mentions code coverage, or requests test-first development'
Add more concrete actions like 'generates test files, runs coverage analysis, creates test fixtures and mocks, validates coverage thresholds'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names domain (writing features, fixing bugs, refactoring) and mentions TDD with coverage requirements, but lacks specific concrete actions like 'generate test files', 'run coverage reports', or 'create mocks'. | 2 / 3 |
Completeness | Explicitly answers both what ('Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests') and when ('Use this skill when writing new features, fixing bugs, or refactoring code'). | 3 / 3 |
Trigger Term Quality | Includes some relevant terms ('features', 'bugs', 'refactoring', 'test-driven', 'coverage') but these are fairly generic coding terms that could apply to many skills. Missing natural variations like 'TDD', 'write tests', 'testing', 'test coverage'. | 2 / 3 |
Distinctiveness Conflict Risk | The triggers 'writing new features, fixing bugs, or refactoring code' are extremely broad and would conflict with virtually any coding-related skill. The TDD/testing focus provides some distinction but the trigger conditions are too generic. | 2 / 3 |
Total | 9 / 12 Passed |
Implementation
70%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill excels at actionability with comprehensive, executable code examples and has a clear TDD workflow with proper validation steps. However, it suffers from being overly long and monolithic—content that should be in separate reference files (mocking patterns, E2E examples, testing patterns) is all inline, and some sections contain generic advice Claude already knows.
Suggestions
Split detailed patterns into separate files: MOCKING.md for mock examples, E2E-PATTERNS.md for Playwright patterns, and reference them from the main skill
Remove generic content Claude already knows: 'Best Practices' list items like 'Write Tests First' and 'One Assert Per Test' are standard TDD knowledge
Condense the 'When to Activate' section—Claude can infer when TDD applies without an explicit list
Add a quick-reference summary at the top with the core workflow steps, moving detailed examples to linked files
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is moderately verbose with some unnecessary explanations (e.g., explaining what TDD is, listing 'When to Activate' scenarios Claude can infer). The extensive code examples are valuable but could be more condensed, and some sections like 'Best Practices' and 'Success Metrics' contain generic advice Claude already knows. | 2 / 3 |
Actionability | Provides fully executable, copy-paste ready code examples for unit tests, integration tests, E2E tests, and mocking patterns. Commands are specific (npm test, npm run test:coverage) and examples are complete with imports and assertions. | 3 / 3 |
Workflow Clarity | Clear 7-step TDD workflow with explicit validation checkpoints (Step 3: tests should fail, Step 5: tests should pass, Step 7: verify coverage). Includes feedback loop for refactoring while keeping tests green, and continuous testing patterns for ongoing validation. | 3 / 3 |
Progressive Disclosure | Monolithic wall of text at ~400 lines with no references to external files. Content like detailed mocking patterns, E2E test examples, and testing patterns could be split into separate reference files. No navigation structure beyond inline headers. | 1 / 3 |
Total | 9 / 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.