tdd-test-writer
Writes failing tests first for test-driven development and hands off a strict implementation contract that requires agents to make those tests pass without weakening the tests. Use when users ask for test-first workflows, RED/GREEN cycles, or behavior-gating tasks with automated tests.
Install with Tessl CLI
npx tessl i github:am-will/codex-skills --skill tdd-test-writer100
Does it follow best practices?
Validation for skill structure
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-crafted skill description that excels across all dimensions. It clearly articulates the TDD-specific workflow (writing failing tests first, enforcing implementation contracts), uses natural terminology that developers would actually say, and includes an explicit 'Use when...' clause with multiple trigger scenarios. The description is distinctive enough to avoid conflicts with general testing or coding skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Writes failing tests first', 'hands off a strict implementation contract', 'requires agents to make those tests pass without weakening the tests'. These are clear, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what (writes failing tests, hands off implementation contract) AND when with explicit 'Use when...' clause covering 'test-first workflows, RED/GREEN cycles, or behavior-gating tasks with automated tests'. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'test-driven development', 'test-first workflows', 'RED/GREEN cycles', 'behavior-gating tasks', 'automated tests'. Good coverage of TDD terminology and variations. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on TDD workflows with distinct triggers like 'RED/GREEN cycles' and 'behavior-gating'. Unlikely to conflict with general testing or code generation skills due to the specific test-first methodology focus. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent skill that demonstrates strong TDD workflow guidance. It's concise yet comprehensive, with clear sequencing, explicit validation steps, and a well-defined handoff format. The skill respects Claude's intelligence while providing the specific constraints and output structure needed for reliable execution.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, avoiding explanations of concepts Claude already knows (TDD, testing frameworks). Every section serves a purpose with no padding or unnecessary context. | 3 / 3 |
Actionability | Provides concrete, specific guidance throughout: exact workflow steps, required output format with template, specific constraints like 'do not modify production code', and clear verification commands. The handoff template is copy-paste ready. | 3 / 3 |
Workflow Clarity | Clear 6-step sequence with explicit validation checkpoint (Step 5: Verify RED State) and feedback loop ('If failure is caused by test syntax/setup, fix tests and rerun'). The workflow handles error recovery and has clear completion criteria. | 3 / 3 |
Progressive Disclosure | Well-organized with clear sections (When To Use, Required Rules, Workflow, Output Format, Quality Bar). Content is appropriately structured for a single-file skill under reasonable length with no need for external references. | 3 / 3 |
Total | 12 / 12 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 — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- 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.