CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

tdd

TDD loop, one vertical slice at a time (red, green, refactor). Trigger: test-first development, TDD.

Quality

82%

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

SKILL.md
Quality
Evals
Security

Quality

Content

75%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 lean, well-organized process reference with concrete rules and a clearly sequenced red→green loop. Its main defects are that both files it references are absent from the bundle (breaking the disclosure chain) and that the loop's verification checkpoint is left implicit.

Suggestions

Ship tests.md and mocking.md in the skill bundle (or remove the references from SKILL.md): the body links to both, but neither file exists alongside SKILL.md, so the promised examples and mocking guidelines are unreachable.

Add a minimal worked example of one full red→green cycle (a named seam, the failing test, then the minimal implementation) directly in the body so the loop is concrete even without the external example file.

Make the loop's verification checkpoint explicit — e.g., "run the test and confirm it fails for the expected reason before writing any implementation" — rather than leaving the red-phase gate implicit in "Red before green".

DimensionReasoningScore

Conciseness

The body is lean, prescriptive doctrine ("No test is written at an unconfirmed seam", "One seam, one test, one minimal implementation per cycle") with only minor over-explanation of standard testing wisdom Claude already knows ("A good test reads like a specification… it survives refactors because it doesn't care about internal structure"). Not 5 because a few such passages could be trimmed; not 3 because padding is minor rather than a pattern.

4 / 5

Actionability

Concrete, executable directives are present: "Before writing any test, write down the seams under test and confirm them with the user", a copy-paste question ("What's the public interface, and which seams should we test?"), and a concrete tautology example ("expect(add(a, b)).toBe(a + b)"). Not 5 because no worked red→green cycle example exists in the body and the examples are delegated to tests.md, which is not in the bundle; not 3 because the guidance given is specific and directive, not pseudocode or vague hints.

4 / 5

Workflow Clarity

The loop is clearly sequenced with the failing test as a gate: "Red before green. Write the failing test first, then only enough code to pass it", plus the rule that changes to existing code start a new cycle. Not 5 because the verification checkpoint is implicit — it never says to run the test and confirm it fails for the expected reason before writing implementation; not 3 because the sequence and its checkpoints are mostly explicit and this is not a destructive/batch operation.

4 / 5

Progressive Disclosure

The body is short and well-sectioned with clearly signaled, one-level-deep references ("See [tests.md](tests.md) for examples and [mocking.md](mocking.md) for mocking guidelines"). Held below 5 — and straining the 4 anchor — because neither referenced file exists in the bundle (no references/, scripts/, or assets/ directories are present), so navigation to the delegated examples and mocking guidance is broken; not 3 because the in-file structure and reference signaling are good and nothing that belongs in separate files is inlined.

4 / 5

Total

16

/

20

Passed

Description

82%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: it explicitly states what the skill does and when to use it, with natural trigger terms in a distinct TDD niche. Its only weakness is terseness on the "what" side — it names the process without enumerating the skill's actual coverage (seams, anti-patterns, loop rules).

DimensionReasoningScore

Specificity

"TDD loop, one vertical slice at a time (red, green, refactor)" names the domain and the loop's phases but stops at naming a single process rather than listing several concrete actions, and it omits the body's actual coverage (seams, anti-patterns, loop rules). Matches anchor 3; not 4 because it lacks the several distinct actions of anchor 4, and not 2 because it is more than a bare domain mention.

3 / 5

Completeness

Both questions are answered explicitly: what — "TDD loop, one vertical slice at a time (red, green, refactor)"; when — "Trigger: test-first development, TDD", an explicit trigger clause with concrete trigger phrases. Not 4 because the "when" is fully explicit rather than merely present or weakly implied.

5 / 5

Trigger Term Quality

"Trigger: test-first development, TDD" supplies exactly the natural phrases a user would say when needing this skill. Not 5 because common variations are missing ("write tests first", "test-driven development" spelled out, "red-green-refactor" as a trigger phrase); not 3 because the terms present are natural user language, not generic.

4 / 5

Distinctiveness Conflict Risk

"test-first development, TDD" carves a clear niche with distinct triggers; a request to just write tests or review code would not fire this skill. Minimal conflict risk, matching anchor 5; not 4 because the triggers are specific to the TDD methodology rather than a broad testing domain.

5 / 5

Total

17

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

relative_links

Relative link issues: 2 missing

Warning

Total

15

/

16

Passed

Repository

YoizenSA/dev-ai-workflow

Path

ywai/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.