skill-tdd

Build features with tests-before-code rigor — use for new features needing test coverage

Quality

66%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/skill-tdd/SKILL.md

Quality

Content

70%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 excels at workflow clarity with strong validation checkpoints and concrete examples, and is largely actionable. It is held back by repeated compliance rhetoric and the absence of any progressive disclosure via bundle files despite its length.

Suggestions

Consolidate the redundant 'no code before test / delete it' messaging from MANDATORY COMPLIANCE, Iron Law, Red Flags, and The Bottom Line into a single authoritative section to recover tokens.

Move the longer worked examples or the integration-with-octopus table into a reference file under references/ and link to it from SKILL.md to add progressive disclosure.

Replace the orchestrate.sh placeholder block with a concrete, runnable invocation or move the dispatch mechanics into a script file referenced by name.

Dimension	Reasoning	Score
Conciseness	The body avoids explaining concepts Claude already knows, but restates the 'no code without a test / delete it' rule across MANDATORY COMPLIANCE, Iron Law, Red Flags, and The Bottom Line, producing noticeable rhetorical padding that could be consolidated.	3 / 5
Actionability	It provides executable TypeScript examples, concrete 'npm test' commands, good/bad contrasts, and a full bug-fix walkthrough; minor gaps (e.g. the orchestrate.sh dispatch snippet is a template with a placeholder) keep it just below fully copy-paste ready.	4 / 5
Workflow Clarity	The Red-Green-Refactor cycle is explicitly sequenced with mandatory VERIFY checkpoints at each phase, outcome→action tables for error recovery, and a completion checklist, matching the anchor for clear sequence with explicit validation and feedback loops.	5 / 5
Progressive Disclosure	No references/, scripts/, or assets/ bundle files exist; the skill is a single ~310-line SKILL.md with clear section headers but all content inlined and no one-level-deep reference split, so structure is present but disclosure is not used.	3 / 5
	Total	15 / 20 Passed

Description

62%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 concise and clearly distinguishes TDD via test-first discipline, with an explicit 'use for' trigger. Its main weakness is narrow trigger-term coverage and a single named action rather than a fuller capability list.

Suggestions

Add natural trigger synonyms users actually say, e.g. 'unit tests', 'TDD', or 'test-first development'.

Consider naming one or two more concrete capabilities (e.g. 'write failing tests, then minimal implementation, then refactor') to lift specificity.

Tighten the 'when' clause with concrete scenarios, e.g. 'use when adding a new function, fixing a bug, or extending behavior that needs regression coverage'.

Dimension	Reasoning	Score
Specificity	The phrase 'Build features with tests-before-code rigor' names the TDD domain and one concrete method (tests-before-code), but lists only a single action rather than several specific actions, matching the anchor for 1-2 concrete actions.	3 / 5
Completeness	It answers both what ('Build features with tests-before-code rigor') and when ('use for new features needing test coverage'); the 'when' is explicit via 'use for' but could be more specific about trigger scenarios, fitting the 'both present, when could be more explicit' anchor.	4 / 5
Trigger Term Quality	It surfaces natural terms like 'tests', 'test coverage', and 'new features', but omits common synonyms users would say such as 'unit tests', 'TDD', or 'test-first', leaving relevant keyword variations missing.	3 / 5
Distinctiveness Conflict Risk	'tests-before-code' / 'test coverage' is a fairly distinct TDD niche unlikely to fire for unrelated skills, with only minor overlap risk against general testing skills.	4 / 5
	Total	14 / 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: nyldn/claude-octopus
Path: skills/skill-tdd/SKILL.md
Commit: 242e51d

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.