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.

Quality

80%

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

73%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, actionable TDD guide with a strong validated workflow and concrete code throughout. Its main weakness is conciseness: several sections restate software-design concepts Claude already knows rather than staying lean.

Suggestions

Trim the Philosophy and 'deep modules' explanations to the TDD-specific guidance, cutting general software-design prose Claude already knows.

Consider moving the detailed Type Testing section (utilities, negative tests, tips) into a reference file referenced from SKILL.md to reduce body length and improve progressive disclosure.

Tighten the Mocking and Interface Design sections to rely more on the code examples and less on surrounding exposition.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and code-forward, but the Philosophy, anti-pattern, and 'deep modules' sections spend tokens explaining general software-design concepts a competent model already knows, which could be tightened.	3 / 5
Actionability	It provides executable TypeScript examples, concrete commands like 'bun typecheck', and a concrete bug-fix RED/GREEN walkthrough, with only minor gaps where guidance stays at the illustrative level.	4 / 5
Workflow Clarity	The workflow is clearly sequenced (Planning, Tracer Bullet, Incremental Loop, Refactor) with explicit validation checkpoints ('confirm it FAILS correctly', 'confirm it PASSES', 'Verify all other tests still pass') and a per-cycle checklist.	5 / 5
Progressive Disclosure	The single SKILL.md is well-organized into clearly headed sections with no bundle files to mismanage, though at ~326 lines the detailed Type Testing section could plausibly live in a separate reference for better separation.	4 / 5
	Total	16 / 20 Passed

Description

87%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 strong: it pairs a concrete statement of capability with an explicit, multi-trigger 'Use when' clause and distinctive TDD-specific keywords. Its only minor weakness is slightly broader phrasing where a few additional natural synonyms could round out the trigger list.

Dimension	Reasoning	Score
Specificity	The description names the TDD domain and lists several concrete actions ('build features or fix bugs using TDD', 'wants integration tests', 'test-first development'), with only minor coverage gaps versus the comprehensive anchor.	4 / 5
Completeness	It clearly states what the skill does ('Test-driven development with red-green-refactor loop') and gives an explicit 'Use when...' clause with concrete trigger phrases covering multiple user intents.	5 / 5
Trigger Term Quality	It surfaces natural terms a user would say ('TDD', 'red-green-refactor', 'integration tests', 'test-first development'), with good keyword coverage though a few natural synonyms (e.g. 'write tests first') are absent.	4 / 5
Distinctiveness Conflict Risk	It carves a clear TDD niche with distinctive triggers ('red-green-refactor', 'test-first development') that are unlikely to fire for unrelated skills, minimizing conflict risk.	5 / 5
	Total	18 / 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: udecode/plate
Path: .agents/skills/tdd/SKILL.md
Commit: d76efae

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.