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:ysyecust/everything-claude-code --skill tdd-workflow

What are skills?

1.07x

Quality

68%

Does it follow best practices?

Impact

89%

1.07x

Average score across 3 eval scenarios

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/tdd-workflow/SKILL.md

SKILL.md

Review

Evals

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.

The skill provides excellent actionable guidance with executable code examples and a clear TDD workflow with validation steps. However, it suffers from being overly verbose and monolithic—content that Claude already knows (TDD principles, best practices lists) inflates the token count, and the lack of progressive disclosure means everything is dumped into one large file rather than organized with references.

Suggestions

Split testing patterns (unit, integration, E2E) into separate reference files like UNIT_TESTS.md, INTEGRATION_TESTS.md, E2E_TESTS.md and link to them from the main skill

Remove or drastically condense 'Core Principles', 'Best Practices', and 'Common Testing Mistakes' sections—Claude knows TDD fundamentals

Move mocking examples to a separate MOCKING.md reference file

Reduce the main SKILL.md to a concise overview (~100 lines) with the 7-step workflow and links to detailed reference files

Dimension	Reasoning	Score
Conciseness	The skill is comprehensive but overly verbose for Claude. Sections like 'Core Principles' and 'Best Practices' list concepts Claude already knows. The extensive code examples are valuable but could be more condensed with references to external files.	2 / 3
Actionability	Provides fully executable code examples for unit tests, integration tests, and E2E tests. Commands are copy-paste ready (npm test, npm run test:coverage), and patterns include complete, runnable TypeScript/Jest/Playwright code.	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.	3 / 3
Progressive Disclosure	Monolithic wall of text at ~400 lines with no references to external files. Testing patterns, mocking examples, and E2E patterns could be split into separate reference files. Everything is inline with no navigation structure.	1 / 3
	Total	9 / 12 Passed

Validation

90%

Warnings & errors only

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: 5 days ago

Table of Contents

Discovery Implementation Validation

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.