test-driven-dev

Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development.

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

The canonical home for this skill is tdd in mattpocock/skills

Quality

Content

92%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A tight, opinionated TDD workflow with strong sequencing, checklists, and validation checkpoints. The main weakness is progressive disclosure: five bundle files are referenced but none are present, leaving dead links that break navigation.

Suggestions

Create the referenced bundle files (tests.md, mocking.md, deep-modules.md, interface-design.md, refactoring.md) or remove the broken links so navigation actually resolves.

If those topics are not substantial enough to warrant separate files, fold the essential guidance inline and drop the references rather than leaving dangling pointers.

Consider adding one concrete red-green-refactor code example (a failing test followed by minimal implementation) to make the abstract 'tracer bullet' step immediately executable.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence — it states a specific stance (vertical slices, don't mock internals) without explaining basic concepts Claude already knows, so every token earns its place per the score-3 anchor.	3 / 3
Actionability	Concrete, actionable guidance throughout — numbered workflow steps, explicit rules ('One test at a time', 'Only enough code to pass current test'), and copy-ready checklists; absence of code is not penalized for an instruction-only skill whose guidance is actionable.	3 / 3
Workflow Clarity	The RED→GREEN→Refactor process is clearly sequenced (Planning, Tracer Bullet, Incremental Loop, Refactor) with explicit validation checkpoints ('Never refactor while RED', 'Run tests after each refactor step') and per-cycle checklists, matching the score-3 anchor.	3 / 3
Progressive Disclosure	References are well-signaled inline ([tests.md], [mocking.md], [deep-modules.md], [interface-design.md], [refactoring.md]) and one level deep, but none of the referenced files actually exist in the bundle, so navigation does not resolve — capping this below 3.	2 / 3
	Total	11 / 12 Passed

Description

90%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, well-structured description with explicit 'Use when' triggers and good natural-keyword coverage. The only weakness is that the stated actions ('build features or fix bugs') are generic rather than concrete capabilities, capping specificity at 2.

Dimension	Reasoning	Score
Specificity	Names the domain ('Test-driven development with red-green-refactor loop') and the actions ('build features or fix bugs using TDD'), but the actions are generic rather than a list of multiple concrete capabilities as in the score-3 anchor.	2 / 3
Completeness	Explicitly answers both what (TDD with red-green-refactor loop) and when via a clear 'Use when...' clause listing multiple triggers, matching the score-3 anchor; not capped at 2 since the trigger guidance is explicit.	3 / 3
Trigger Term Quality	Covers natural terms a user would say — 'TDD', 'red-green-refactor', 'integration tests', 'test-first development' — matching the score-3 anchor's good coverage of natural keywords.	3 / 3
Distinctiveness Conflict Risk	TDD is a clear niche with distinct triggers ('red-green-refactor', 'test-first development') unlikely to fire for the wrong skill, matching the score-3 anchor.	3 / 3
	Total	11 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 5 missing	Warning

	Total	15 / 16 Passed

Repository: zebbern/claude-code-guide
Path: skills/test-driven-dev/SKILL.md
Commit: af7d491

Reviewed: about 8 hours 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.