CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

tdd

Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development.

Quality

77%

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

Quality

Content

67%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 procedural skill with a genuinely useful project-context prelude, a clear anti-pattern section, and a well-sequenced workflow with checklists. It is held back by Philosophy-section content that restates knowledge Claude already has and by sidecar references that cannot be confirmed against the bundle.

Suggestions

Cut or compress the Philosophy section's explanation of good-vs-bad tests (behavior through public interfaces, implementation coupling) to a one-line principle and delegate the examples entirely to tests.md/mocking.md, which already exist for that purpose.

Add a short recovery branch to the Incremental Loop for when a test will not go green (e.g., expected-failure diagnosis, when to delete and rewrite the test), closing the workflow's only validation gap.

Ensure the five sidecar files referenced in the body are actually bundled with the skill so the one-level-deep reference structure is verifiable in the distributed artifact.

DimensionReasoningScore

Conciseness

The project-context prelude and horizontal-slices anti-pattern are dense and earn their tokens, but the Philosophy section re-explains fundamentals Claude already knows ("Tests should verify behavior through public interfaces, not implementation details", "Good tests are integration-style... describe _what_ the system does"), which could be tightened.

3 / 5

Actionability

Concrete, actionable instruction-only guidance: the WRONG/RIGHT horizontal-vs-vertical slice diagram, exact questions to ask the user ("What should the public interface look like?"), and copy-ready per-cycle checklists; minor abstraction remains in refactor steps like "Apply SOLID principles where natural".

4 / 5

Workflow Clarity

Planning, Tracer Bullet, Incremental Loop, and Refactor are clearly sequenced with explicit checkpoints ("Never refactor while RED", "Run tests after each refactor step", "suite green before and after"), but there is no recovery guidance for when a test will not go green, leaving a minor validation gap.

4 / 5

Progressive Disclosure

Sidecar references ([tests.md], [mocking.md], [deep-modules.md], [interface-design.md], [refactoring.md]) are well-signaled, inline at point of relevance, and one level deep, and the prelude points to project files rather than inlining them; however, none of the referenced sidecar files are present in the bundle being reviewed, so the split cannot be verified.

4 / 5

Total

15

/

20

Passed

Description

78%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 with a clear what, an explicit multi-trigger use-when clause in third person, and distinct TDD-specific keywords. Its main gap is thin capability coverage (one method named) and a slightly over-broad integration-tests trigger.

DimensionReasoningScore

Specificity

Names the domain ("Test-driven development") plus one concrete method ("red-green-refactor loop"), matching the 1-2 concrete actions anchor; it does not enumerate several specific actions, so it falls short of anchor 4.

3 / 5

Completeness

Explicitly answers both what ("Test-driven development with red-green-refactor loop") and when ("Use when user wants to build features or fix bugs using TDD, mentions 'red-green-refactor', wants integration tests, or asks for test-first development") with concrete trigger phrases, matching the anchor-5 example pattern.

5 / 5

Trigger Term Quality

Natural trigger phrases are present ("TDD", "red-green-refactor", "test-first development", "integration tests", "build features or fix bugs"), but common user variations like "write tests first" or "unit tests" are missing, keeping it below comprehensive coverage.

4 / 5

Distinctiveness Conflict Risk

The TDD niche is distinct with specific triggers, but the "wants integration tests" trigger can fire on ordinary test-writing requests that don't intend TDD, a minor overlap with a generic testing skill.

4 / 5

Total

16

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 5 possibly missing (deep-modules.md, interface-design.md, mocking.md, refactoring.md, tests.md)

Warning

referenced_paths_exist

Referenced path issues: 3 possibly missing (scripts/guards.config.sh, scripts/tdd-pairing-guard-ci.sh, scripts/tdd-pairing-guard.sh)

Warning

Total

14

/

16

Passed

Repository

agranado2k/tic-tac-toe-haskell

Path

.agents/skills/tdd/SKILL.md

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.