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

83%

Does it follow best practices?

Impact

96%

1.18x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

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

Quality

Content

77%

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

The body is well-structured and actionable with a clear validated workflow, but it is somewhat verbose in its philosophy section and, more importantly, references five bundle files that are not present in the skill bundle, leaving its progressive-disclosure links broken.

Suggestions

Tighten the Philosophy section: replace the multi-paragraph good/bad tests explanation with a compact behavior-vs-implementation rule and one short warning sign, and trim the ASCII WRONG/RIGHT diagram to a single-line contrast.

Resolve the dangling references: either add the missing tests.md, mocking.md, deep-modules.md, interface-design.md, and refactoring.md under references/, or remove the inline links and inline any content that is essential to the workflow.

Keep only the references the workflow actually depends on for its core steps, so the overview points to a small, real set of supporting files rather than five unresolved links.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and skill-specific, but the Philosophy section restates behavior-vs-implementation coupling that an experienced Claude largely knows, and the ASCII WRONG/RIGHT diagram plus verbose anti-pattern prose add tokens that could be tightened without losing the point.	2 / 3
Actionability	Concrete, executable guidance throughout: a planning checklist, a one-test tracer-bullet step, an incremental RED/GREEN loop with explicit rules, a refactor checklist, and a per-cycle checklist — all specific and directive for an instruction-only skill.	3 / 3
Workflow Clarity	The four-phase sequence (Planning, Tracer Bullet, Incremental Loop, Refactor) is clearly ordered with built-in validation feedback loops (RED fails → GREEN passes), an explicit 'run tests after each refactor step' checkpoint, and a 'never refactor while RED' guard.	3 / 3
Progressive Disclosure	References are one level deep and inline-signaled (tests.md, mocking.md, deep-modules.md, interface-design.md, refactoring.md), but none of these bundle files exist under references/, scripts/, or assets/, so the links are dangling and navigation breaks.	2 / 3
	Total	10 / 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-formed description with explicit what-and-when structure, third-person voice, and naturally phrased trigger terms. Its only weakness is that the named actions are somewhat generic development verbs rather than concrete, methodology-specific operations.

Dimension	Reasoning	Score
Specificity	Names the domain (TDD, red-green-refactor) and several actions (build features, fix bugs, integration tests, test-first development), but the actions themselves are generic development verbs rather than the concrete mechanical operations the rubric's top anchor exemplifies.	2 / 3
Completeness	Explicitly answers both what ('Test-driven development with red-green-refactor loop') and when ('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').	3 / 3
Trigger Term Quality	Natural user-facing triggers are well covered: 'TDD', 'red-green-refactor', 'integration tests', and 'test-first development' are exactly the phrases a user requesting this skill would say.	3 / 3
Distinctiveness Conflict Risk	The distinctive triggers (red-green-refactor, test-first development) carve out a clear TDD niche, so it is unlikely to fire for non-TDD feature/bug work despite the broad 'build features or fix bugs' phrasing.	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: openstatusHQ/data-table-filters
Path: .agents/skills/tdd/SKILL.md
Commit: f1cbf2f

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