tdd

AI DevKit · Test-driven development — write a failing test before writing production code. Use when implementing new functionality, adding behavior, or fixing bugs during active development.

Quality

87%

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

Quality

Content

92%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.

The content is a well-structured, lean instruction-only skill with a clear validated workflow and strong actionable rules. The only minor gap is the absence of executable code examples, which is partly justified by the instruction-only nature.

Dimension	Reasoning	Score
Conciseness	The body is lean and imperative with no over-explanation of TDD concepts Claude already knows; every line earns its place, matching the top anchor.	5 / 5
Actionability	Guidance is concrete and specific ("delete it and start over", "Hardcode if needed", "Name the test after what the system should do"), but as an instruction-only skill it lacks executable examples, leaving minor gaps versus the fully copy-paste-ready top anchor.	4 / 5
Workflow Clarity	The Red-Green-Refactor cycle is explicitly sequenced with run-the-test validation checkpoints in each step, a "Still green? Done" feedback loop, and a verify-skill gate, matching the top anchor.	5 / 5
Progressive Disclosure	With no bundle files and a single-purpose skill organized into clear sections (Hard Rules, Cycle, Rules for Each Step, Anti-Patterns), it qualifies for the simple-skill exception at the top anchor.	5 / 5
	Total	19 / 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.

The description is concise, third-person, and clearly answers both what the skill does and when to use it with explicit trigger phrases. It could enumerate more concrete cycle actions to raise specificity.

Dimension	Reasoning	Score
Specificity	Names the domain (test-driven development) and one concrete action ("write a failing test before writing production code"), but does not enumerate the broader cycle actions, matching the 1-2 concrete-actions anchor.	3 / 5
Completeness	It explicitly answers both what (test-driven development, failing-test-first) and when (concrete "Use when" trigger clause with multiple scenarios), matching the top anchor.	5 / 5
Trigger Term Quality	The "Use when implementing new functionality, adding behavior, or fixing bugs" clause covers natural developer phrases, though it lacks synonyms or broader variations, fitting just above the 3 anchor.	4 / 5
Distinctiveness Conflict Risk	TDD is a distinct niche with clearly tied trigger phrases and minimal overlap risk with other skills.	5 / 5
	Total	17 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: codeaholicguy/ai-devkit
Path: skills/tdd/SKILL.md
Commit: d56e554

Reviewed: 3 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.