CtrlK
BlogDocsLog inGet started
Tessl Logo

skill-tdd

Build features with tests-before-code rigor — use for new features needing test coverage

60

Quality

70%

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 ./.claude/skills/skill-tdd/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

77%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 delivers a well-sequenced TDD workflow with strong validation checkpoints and actionable examples, though it carries repetitive enforcement rhetoric that inflates token use.

Suggestions

Trim redundant enforcement sections (Common Rationalizations, Red Flags, The Bottom Line) that restate the Iron Law already covered above.

Replace generic placeholders like <paste test code here> and path/to/test.test.ts with concrete filled examples.

DimensionReasoningScore

Conciseness

Mostly task-oriented but padded with repeated enforcement rhetoric (Common Rationalizations, Red Flags, The Bottom Line) and TDD philosophy Claude already knows.

3 / 5

Actionability

Provides concrete executable code, specific npm commands, and a real provider-dispatch bash block, with minor gaps from placeholders like <paste test code here> and path/to/test.test.ts.

4 / 5

Workflow Clarity

Clear RED→VERIFY→GREEN→VERIFY→REFACTOR sequence with mandatory verification checkpoints, outcome decision tables, feedback loops, and a final completion checklist.

5 / 5

Progressive Disclosure

Single self-contained skill with no external references needed, well-organized into clear sections; fits the simple-skill exception for a 5.

5 / 5

Total

17

/

20

Passed

Description

62%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 covers both what the skill does and when to use it with a distinct test-first niche, but it under-specifies concrete actions and lacks common natural trigger terms like 'TDD' or 'write tests'.

Suggestions

List 2-3 concrete actions instead of one (e.g., 'Write failing tests first, implement minimal code to pass, then refactor').

Add natural trigger keywords users actually say, such as 'TDD', 'write tests', 'unit test', or 'test-driven'.

Broaden the 'use for' clause beyond 'new features needing test coverage' to cover bugfixes and behavior changes.

DimensionReasoningScore

Specificity

Names the TDD domain and one concrete action framing ('Build features with tests-before-code rigor'), but does not list multiple specific actions.

3 / 5

Completeness

Has both a clear 'what' (build features with test-first rigor) and an explicit 'use for' when-clause, though the 'when' is a single narrow case rather than concrete trigger phrases.

4 / 5

Trigger Term Quality

Includes 'features' and 'test coverage' but omits common natural phrases and synonyms like 'write tests', 'TDD', or 'unit test'.

3 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (test-first discipline) distinguishable from general coding skills, with only minor overlap risk against generic testing skills.

4 / 5

Total

14

/

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
nyldn/claude-octopus
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.