tdd

Test-driven development and testing patterns for Rails applications. Drives implementation from tests using an outside-in approach with RSpec, Capybara, and FactoryBot. Use when building new features, writing or improving tests, adding test coverage, fixing bugs with a test-first workflow, or when the user mentions TDD, test-driven, test-first, outside-in, spec plan, RSpec, Capybara, system specs, model specs, testing patterns, writing tests, or improving test coverage.

Quality

92%

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.

Excellent instructional content: a well-sequenced TDD workflow with genuine validation checkpoints, copy-paste-ready commands and templates, and a clean overview-plus-references structure where every referenced file exists. The only improvement space is trimming the philosophy sections that restate testing knowledge Claude already has.

Dimension	Reasoning	Score
Conciseness	The body is dense and mostly earns its tokens (process steps, commands, spec-plan template, decision table), but sections like 'Tests as documentation' with its Given/When/Then bullet explanation and 'DAMP over DRY' spend lines explaining testing background Claude already knows — minor over-explanation, matching anchor 4 rather than anchor 5's every-token-earns-its-place.	4 / 5
Actionability	Fully executable throughout: concrete rspec invocations including line-number and '-e' filtering, a complete copy-paste spec-plan markdown template, a layered what-gets-its-own-spec decision table, and a precise Prove-It bug pattern with 'write a test that reproduces the bug' — matches anchor 5's copy-paste-ready coverage of common cases.	5 / 5
Workflow Clarity	The five-step process has explicit validation checkpoints: 'confirm it fails for the right reason (missing route, missing method, missing template), not a syntax error', stop-and-review gates after the plan and first test, re-reading the spec after user edits, and a final completeness plus regression check ('run every spec listed in the Related specs section'). This matches anchor 5's explicit validation steps and error-recovery loops.	5 / 5
Progressive Disclosure	SKILL.md is an overview with per-reference bullet summaries ('Read the appropriate reference before writing a new spec'), and all three referenced files — references/system_spec.rb, references/model_spec.rb, references/spec_conventions.md — exist in the bundle and are one level deep with clear section-by-section pointers, matching anchor 5.	5 / 5
	Total	19 / 20 Passed

Description

91%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 explicit what and when clauses, rich natural trigger terms, and third-person voice. The only gaps are a slightly thin concrete-action list and a few generic trigger phrases that could overlap with non-Rails testing requests.

Dimension	Reasoning	Score
Specificity	Names the domain (Rails TDD) with several concrete actions and tools — 'Drives implementation from tests using an outside-in approach with RSpec, Capybara, and FactoryBot' and 'fixing bugs with a test-first workflow' — but the action list is thinner than anchor 5, which expects comprehensive concrete actions; the bulk of the description is trigger phrases rather than capabilities.	4 / 5
Completeness	Explicitly answers both questions: what ('Test-driven development and testing patterns for Rails applications. Drives implementation from tests using an outside-in approach with RSpec, Capybara, and FactoryBot') and when ('Use when building new features, writing or improving tests... or when the user mentions TDD...'). Structurally matches the anchor-5 example exactly.	5 / 5
Trigger Term Quality	Comprehensive natural trigger coverage: 'TDD, test-driven, test-first, outside-in, spec plan, RSpec, Capybara, system specs, model specs, testing patterns, writing tests' plus scenario phrasings like 'building new features' and 'adding test coverage'. Covers synonyms and natural user phrasings fully, matching the anchor-5 pattern.	5 / 5
Distinctiveness Conflict Risk	Rails-scoped with distinct tool triggers (RSpec, Capybara, FactoryBot), but generic phrases like 'writing or improving tests, adding test coverage' could fire for testing requests in any stack — minor overlap risk with a general test-writing skill, matching anchor 4 rather than anchor 5's minimal conflict.	4 / 5
	Total	18 / 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
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning

	Total	15 / 16 Passed

Repository: RoleModel/rolemodel-skills
Path: skills/tdd/SKILL.md
Commit: cb80143

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