tdd

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.

1.18x

Quality

76%

Does it follow best practices?

Impact

96%

1.18x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/tdd/SKILL.md

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

Quality

Content

70%Weight 40%Scale 1-5

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

A well-sequenced, opinionated TDD workflow with strong checklists and feedback loops, but it over-explains testing fundamentals Claude already knows and references five detail files that are not present in the bundle.

Suggestions

Create the referenced bundle files (tests.md, mocking.md, deep-modules.md, interface-design.md, refactoring.md) or remove the dangling links, since every 'See X.md' pointer currently dead-ends.

Trim the Philosophy section's explanation of good vs bad tests and implementation coupling — Claude already knows these concepts; keep only the skill's specific stance.

Add one short worked example of a full RED→GREEN→REFACTOR cycle (a failing test, the minimal code, the passing result) to make the loop concrete rather than abstract.

Dimension	Reasoning	Score
Conciseness	The workflow and anti-pattern sections are tight and opinionated, but the Philosophy section re-explains concepts Claude already knows (what 'good' vs 'bad' tests are, why implementation-coupled tests break on refactor) and could be trimmed.	3 / 5
Actionability	Concrete, specific rules ('One test at a time', 'Only enough code to pass current test', 'Never refactor while RED') plus checklists and a WRONG/RIGHT slicing example give actionable guidance, though no worked test→impl code example is shown.	4 / 5
Workflow Clarity	A clearly sequenced four-phase workflow (Planning → Tracer Bullet → Incremental Loop → Refactor) with an inherent RED/GREEN feedback loop, explicit checkpoints ('Never refactor while RED', 'Run tests after each refactor step'), and per-cycle/planning checklists.	5 / 5
Progressive Disclosure	Sections are well-organized and references are one-level-deep and inline-signaled, but all five referenced files (tests.md, mocking.md, deep-modules.md, interface-design.md, refactoring.md) do not exist in any bundle directory, so navigation is broken.	3 / 5
	Total	15 / 20 Passed

Description

82%Weight 40%Scale 1-5

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 description with an explicit 'Use when' trigger clause and good keyword coverage, clearly distinguishing TDD from general testing skills. The only weakness is that the concrete actions listed are generic ('build features or fix bugs') rather than specific capabilities.

Dimension	Reasoning	Score
Specificity	Names the domain ('Test-driven development') and one concrete method ('red-green-refactor loop'), but the only actions offered ('build features or fix bugs') are generic rather than a comprehensive list of concrete capabilities.	3 / 5
Completeness	Explicitly states what the skill does ('Test-driven development with red-green-refactor loop') and gives a concrete 'Use when...' clause listing multiple trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	Includes several natural terms a user would say — 'TDD', 'red-green-refactor', 'integration tests', 'test-first development' — but misses common variations like 'unit tests' or related synonyms.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (TDD specifically) with distinctive triggers ('red-green-refactor', 'test-first') that are unlikely to fire for unrelated skills.	5 / 5
	Total	17 / 20 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: openstatusHQ/data-table-filters
Path: .agents/skills/tdd/SKILL.md
Commit: 5017387

Reviewed: 1 day 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.