CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

test-driven-development

Use when implementing any feature or bugfix, before writing implementation code - write the test first, watch it fail, write minimal code to pass; ensures tests actually verify behavior by requiring failure first

Quality

77%

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 ./antigravity/skills/test-driven-development/SKILL.md

The canonical home for this skill is test-driven-development in NeoLabHQ/context-engineering-kit

SKILL.md
Quality
Evals
Security

Quality

Content

62%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 skill delivers a clearly sequenced TDD workflow with strong validation checkpoints and mostly executable examples, but it is severely overlong: rationalization rebuttals repeat three times and an entire second document is appended inline. Splitting the anti-patterns material into a reference file and cutting the redundant rationalization sections would materially improve it.

Suggestions

Deduplicate the rationalization material: 'Why Order Matters', 'Common Rationalizations', and 'Red Flags' cover the same excuses three times — keep one compact table and cut the rest.

Move the ~300-line 'Testing Anti-Patterns' document into a separate references/ file (e.g., references/anti-patterns.md) with a one-line pointer from SKILL.md.

Fix the Anti-Pattern 3 code example (add `async` to the test callback) so the shown code is actually executable as required by the actionability standard the skill itself sets.

DimensionReasoningScore

Conciseness

The ~695-line body covers the same rationalizations three times (the 'Why Order Matters' prose sections, the 'Common Rationalizations' table, and the 'Red Flags' list), and appends an entire second document on anti-patterns, making it noticeably verbose with substantial padded repetition.

2 / 5

Actionability

Concrete TypeScript Good/Bad pairs, executable `npm test` commands, and a fully worked bug-fix example give mostly copy-paste-ready guidance; minor gaps include the Anti-Pattern 3 example using `await` inside a non-async callback, so it does not run as written.

4 / 5

Workflow Clarity

The Red-Green-Refactor cycle is explicitly sequenced with mandatory verification checkpoints (Verify RED, Verify GREEN), explicit error-recovery loops ('Test errors? Fix error, re-run until it fails correctly'), and a completion checklist — validation is present even for the destructive delete-and-restart guidance.

5 / 5

Progressive Disclosure

Section structure within each document is good, but there are no bundle files at all: the ~300-line Testing Anti-Patterns document is inlined in SKILL.md when it clearly belongs in a separate reference file, leaving the main file monolithic.

3 / 5

Total

14

/

20

Passed

Description

83%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 with an explicit 'Use when' clause, a clear three-action statement of what to do, and a rationale clause. Main weaknesses are missing common synonyms (TDD, test-driven) and a very broad trigger scope that could overlap with general coding skills.

Suggestions

Add natural synonyms such as 'TDD', 'test-driven development', or 'write tests first' to broaden trigger-term coverage.

Narrow or qualify the trigger scope (e.g., 'when writing code for a feature or bugfix') to reduce overlap with general implementation skills.

DimensionReasoningScore

Specificity

The description lists several concrete actions ("write the test first, watch it fail, write minimal code to pass") rather than vague language, though the refactor stage and bug-fix specifics are minor coverage gaps.

4 / 5

Completeness

It explicitly answers both questions: "Use when implementing any feature or bugfix, before writing implementation code" gives the when with concrete triggers, and the three-step formulation plus "ensures tests actually verify behavior by requiring failure first" gives the what.

5 / 5

Trigger Term Quality

Natural phrases users would say are present ("implementing any feature or bugfix", "before writing implementation code"), but common synonyms such as "TDD", "test-driven", or "write tests" are missing.

4 / 5

Distinctiveness Conflict Risk

The TDD methodology is a distinct niche with methodology-specific triggers, but "any feature or bugfix" is an extremely broad trigger scope that overlaps with general implementation and testing skills.

4 / 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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (699 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Repository

NeoLabHQ/context-engineering-kit

Path

antigravity/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.