CtrlK
BlogDocsLog inGet started
Tessl Logo

test-driven-development

Follow TalkPipe TDD workflow when making code changes. Use when implementing features, fixing bugs, or refactoring. Enforces write-fail-fix-pass order and test placement conventions.

87

0.83x
Quality

91%

Does it follow best practices?

Impact

67%

0.83x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

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.

The body is a model of a concise, actionable process skill: a strict test-first workflow with explicit fail/pass verification checkpoints, executable pytest commands, an escape hatch with user confirmation, and a closing checklist. It assumes Claude's knowledge and wastes no tokens.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — it never explains what TDD or pytest is, and every section (When to Use, Workflow, Conventions, Commands, escape hatch, Checklist) earns its tokens, matching the 'lean and efficient; every token earns its place' anchor.

5 / 5

Actionability

Provides fully executable, copy-paste-ready commands ('pytest tests/test_foo.py::test_bar -v', 'pytest --cov=src', 'source .venv/bin/activate') covering the common run cases, matching the top anchor.

5 / 5

Workflow Clarity

A strict-ordered four-step workflow with explicit validation checkpoints (verify fail, then verify pass), an error-recovery feedback loop via the 'When a Test Is Not Reasonable' section requiring user confirmation, and a final checklist — exactly the top anchor, and validation is present so the destructive/batch cap does not apply.

5 / 5

Progressive Disclosure

No bundle files exist and none are needed; the single-purpose skill is just over 50 lines but well-organized into clear, navigable section headers with no nested references or inlined bulk content, satisfying the simple-skill exception for well-organized structure.

5 / 5

Total

20

/

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.

The description is strong and explicit, clearly stating both capability and trigger conditions in third-person imperative voice. It is specific and actionable, with only minor gaps in trigger-term synonyms and slight overlap risk with generic coding skills.

Suggestions

Broaden trigger terms with natural synonyms users say, e.g. 'writing tests', 'test coverage', or 'adding tests', to lift trigger_term_quality toward comprehensive coverage.

Tighten the distinctiveness by foregrounding the TDD-specific signal (e.g. 'Use when the user wants test-first development') so it is less likely to fire for non-TDD coding tasks.

DimensionReasoningScore

Specificity

Names the TDD domain and several concrete actions ('making code changes', 'implementing features, fixing bugs, or refactoring', 'Enforces write-fail-fix-pass order and test placement conventions'), approaching comprehensive coverage but describing the workflow's enforcement rather than enumerating many discrete operations — fits the 'several specific actions; minor gaps' anchor rather than the fully comprehensive anchor.

4 / 5

Completeness

Explicitly answers both what ('Follow TalkPipe TDD workflow... Enforces write-fail-fix-pass order and test placement conventions') and when ('Use when implementing features, fixing bugs, or refactoring') with concrete trigger phrases, matching the top anchor exactly.

5 / 5

Trigger Term Quality

Includes natural phrases a user would say ('implementing features, fixing bugs, or refactoring') with good keyword coverage, but misses common synonyms such as 'writing tests' or 'test coverage', matching the 'good coverage; a few natural terms missing' anchor.

4 / 5

Distinctiveness Conflict Risk

The 'TalkPipe TDD workflow' framing carves a distinct niche, but the trigger set (features/bugs/refactoring) is broad enough to overlap with general coding skills, fitting 'mostly distinct; minor overlap risk' rather than 'clear niche with minimal conflict risk'.

4 / 5

Total

17

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
sandialabs/talkpipe
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.