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:affaan-m/everything-claude-code --skill tdd-workflow74
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/skillValidation 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 terms are overly broad (features, bugs, refactoring apply to nearly all coding tasks), which creates high conflict risk with other coding skills. The specific actions enforced by the skill could be more concrete.
Suggestions
Narrow the trigger conditions to be more specific, e.g., 'Use when the user explicitly requests test-driven development, asks for tests to be written first, or mentions coverage requirements'
Add more natural trigger term variations like 'TDD', 'write tests first', 'test coverage', 'testing strategy'
List more concrete actions the skill performs, e.g., 'Writes failing tests before implementation, generates test fixtures, 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 'write unit tests', 'generate test fixtures', or 'run coverage reports'. | 2 / 3 |
Completeness | Explicitly answers both what (enforces TDD with 80%+ coverage including unit, integration, E2E tests) and when ('Use this skill when writing new features, fixing bugs, or refactoring code') with clear trigger guidance. | 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 features', 'fixing bugs', and 'refactoring code' are extremely common coding activities that would likely conflict with general coding skills. The TDD/testing focus provides some distinction but the primary triggers are too broad. | 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 provides excellent actionable guidance with complete, executable code examples and a clear TDD workflow with validation checkpoints. However, it suffers from being overly long and monolithic - content like mocking patterns, CI/CD integration, and detailed test organization should be split into separate reference files. Some sections explain concepts Claude already knows (basic TDD principles, best practices lists).
Suggestions
Split mocking patterns, CI/CD integration, and test organization into separate reference files (e.g., MOCKING.md, CI_SETUP.md) with clear links from the main skill
Remove or significantly condense the 'Best Practices' and 'Common Testing Mistakes' sections - Claude knows these patterns
Trim the 'Core Principles' section which restates TDD basics that Claude already understands
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is moderately efficient but includes some unnecessary content like the 'Best Practices' list of 10 items that Claude already knows, and verbose explanations of TDD concepts. The file is quite long (~400 lines) when it could be more compact. | 2 / 3 |
Actionability | Provides fully executable code examples for unit tests, integration tests, E2E tests, and mocking patterns. Commands are copy-paste ready (npm test, npm run test:coverage) and examples are complete TypeScript/JavaScript. | 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). The sequence is unambiguous with feedback loops built in. | 3 / 3 |
Progressive Disclosure | Monolithic wall of text with no references to external files. All content is inline including detailed mocking patterns, test organization, and CI/CD examples that could be split into separate reference files for better organization. | 1 / 3 |
Total | 9 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- 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.