CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

tdd-cycle

Use during the implementation step of any requirement — after the spec exists and before declaring done. Defines the red/green/refactor loop, the Three Laws adapted for agents, the mandatory refactor step with its quality gates (Four Rules of Simple Design, CRAP threshold), and the backtracking protocol for when you get stuck.

Quality

78%

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-cycle/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 strong, disciplined instruction-only skill: the loop is sequenced with explicit validation checkpoints and error-recovery protocols, and guidance is concrete down to stub values and commit-message formats. Its only notable gaps are un-pathed cross-references to sibling skills and slight over-explanation in a couple of motivational passages.

DimensionReasoningScore

Conciseness

Dense and token-efficient: assumes TDD familiarity, cites sources in a line ('Source discipline: Robert C. Martin's Three Laws'), and every section adds project-specific rules rather than general knowledge. Minor over-explanation (the opening rationale paragraph, the elaboration in 'Specific tests, generic code') keeps it below the lean-everything-earns-its-place anchor.

4 / 5

Actionability

Highly concrete for an instruction-only skill: stub recipes ('is_merge -> false', 'title -> String::new()', 'parse -> None'), explicit anti-patterns ('Do NOT stub with unimplemented!()/todo!()'), a commit-message format example ('pricing: extract bracket lookup from compute_tax'), and commands ('git stash'). Minor gaps: cross-references to verification-ratchet, spec-authoring, and testing-strategy lack file paths.

4 / 5

Workflow Clarity

The RED/GREEN/REFACTOR loop is explicitly sequenced with validation checkpoints ('Confirm it fails, and fails for the expected reason'; 'All tests green, not just the new one'; 'Refactor ONLY on green') plus full error-recovery feedback loops: the backtracking protocol with report-and-wait-for-human-ack, and handling for a test that passes immediately. This matches the clear-sequence-with-explicit-validation anchor.

5 / 5

Progressive Disclosure

No bundle files exist; the ~127-line body is organized into clear, well-ordered sections with no content that obviously belongs in a separate file. However, sibling-skill references ('see verification-ratchet, Layer 3', 'see testing-strategy', 'see CLAUDE.md boundary') are name-drops without paths or links — minor organization gaps characteristic of anchor 4.

4 / 5

Total

17

/

20

Passed

Description

63%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 clearly communicates a well-scoped what and an explicit when, anchored to a specific discipline (TDD red/green/refactor with named quality gates). Its weaknesses are trigger-term coverage — it never uses the vocabulary a user would naturally say ('TDD', 'test', 'test-driven') — and a broad implementation-stage trigger that risks overlapping sibling coding skills.

Suggestions

Add natural trigger vocabulary users actually say: 'Use when doing TDD, writing tests first, or when the user asks for red/green/refactor during implementation' — the word 'test' currently never appears in the description.

Sharpen the when-clause with concrete user-facing triggers (e.g., 'when the user asks to implement a requirement, feature, or bugfix from a spec') instead of only workflow-stage language.

Narrow the trigger scope ('implementation step of any requirement' fires on nearly any coding task) to reduce conflict with general implementation or verification skills.

DimensionReasoningScore

Specificity

Lists several concrete components — 'the red/green/refactor loop', 'the Three Laws adapted for agents', 'quality gates (Four Rules of Simple Design, CRAP threshold)', 'the backtracking protocol' — though these name concepts/protocols more than executable actions. Not 5 because the items are less concretely actionable than extract/fill/merge-style verbs; not 3 because coverage goes well beyond 1-2 items.

4 / 5

Completeness

Both what ('Defines the red/green/refactor loop... backtracking protocol') and when ('Use during the implementation step of any requirement — after the spec exists and before declaring done') are present and explicit. Not 5 because the when-clause is workflow-stage-based rather than concrete user trigger phrases like 'when the user asks to...'.

4 / 5

Trigger Term Quality

Relevant keywords exist ('implementation step', 'spec', 'red/green/refactor', 'when you get stuck') but common user phrasings are missing — 'TDD', 'test-driven', 'write tests first', even the word 'test' never appears. This matches 'some relevant keywords but missing common variations or synonyms' rather than the good-coverage anchor.

3 / 5

Distinctiveness Conflict Risk

The TDD-specific content (Three Laws, CRAP threshold, refactor gates) is distinctive, but the trigger 'implementation step of any requirement' is broad enough to fire on almost any coding task, overlapping general implementation and verification skills. Somewhat specific but real overlap risk with closely related skills.

3 / 5

Total

14

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

igouss/gitweb-rs

Path

.claude/skills/tdd-cycle/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.