CtrlK
BlogDocsLog inGet started
Tessl Logo

tdd

AI DevKit · Test-driven development — write a failing test before writing production code. Use when implementing new functionality, adding behavior, or fixing bugs during active development.

74

Quality

91%

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

100%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A tight, well-structured methodology skill that assumes Claude's competence and gives concrete, sequenced guidance with validation checkpoints. No bundle files exist, and none are needed for this scope.

DimensionReasoningScore

Conciseness

Lean and directive throughout ("Red. Green. Refactor. In that order, every time.") with no padding explaining concepts Claude already knows; every section earns its place.

3 / 3

Actionability

Gives concrete directives ("Write the simplest code that passes. Hardcode if needed") and an executable command (`npx ai-devkit@latest memory store …`); as an instruction-only skill, the guidance is specific and actionable.

3 / 3

Workflow Clarity

The Red→Green→Refactor cycle is explicitly sequenced with validation checkpoints ("Run it. It must fail.", "Run the test again. Still green? Done.") and clear feedback loops.

3 / 3

Progressive Disclosure

A single self-contained file with well-organized sections and no nested references; there is nothing that needs splitting out, so the flat structure is appropriate.

3 / 3

Total

12

/

12

Passed

Description

82%Weight 40%Scale 1-3

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 clear, well-triggered description with explicit "Use when" guidance and natural trigger phrases. Its main weakness is that the trigger conditions are broad and it names only one concrete action rather than a list.

Suggestions

Add at least one more concrete action (e.g., "drive interface design from failing tests") to lift specificity to the top anchor.

Narrow the trigger terms to TDD-specific phrasing (e.g., "Use when the user asks for test-driven development or wants tests written before code") to reduce overlap with general coding skills.

DimensionReasoningScore

Specificity

Names the domain and one concrete action ("write a failing test before writing production code"), but does not list multiple specific concrete actions as the top anchor requires.

2 / 3

Completeness

It states what the skill does (test-driven development, failing test first) and gives an explicit "Use when …" clause answering when to invoke it.

3 / 3

Trigger Term Quality

Phrases like "implementing new functionality, adding behavior, or fixing bugs during active development" are natural terms users would actually say when they need this skill.

3 / 3

Distinctiveness Conflict Risk

The TDD niche is recognizable, but the trigger conditions (implementing functionality, fixing bugs) are broad enough to overlap with general development skills, so it could trigger for the wrong skill.

2 / 3

Total

10

/

12

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
codeaholicguy/ai-devkit
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.