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

79%

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 ./.claude/skills/tdd/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

73%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 process skill with an exemplary workflow structure — validation is built into every cycle and the anti-pattern guidance (horizontal vs. vertical slicing) is genuinely non-obvious and valuable. The main costs are a Philosophy section that re-teaches known concepts and the absence of a single worked RED→GREEN example, plus sidecar references that could not be verified in the bundle.

Suggestions

Compress the Philosophy section to the project's normative stance only (behavior-through-public-interfaces, integration-style) and drop the generic explanation of what bad tests do, which Claude already knows.

Include one tiny worked example of a full cycle — a behaviorally-named failing test and the minimal code that turns it green — so the loop is concrete rather than purely procedural.

Gather the five sidecar links into a short 'Reference guides' section so navigation is consolidated, and verify the sidecar files actually ship in the bundle.

DimensionReasoningScore

Conciseness

The body is mostly efficient — the anti-pattern and workflow sections are tight and earn their tokens — but the Philosophy section re-explains concepts Claude already knows ('Bad tests are coupled to implementation. They mock internal collaborators, test private methods, or verify through external means'), spanning multiple paragraphs that could be trimmed to the project's normative stance. This is more than the 'minor instances' of anchor 4.

3 / 5

Actionability

Concrete, specific guidance throughout: planning checklists with the exact question to ask ('What should the public interface look like? Which behaviors are most important to test?'), one-test-at-a-time rules, and a per-cycle checklist. It falls short of anchor 5 because it contains no worked example of a single RED→GREEN cycle (test name plus the minimal implementation that satisfies it) — everything concrete about test style is deferred to the sidecars.

4 / 5

Workflow Clarity

The multi-step process is clearly sequenced (Planning → Tracer Bullet → Incremental Loop → Refactor) with validation embedded in every step: RED must fail, GREEN must pass, 'Run tests after each refactor step', and 'Never refactor while RED. Get to GREEN first.' Combined with three checklists, this matches the anchor-5 pattern of explicit validation and feedback loops.

5 / 5

Progressive Disclosure

Good structure with one-level-deep, contextually signaled sidecar references ('See [tests.md](tests.md) for examples and [mocking.md](mocking.md) for mocking guidelines'). It does not reach anchor 5 because the five referenced sidecar files are not present in the bundle, the dense prelude interleaves six external file pointers without a consolidated navigation section, and reference signals are scattered rather than gathered.

4 / 5

Total

16

/

20

Passed

Description

78%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 with an explicit and well-enumerated trigger clause that clearly answers both what the skill does and when to use it. The main weakness is that the capability statement is a single methodology phrase, so it reads slightly thinner on distinct concrete capabilities than the best examples.

Suggestions

Enumerate one or two concrete capabilities in the 'what' clause (e.g., 'Write failing tests first, then implement minimal code to pass them, then refactor') so the description lists specific actions rather than just naming the methodology.

Add common trigger synonyms such as 'unit tests' or 'write tests first' to broaden natural keyword coverage.

DimensionReasoningScore

Specificity

The 'what' is a single methodology statement — 'Test-driven development with red-green-refactor loop' — plus trigger scenarios like 'build features or fix bugs' and 'wants integration tests'. This names the domain and 1-2 concrete actions without comprehensively listing distinct capabilities, matching anchor 3 rather than anchor 4's 'several specific actions'.

3 / 5

Completeness

It clearly answers both 'what' ('Test-driven development with red-green-refactor loop') and 'when' via an explicit 'Use when...' clause with concrete trigger phrases ('mentions "red-green-refactor"', 'asks for test-first development'), matching the anchor-5 good example. It is not 4 because the 'when' is specific and enumerated, not merely present.

5 / 5

Trigger Term Quality

Natural trigger phrases are present: 'TDD', 'red-green-refactor', 'test-first development', 'integration tests'. It falls short of anchor 5 because common variations such as 'unit tests', 'write tests first', or 'test coverage' are missing.

4 / 5

Distinctiveness Conflict Risk

Triggers like 'red-green-refactor' and 'test-first development' carve a clear niche with minimal conflict risk, but the broad 'build features or fix bugs' phrasing could overlap with general coding or debugging skills, keeping it at anchor 4 rather than 5.

4 / 5

Total

16

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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: 3 possibly missing (scripts/guards.config.sh, scripts/tdd-pairing-guard-ci.sh, scripts/tdd-pairing-guard.sh)

Warning

Total

14

/

16

Passed

Repository

agranado2k/google-books-clojure

Path

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