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.

85

0.83x
Quality

87%

Does it follow best practices?

Impact

67%

0.83x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

100%

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

This is a well-crafted TDD workflow skill that is concise, actionable, and clearly structured. The strict ordering with verification steps at each stage ensures safe code changes, and the escape hatch for unreasonable tests is properly bounded with user confirmation. The checklist provides a useful summary reinforcement of the workflow.

DimensionReasoningScore

Conciseness

Every section earns its place. No unnecessary explanations of what TDD is or how pytest works. The content is lean and assumes Claude's competence with testing concepts.

3 / 3

Actionability

Provides concrete, copy-paste-ready pytest commands, a strict ordered workflow, and specific conventions. The commands section gives exact executable examples for common scenarios.

3 / 3

Workflow Clarity

The four-step workflow is clearly sequenced with explicit verification checkpoints (verify fail, then verify pass). The checklist at the end reinforces the feedback loop, and the 'When a Test Is Not Reasonable' section handles the escape hatch with a requirement to notify the user rather than skip silently.

3 / 3

Progressive Disclosure

For a simple, single-purpose skill under 50 lines with no need for external references, the content is well-organized into logical sections (workflow, conventions, commands, exceptions, checklist) that are easy to scan and navigate.

3 / 3

Total

12

/

12

Passed

Description

75%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a reasonably well-structured skill description with a clear 'Use when' clause and good distinctiveness through project-specific terminology. Its main weaknesses are that the specific actions could be more concrete (e.g., detailing what the TDD steps entail) and the trigger terms could cover more natural variations of how users might request TDD-related help.

Suggestions

Add more specific concrete actions describing what the skill does, e.g., 'writes failing tests before implementation, ensures minimal code to pass tests, enforces test file placement conventions'

Include additional natural trigger terms users might say, such as 'test-driven development', 'red-green-refactor', 'write tests first', 'unit tests', or 'test coverage'

DimensionReasoningScore

Specificity

Names the domain (TDD workflow, code changes) and some actions (implementing features, fixing bugs, refactoring), but doesn't list specific concrete actions like 'write failing test first, implement minimal code to pass, refactor'. The actions mentioned are generic software development activities rather than specific TDD steps.

2 / 3

Completeness

Clearly answers both 'what' (follow TalkPipe TDD workflow, enforces write-fail-fix-pass order and test placement conventions) and 'when' (when implementing features, fixing bugs, or refactoring) with an explicit 'Use when' clause.

3 / 3

Trigger Term Quality

Includes some relevant keywords like 'TDD', 'features', 'bugs', 'refactoring', 'test', but misses common natural variations users might say such as 'test-driven', 'red-green-refactor', 'unit test', 'write tests', or 'test first'. 'TalkPipe' is a project-specific term that helps with distinctiveness but isn't a natural trigger.

2 / 3

Distinctiveness Conflict Risk

The combination of 'TalkPipe TDD workflow', 'write-fail-fix-pass order', and 'test placement conventions' creates a clear, distinct niche. The project-specific name 'TalkPipe' and the specific methodology (TDD with defined order) make it unlikely to conflict with other skills.

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

Validation11 / 11 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.