CtrlK
BlogDocsLog inGet started
Tessl Logo

agentic-tdd

Use whenever implementing changes with red-green-refactor, TDD, BDD, ATDD, or related test-first workflows. Guides refactoring timing and the final test-cleanup pass.

63

Quality

74%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/instruction/agentic-tdd/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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.

A tight, well-structured instruction skill that lays out the red-green-refactor-tidy cycle with clear sequencing and built-in validation checkpoints. It is slightly verbose in places and could benefit from a concrete worked example of one slice to anchor the abstract 'seam' language.

Suggestions

Add one short worked example of a single red-green-refactor-tidy slice to make the abstract 'seam' concept concrete.

Tighten the 'Tidy by default' bullet, which is the longest and could lose some explanatory padding without losing meaning.

DimensionReasoningScore

Conciseness

Lean body that assumes Claude knows TDD and avoids re-explaining concepts; the explanatory clauses within bullets earn their place but could be trimmed slightly.

4 / 5

Actionability

Concrete, directive prose ('Write and run the failing test first', 'One seam, one test, one minimal implementation per cycle') gives actionable guidance for an instruction-only skill, with minor gaps in concrete examples.

4 / 5

Workflow Clarity

Clear red-green-refactor-tidy sequence with explicit checkpoints ('Confirm that it fails for the expected reason', 'only after the test passes') and an error-recovery loop ('If it already passes, check whether the behavior already exists'); not a full checklist so not a 5.

4 / 5

Progressive Disclosure

Under 50 lines, single-purpose, no external references needed, and well-organized with a header plus four labeled principle bullets; meets the simple-skill exception for a top score.

5 / 5

Total

17

/

20

Passed

Description

70%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 concise, well-triggered description that clearly signals when to use the skill via natural TDD-family keywords. It is somewhat thin on the 'what' side, naming only refactoring timing and the cleanup pass rather than the full red-green-refactor-tidy cycle it guides.

Suggestions

Expand the 'what' to name the full cycle it guides (e.g. 'Guides the red-green-refactor-tidy cycle: writing failing tests first, minimal implementation, refactoring timing, and final test cleanup').

Add a natural-language phrasing such as 'writing tests first' alongside the acronyms to broaden trigger coverage.

DimensionReasoningScore

Specificity

Names the TDD/test-first domain and a couple of concrete actions ('Guides refactoring timing and the final test-cleanup pass'), but coverage of what the skill does is not comprehensive.

3 / 5

Completeness

Explicit 'Use whenever...' clause answers 'when' concretely and the second sentence answers 'what'; the 'what' could be slightly more specific about the full cycle it guides.

4 / 5

Trigger Term Quality

Good keyword coverage with natural terms and synonyms ('red-green-refactor, TDD, BDD, ATDD, test-first workflows'), though a few natural phrasings like 'writing tests first' are absent.

4 / 5

Distinctiveness Conflict Risk

Clear TDD/test-first niche with distinctive triggers and minimal conflict risk; only minor overlap with general testing/coding skills.

4 / 5

Total

15

/

20

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
choegyumin/agent-skills
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.