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

80%

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

The canonical home for this skill is tdd in agranado2k/google-books-clojure

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 strong, opinionated process skill: clear sequencing, explicit validation gates, useful checklists, and disciplined delegation of detail to sidecars and project files. Its weaknesses are modest — some restateable testing doctrine, executable specifics (runner command, naming convention) living one hop away, no error-recovery branches, and referenced sidecar files that are absent from the bundle as shipped.

Suggestions

Add brief error-recovery guidance to the workflow (e.g., what to do when the tracer-bullet test cannot reach GREEN, or when a refactor step breaks the suite — revert and re-run before continuing).

State the test-runner command and file-naming convention inline (even one line each) so a reader can execute the first RED step without opening constitution/local-engineering.md.

Tighten the Philosophy section's Good/Bad tests paragraphs into a few bullet rules; the horizontal-slicing rationale could likewise compress without losing the directive force.

Ensure the five referenced sidecar files (tests.md, mocking.md, deep-modules.md, interface-design.md, refactoring.md) actually ship alongside SKILL.md — they are linked but missing from the bundle.

DimensionReasoningScore

Conciseness

The body is dense and directive — the project-context prelude is high-value pointer content, and rules like "Never refactor while RED" and "A test that cannot fail is worse than no test" earn their tokens. Minor over-explanation remains (the Good/Bad tests paragraphs and the horizontal-slicing rationale restate testing doctrine Claude broadly knows), matching the score-4 anchor of efficient content with trimmable instances. It is not 5 because those doctrinal paragraphs could be tightened, and not 3 because there is no library- or concept-level padding.

4 / 5

Actionability

Concrete, executable guidance dominates: explicit RED→GREEN sequences, a planning checklist ("Confirm with user what interface changes are needed"), per-cycle rules ("One test at a time", "Only enough code to pass current test"), and the pointer "scripts/guards.config.sh. Those two regexes are the machine-readable version of 'this change needed a test'". Per the scoring note for instruction-only skills, absent code is not penalized since the guidance is actionable; it stops short of 5 because the most executable details (the runner command, the file-naming convention) are delegated to external files rather than stated, so the reader must hop before executing anything.

4 / 5

Workflow Clarity

The Planning → Tracer Bullet → Incremental Loop → Refactor sequence is clearly laid out with real validation checkpoints: "Write test for first behavior → test fails", "Run tests after each refactor step", "Never refactor while RED", and "a refactor-only pass is its own commit, with the suite green before and after", plus three explicit checklists. It misses 5 because there are no error-recovery feedback loops (e.g., what to do when the tracer-bullet test cannot go green, or when a refactor step breaks the suite); it is well above 3 since checkpoints are explicit, not implicit.

4 / 5

Progressive Disclosure

The file is a well-organized overview with clearly signaled one-level-deep references: "See [tests.md](tests.md) for examples and [mocking.md](mocking.md) for mocking guidelines", plus deep-modules.md, interface-design.md, and refactoring.md linked with stated purposes in the footer. However, none of the five referenced sidecar files exist in the skill's bundle (no references/ directory and no sibling .md files), so the one-level-deep promise cannot be verified — the structure matches score 4's "minor organization gaps" rather than 5's fully navigable split.

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 well-constructed description with an explicit and concrete "Use when" clause covering multiple natural trigger phrasings, and a clear niche. The main weakness is the "what" half: it names the methodology and its loop but does not list the specific actions the skill performs, leaving specificity as the lowest dimension.

Suggestions

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

Add missing natural trigger variations such as "unit tests" or "write the tests first" to broaden keyword coverage.

DimensionReasoningScore

Specificity

"Test-driven development with red-green-refactor loop" names the domain and its core cycle but never enumerates concrete actions (e.g., write a failing test, implement minimal code, refactor) — matching the anchor for domain plus 1-2 concrete elements without comprehensive coverage. It is above score 2 because "red-green-refactor loop" is a concrete, specific mechanism rather than a generic action, but below 4 because no list of specific actions is provided.

3 / 5

Completeness

The description explicitly answers both questions: what ("Test-driven development with red-green-refactor loop") and when ("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") with concrete trigger phrases. This directly matches the score-5 anchor and example structure; no "when" clause is missing or merely implied.

5 / 5

Trigger Term Quality

Triggers include "build features or fix bugs using TDD", "mentions 'red-green-refactor'", "wants integration tests", and "asks for test-first development" — natural phrases users would say, with good synonym coverage (TDD, test-first, red-green-refactor). It falls short of 5 because common variations like "unit tests", "write the tests first", or "test coverage" are absent; it is clearly above 3 since multiple natural terms and synonyms are present.

4 / 5

Distinctiveness Conflict Risk

TDD with "red-green-refactor" triggers carves a clear niche with minimal conflict risk against unrelated skills. It is not 5 because the standalone trigger "wants integration tests" is broad enough to overlap with a general testing skill; it is well above 3 because the dominant triggers (TDD, red-green-refactor, test-first) are unmistakably specific to this skill.

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/tic-tac-toe-with-agentic-sdlc

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.