CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

test-driven-development

Implements a feature or bug fix test-first: write one failing test, run it and watch it fail, write the minimal code to pass, then refactor with the tests green. Use when a change alters code behavior: a new feature, a bug fix, or a behavior change, whether the request comes alone or through delivery-flow.

76

Quality

95%

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

The canonical home for this skill is test-driven-development in tesslio/tessl-eval-demo

SKILL.md
Quality
Evals
Security

Quality

Content

100%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.

This is a model instruction-only SKILL.md body: a tight five-step cycle with validation checkpoints and feedback loops, rules that resolve real edge cases, a completion checklist, and a single well-signaled one-level-deep reference. Nothing is padded, nothing is missing for the workflow it teaches.

DimensionReasoningScore

Conciseness

The ~26-line body contains zero concept explanation and zero padding; every sentence is an instruction ('Write one test for one behavior', 'Add nothing the test does not need'), assuming Claude's competence throughout.

5 / 5

Actionability

Although this is an instruction-only skill with no code, the guidance is fully directive and covers the common cases: the five-step cycle, a bug fix that 'starts with a test that reproduces the bug', the pass-on-red failure mode ('If it passes, it tests nothing new: change the test'), and the hard-test design signal. Per the scoring notes, instruction-only skills are not penalized for lacking code when the guidance is this actionable.

5 / 5

Workflow Clarity

The Red/Green/Refactor sequence is explicit with validation checkpoints at every step ('Watch it fail', 'Watch it pass... no errors or warnings'), an error-recovery feedback loop ('must fail because the behavior is missing, not because of a typo'), and a closing 'Before you say it is done' checklist — exactly the anchor-5 pattern.

5 / 5

Progressive Disclosure

The skill is under 50 lines with well-organized sections (cycle, rules, done-checklist), and its single reference is real (references/writing-good-tests.md exists), one level deep, and clearly signaled with a load condition ('When writing or changing a test, read...').

5 / 5

Total

20

/

20

Passed

Description

88%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: concrete, third-person, and complete with an explicit Use-when clause covering features, bug fixes, and behavior changes. Keyword coverage is good but would catch more natural phrasings (e.g. 'TDD', 'write tests first') if the obvious synonyms were included.

Suggestions

Add natural synonyms users would say to the trigger clause, e.g. 'when the user asks to write a test first, mentions TDD, or asks for test-driven development'.

Tighten distinctiveness by naming what this skill does NOT cover (e.g. pure refactoring or test-only changes) to reduce overlap with adjacent delivery-flow skills.

DimensionReasoningScore

Specificity

The description enumerates the complete concrete cycle — 'write one failing test, run it and watch it fail, write the minimal code to pass, then refactor with the tests green' — matching the comprehensive multi-action anchor.

5 / 5

Completeness

It explicitly answers both questions: a concrete 'what' ('Implements a feature or bug fix test-first: ...') and a concrete 'when' ('Use when a change alters code behavior: a new feature, a bug fix, or a behavior change').

5 / 5

Trigger Term Quality

Natural user phrases like 'a new feature', 'a bug fix', and 'a behavior change' are present, but common synonyms a user might actually say — 'TDD', 'test-driven', 'unit tests', 'write the tests first' — are missing.

4 / 5

Distinctiveness Conflict Risk

The test-first framing is clearly distinguishable from any other skill, and the trigger is deliberately scoped ('whether the request comes alone or through delivery-flow'), though 'any behavior change' is broad enough to overlap with closely related workflow skills.

4 / 5

Total

18

/

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

tesslio/tessl-eval-demo

Path

03-ablation/versions/full/sdlc-implementation/skills/test-driven-development/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.