CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

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.

An excellent instruction-style skill body: lean, imperative, and free of padding, with a clearly sequenced cycle that embeds validation and error-recovery at each step. The only minor gap is the absence of a concrete example (e.g., a sample test name or run command) that would make the guidance fully copy-paste ready.

DimensionReasoningScore

Conciseness

The body is lean and dense — "Red. Green. Refactor. In that order, every time." — with no explanation of concepts Claude already knows, compact tables for anti-patterns, and every rule stated once without padding; every token earns its place.

5 / 5

Actionability

Concrete, executable guidance throughout: per-step rules ("The test must fail for the right reason — a missing method, wrong return value, unmet condition"), a copy-paste-ready command (`npx ai-devkit@latest memory store ...`), and explicit `verify` skill hooks. It falls just short of fully executable because it gives no example test name or concrete test-run command.

4 / 5

Workflow Clarity

The Red/Green/Refactor cycle is a clearly sequenced workflow with explicit validation at every step ("Run it. It must fail", "Run the test again. Still green? Done.") and error-recovery feedback loops ("If the test passes immediately... Delete it or pick a different behavior"), matching the top anchor.

5 / 5

Progressive Disclosure

The skill is a single-task, self-contained document (~62 lines) with well-organized sections and no bundle files; nothing here needs splitting into references, so the structure fully satisfies the simple-skill case for progressive disclosure.

5 / 5

Total

19

/

20

Passed

Description

66%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 concise, well-structured description with an explicit trigger clause and natural language, free of fluff and over-claims. Its main weaknesses are a single-action "what" that undersells the full TDD cycle and overly broad triggers that could fire on almost any coding task.

Suggestions

Expand the capability statement to name the full cycle, e.g. "write a failing test, implement the minimum code to pass it, then refactor — in that order".

Add natural trigger synonyms such as "unit tests", "test-first", or "write the test first" to improve keyword coverage.

Narrow the 'Use when' clause to distinguish TDD from ordinary implementation work, e.g. "Use when the user asks for test-driven development or test-first implementation, not for routine feature work".

DimensionReasoningScore

Specificity

The description names the TDD domain and one concrete action ("write a failing test before writing production code") but does not list several specific actions such as the green/refactor steps, matching the 'names domain and 1-2 concrete actions' anchor rather than the 'several specific actions' anchor.

3 / 5

Completeness

Both halves are present: a clear "what" (write a failing test before production code) and an explicit "Use when..." clause with concrete triggers. The "when" is strong but the "what" is thin — it covers only the test-first rule and not the broader cycle — so it falls just below the 'clearly and explicitly answers both' top anchor.

4 / 5

Trigger Term Quality

Natural phrases like "test-driven development", "failing test", "implementing new functionality", and "fixing bugs" map well to what users would say, but common synonyms such as "unit test", "test first", or "write tests" are missing, placing it at good-but-not-comprehensive coverage.

4 / 5

Distinctiveness Conflict Risk

The TDD niche itself is distinct, but the trigger conditions ("implementing new functionality, adding behavior, or fixing bugs during active development") describe nearly all active development work, creating real overlap risk with general coding and verification skills; it fits 'somewhat specific but could still overlap with similar skills'.

3 / 5

Total

14

/

20

Passed

Validation

100%

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

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.