CtrlK
BlogDocsLog inGet started
Tessl Logo

tdd

Test-driven development workflow using red-green-refactor cycles with integration tests at service boundaries and property-based testing. Use when the user explicitly requests TDD, test-first development, write tests first, unit tests, red-green-refactor, or property-based testing approaches.

73

Quality

89%

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

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

A well-structured TDD process with strong workflow sequencing, validation checkpoints, and clean progressive disclosure into real reference files. Conciseness and a missing executable code example keep it from maximum.

Suggestions

Trim the philosophical opening paragraph ('TDD is a design technique...') to keep only the process-relevant guidance and improve token efficiency.

Add one short executable test snippet (e.g., a failing test plus minimal passing code) to make the implementation phase copy-paste ready.

DimensionReasoningScore

Conciseness

Mostly lean and assumes Claude's competence without explaining basics, but the philosophical opening framing and a few non-action lines could be trimmed; falls just short of the 'every token earns its place' anchor 5.

4 / 5

Actionability

Highly actionable numbered process with a concrete [TEST] comment format and given-when-then guidance, but as an instruction-only skill it lacks a copy-paste executable code example, leaving minor gaps versus anchor 5.

4 / 5

Workflow Clarity

Clear sequenced phases (planning, implementation, final evaluation) with explicit validation checkpoints (predict failure, run tests, see red/green) and feedback loops for error recovery.

5 / 5

Progressive Disclosure

Well-organized overview with clearly signaled one-level-deep references to boundary-testing.md and zombies.md, both of which exist and match their described contents.

5 / 5

Total

18

/

20

Passed

Description

95%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 capabilities and provides explicit, comprehensive trigger phrases in third-person voice. Minor specificity gap keeps it just below maximum.

DimensionReasoningScore

Specificity

Names the domain plus three concrete actions ('red-green-refactor cycles', 'integration tests at service boundaries', 'property-based testing'), matching 'several specific actions; minor gaps' rather than fully comprehensive anchor 5.

4 / 5

Completeness

Clearly answers both 'what' (red-green-refactor cycles with integration/property-based tests) and 'when' via an explicit 'Use when...' clause with concrete trigger phrases.

5 / 5

Trigger Term Quality

Lists comprehensive natural trigger phrases users would say ('TDD', 'test-first development', 'write tests first', 'unit tests', 'red-green-refactor', 'property-based testing'), including synonyms.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear TDD niche with distinctive triggers ('red-green-refactor', 'write tests first') that are unlikely to fire for unrelated skills.

5 / 5

Total

19

/

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
ericjohnolson/tessl-test
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.