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.

71

Quality

89%

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

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

An excellent, highly actionable skill body: the TDD cycle is sequenced with mandatory verification checkpoints, feedback loops, complete executable examples, and proper progressive disclosure into a well-signaled reference file. Its one weakness is redundancy — the core 'no code without a failing test / delete and start over' rule is repeated across four overlapping sections (Iron Law, Common Rationalizations, Red Flags, Final Rule) that could be consolidated.

Suggestions

Consolidate the redundant enforcement sections: 'The Iron Law', 'Red Flags - STOP and Start Over', and 'Final Rule' all restate the same rule, and the Red Flags bullets duplicate ~8 rows of the 'Common Rationalizations' table nearly verbatim — merge them into a single section to cut roughly 40 lines of repeated messaging.

Trim the wordiest 'Common Rationalizations' rows (e.g. "I'll test after" and "Tests after achieve same goals") to one-sentence rebuttals; the current multi-sentence explanations re-argue points the table format makes on its own.

The graphviz dot block adds a second visual restatement of the same cycle the headings already sequence — consider dropping it in favor of the section structure alone.

DimensionReasoningScore

Conciseness

The core Red-Green-Refactor guidance is lean and assumes Claude's competence (no basic-concept explanations), but the "no production code without a failing test / delete and start over" rule is restated across "The Iron Law", "Common Rationalizations", "Red Flags" (which duplicates ~8 rationalization rows nearly verbatim), and "Final Rule". Mostly efficient, but consolidating these overlapping enforcement sections would tighten it considerably — not a 2 because the repetition targets a specific failure mode rather than generic padding, not a 4 because several sections are redundant.

3 / 5

Actionability

Fully executable throughout: copy-paste-ready commands ("npm test path/to/test.test.ts"), complete TypeScript test and implementation examples for retryOperation with Good/Bad contrasts, and an end-to-end bug-fix walkthrough. Specific examples cover the common cases, matching the top anchor.

5 / 5

Workflow Clarity

The Red-Green-Refactor cycle is clearly sequenced with mandatory verification checkpoints at each phase, explicit feedback loops for error recovery ("Test errors? Fix error, re-run until it fails correctly"; "Other tests fail? Fix now"), and a final verification checklist — matching the top anchor including its checklist criterion.

5 / 5

Progressive Disclosure

SKILL.md serves as a well-sectioned overview while the deep-dive material (test-quality rules) is split into a single real, one-level-deep reference (references/writing-good-tests.md, confirmed present in the bundle with no nested references), clearly signaled by a markdown link plus a bullet summary of its contents. Content is appropriately split and easy to navigate.

5 / 5

Total

18

/

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: it specifies the full test-first workflow concretely in third person and includes an explicit 'Use when' clause with natural trigger phrases. The only gaps are a few missing synonyms (TDD, unit tests) and slightly broad when-triggers that create minor overlap risk with general coding skills.

DimensionReasoningScore

Specificity

"write one failing test, run it and watch it fail, write the minimal code to pass, then refactor with the tests green" lists multiple specific concrete actions covering the entire TDD cycle, matching the comprehensive-coverage anchor. Third-person voice ("Implements") is used correctly, so no specificity penalty applies.

5 / 5

Completeness

The description explicitly answers both what ("Implements a feature or bug fix test-first: write one failing test... then refactor") and when ("Use when a change alters code behavior: a new feature, a bug fix, or a behavior change") with concrete trigger phrases, matching the top anchor. Not a 4 because the 'when' clause is already explicit and specific.

5 / 5

Trigger Term Quality

Trigger terms "a new feature, a bug fix, or a behavior change" are natural phrases users would say, giving good keyword coverage. Not a 5 because common synonyms users would naturally use — "TDD", "unit tests", "write tests first" — are absent from the trigger clause.

4 / 5

Distinctiveness Conflict Risk

The "test-first" implementation framing carves a mostly distinct niche with minor overlap risk against closely related coding/testing skills. Not a 5 because the when-triggers ("new feature, a bug fix, or a behavior change") are broad enough that many code-change requests could match other 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

02-mutation/versions/current/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.