CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/tdd/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

81%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 well-crafted procedural skill body: the workflow is explicitly sequenced with validation gates and checklists, and the project-context prelude adds genuinely non-generic information. The main gaps are minor — slight repetition between the prelude and Planning section, and sidecar references that are linked inline rather than presented as labeled navigation.

DimensionReasoningScore

Conciseness

The body is dense and assumes competence — the project-context prelude delivers specific, non-generic pointers (file paths, hook names, failure modes) rather than textbook padding. Minor over-explanation remains: the domain-glossary and ADR pointers from the prelude are repeated in the Planning section, and "a test that cannot fail is worse than no test" is stated twice. Not 5 because a few of these spots could be trimmed; not 3 because nothing reads as filler Claude already knows.

4 / 5

Actionability

Concrete, executable guidance throughout: the copy-paste-ready `sh scripts/trace.sh emit ...` command with exact arguments, the WRONG/RIGHT horizontal-vs-vertical diagram, per-cycle checklists, and quoted planning questions. It stops short of 5 because there is no example test or runner command in the file itself — the runner command is deliberately deferred to `constitution/local-engineering.md`, leaving a gap if that file isn't consulted.

4 / 5

Workflow Clarity

The sequence (Planning → Tracer Bullet → Incremental Loop → Refactor) is explicit with validation checkpoints at every stage: RED must fail before GREEN, "Run tests after each refactor step", "Never refactor while RED", and the suite green before and after the refactor-only commit. Checklists for planning, refactoring, and each cycle, plus feedback-loop rules ("Only enough code to pass current test"), match the top anchor.

5 / 5

Progressive Disclosure

The overview is a lean ~130-line procedure with one-level-deep sidecar references (tests.md, mocking.md, deep-modules.md, interface-design.md, refactoring.md) and project-context pointers, so no nested-reference problem exists. It falls below 5 because the links are embedded mid-sentence in checklists rather than clearly labeled navigation sections, and none of the referenced sidecar files are present in the provided bundle to verify they resolve. Not 3: the references are clearly signaled and no content that belongs in a sidecar is inlined.

4 / 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, third-person description with an explicit and well-phrased trigger clause. Its main weakness is a thin "what" — it names the methodology but doesn't enumerate the concrete actions the skill performs, leaving specificity and completeness just short of the top anchors.

Suggestions

Enumerate 2-3 concrete actions in the "what" clause, e.g., "Write one failing test at a time, implement the minimal code to pass it, then refactor with the suite green".

Add common trigger synonyms such as "write tests first" or "unit tests" alongside the existing TDD-specific terms.

Narrow the "wants integration tests" trigger (e.g., "wants integration tests written test-first") to reduce overlap with a generic testing skill.

DimensionReasoningScore

Specificity

"Test-driven development with red-green-refactor loop" names the domain and one concrete mechanism but enumerates no further actions (e.g., writing failing tests first, minimal implementation, refactoring passes), matching the anchor for 1-2 concrete actions without comprehensive coverage. It does not reach 4 because no list of specific actions is present.

3 / 5

Completeness

Both parts are present: the "what" ("Test-driven development with red-green-refactor loop") and an explicit "Use when..." clause with concrete triggers. It falls below 5 because the "what" is a single bare methodology name rather than a clear enumeration of what the skill does.

4 / 5

Trigger Term Quality

Natural user phrasings are well covered: "TDD", "red-green-refactor", "integration tests", "test-first development", "build features or fix bugs". A few natural variants ("unit tests", "write tests first", "test coverage") are missing, which keeps it below the comprehensive-synonyms anchor.

4 / 5

Distinctiveness Conflict Risk

Triggers like "red-green-refactor" and "test-first development" carve a clear niche distinct from general coding skills. Minor overlap risk remains: "wants integration tests" could fire for a user who wants tests written without the TDD loop, matching the mostly-distinct anchor.

4 / 5

Total

15

/

20

Passed

Validation

75%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 12 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

metadata_version

'metadata.version' is missing

Warning

relative_links

Relative link issues: 5 possibly missing (deep-modules.md, interface-design.md, mocking.md, refactoring.md, tests.md)

Warning

referenced_paths_exist

Referenced path issues: 4 possibly missing (scripts/guards.config.sh, scripts/tdd-pairing-guard-ci.sh, scripts/tdd-pairing-guard.sh, scripts/trace.sh)

Warning

Total

12

/

16

Passed

Repository

agranado2k/agentic-sdlc

Path

.agents/skills/tdd/SKILL.md

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.