CtrlK
BlogDocsLog inGet started
Tessl Logo

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

64

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 ./plugins/tdd/skills/test-driven-development/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

Highly actionable with an exemplary validated workflow, but the document is overlong and repetitive, and it inlines a second topic that belongs in a referenced file rather than the SKILL.md overview.

Suggestions

Collapse the triplicated rationalization material ("Why Order Matters", "Common Rationalizations" table, "Red Flags" list) into a single section to remove padding.

Move the Testing Anti-Patterns section into a separate reference file (e.g. references/anti-patterns.md) and link to it one level deep from SKILL.md.

Trim persuasive prose (e.g. sunk-cost elaboration) that restates what the Iron Law and checklist already convey.

DimensionReasoningScore

Conciseness

At ~700 lines the body is noticeably verbose, with the same anti-rationalization material triplicated across "Why Order Matters" prose, the "Common Rationalizations" table, and the "Red Flags" list, plus an entire inlined second topic (Testing Anti-Patterns).

2 / 5

Actionability

Fully executable guidance throughout: copy-paste TypeScript examples, concrete commands ("npm test path/to/test.test.ts"), explicit good/bad contrasts, gate functions, and a completion checklist covering common cases.

5 / 5

Workflow Clarity

The Red-Green-Refactor cycle is clearly sequenced with mandatory validation checkpoints ("Verify RED - Watch It Fail", "Verify GREEN") and explicit feedback loops ("Test passes? You're testing existing behavior. Fix test."), so the destructive-operation cap does not apply.

5 / 5

Progressive Disclosure

Well-structured with clear section headers but entirely monolithic — no bundle files or one-level-deep references, and the ~300-line Testing Anti-Patterns section is content that should live in a separate reference file.

3 / 5

Total

15

/

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 that clearly states both the trigger conditions and the concrete TDD procedure in third-person imperative voice. Minor gaps in synonym coverage and some breadth in the trigger keep it just below a perfect score.

DimensionReasoningScore

Specificity

Lists several concrete actions — "write the test first, watch it fail, write minimal code to pass" — covering the core TDD cycle, though it stops at three actions rather than exhaustive coverage.

4 / 5

Completeness

Explicitly answers both what ("write the test first, watch it fail, write minimal code to pass; ensures tests actually verify behavior") and when ("Use when implementing any feature or bugfix, before writing implementation code") with concrete trigger phrasing.

5 / 5

Trigger Term Quality

Includes natural phrases users would say ("implementing any feature or bugfix", "write the test first", "watch it fail") but omits common synonyms like "TDD", "test-driven", "unit test", or "refactoring".

4 / 5

Distinctiveness Conflict Risk

The methodology clause ("write the test first, watch it fail") carves a clear niche, though the trigger "implementing any feature or bugfix" is broad enough to overlap with general coding 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.

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