CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

67

Quality

81%

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

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.

The content is a well-structured, lean methodology skill with a clear sequenced workflow, explicit validation gates, and actionable checklists. Its main weaknesses are minor padding in the closing anecdote and dead reference links pointing to files that are not present in the bundle.

Suggestions

Create the referenced bundle files (tests.md, mocking.md, deep-modules.md, interface-design.md, refactoring.md) or remove the dead links, since none of the linked paths currently exist in the skill directory.

Trim or tighten the closing prompt-cache anecdote so it earns its tokens more directly against the byte-pinning rule it motivates.

Add at least one short executable example (e.g. a minimal RED-GREEN test/code pair) to lift actionability from concrete guidance toward copy-paste ready.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence throughout, but the closing prompt-cache anecdote is somewhat padded relative to the rule it supports, fitting the 'efficient; minor instances that could be trimmed' anchor 4 rather than anchor 5.

4 / 5

Actionability

Provides concrete, specific process guidance (tracer bullet, incremental loop rules, an explicit per-cycle checklist, and the exact byte-sequence regression rule) with a clear horizontal-vs-vertical diagram, but contains no copy-paste executable code, capping it at anchor 4.

4 / 5

Workflow Clarity

The workflow is clearly sequenced (Planning, Tracer bullet, Incremental loop, Refactor) with an explicit validation gate ('Never refactor while RED'), re-run-tests checkpoints, and a per-cycle checklist feedback loop, matching anchor 5.

5 / 5

Progressive Disclosure

Sections are well-organized and references are clearly signaled one level deep (tests.md, mocking.md, deep-modules.md, interface-design.md, refactoring.md), but none of those referenced files actually exist in the bundle, leaving navigation broken — a minor organization gap that holds it at anchor 4.

4 / 5

Total

17

/

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.

The description is strong: it clearly states the skill's purpose and provides an explicit, multi-trigger 'Use when' clause that answers both what and when. Trigger terms are natural and distinct, giving low conflict risk; specificity is the only soft spot, with actions being somewhat generic.

DimensionReasoningScore

Specificity

Names the TDD domain and concrete actions ('build features or fix bugs using TDD', 'red-green-refactor loop'), but the actions are generic rather than a comprehensive list, matching anchor 3.

3 / 5

Completeness

Explicitly answers both what ('Test-driven development with red-green-refactor loop') and when (a 'Use when...' clause with concrete trigger phrases), matching anchor 5.

5 / 5

Trigger Term Quality

Includes natural user-facing terms ('TDD', 'red-green-refactor', 'integration tests', 'test-first development') with good coverage, though a few common synonyms are missing, fitting anchor 4 rather than the comprehensive anchor 5.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche with distinct, specific triggers ('red-green-refactor', 'test-first development') and minimal overlap risk with other skills, matching anchor 5.

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 5 missing

Warning

Total

15

/

16

Passed

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