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

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

81%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 skill: a high-value project-context prelude with exact commands and enforcement details, a clearly sequenced workflow with explicit RED/GREEN validation loops and checklists, and well-signaled one-level references. Weaknesses are minor: some conceptual padding in the Philosophy section, no inline test-writing example, and referenced sidecars missing from the bundle.

Suggestions

Tighten the Philosophy section — the good/bad test paragraphs and the four-bullet 'crap tests' list largely restate what the workflow rules already imply.

Inline one minimal passing/failing test example (e.g. a single vitest *.test.ts case) so the core action doesn't depend entirely on the tests.md sidecar.

Ship the five referenced sidecars (tests.md, mocking.md, refactoring.md, deep-modules.md, interface-design.md) with the skill bundle, or remove the links — as delivered, every reference dead-ends.

DimensionReasoningScore

Conciseness

Largely efficient: the project-context prelude is dense and non-obvious, and the workflow/checklist sections carry no padding. Minor over-explanation in the Philosophy section ("Good tests are integration-style... Bad tests are coupled to implementation") and the four-bullet 'crap tests' rationale, which restate ideas Claude can infer. Not 5 because those passages could be tightened; not 3 because nothing is generic filler.

4 / 5

Actionability

Concrete, executable specifics throughout: "pnpm turbo test --filter=<workspace>", "*.test.ts" vs "*.spec.ts" conventions, "PUSH_WITHOUT_TESTS=1" and the "tdd-exempt" label escape hatches, plus exact file paths (scripts/guards.config.sh, docs/domain-glossary.md). Not 5 because the core skill action — how to write a good test — is entirely deferred to referenced sidecars with no inline example. Not 3 because what is inline is specific and executable, not pseudocode.

4 / 5

Workflow Clarity

Clear sequence (Planning → Tracer Bullet → Incremental Loop → Refactor) with explicit validation checkpoints: each RED→GREEN cycle is a validate-then-fix loop, "Run tests after each refactor step", "Never refactor while RED. Get to GREEN first", plus a per-cycle checklist and planning checklists with user confirmation gates. Matches the anchor-5 pattern (explicit validation, feedback loops, checklists); no destructive/batch cap applies.

5 / 5

Progressive Disclosure

Good structure: overview-sized body with clearly signaled, one-level-deep references ([tests.md], [mocking.md], [refactoring.md], [deep-modules.md], [interface-design.md]) placed at their point of use. Not 5 because none of the five referenced sidecar files exist in the bundle (no references/ or sibling files present), so navigation dead-ends; the references themselves are well organized and only one level deep, keeping this above 3.

4 / 5

Total

17

/

20

Passed

Description

82%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 an explicit what/when structure and concrete, natural trigger phrases. The only weakness is that the 'what' clause names the methodology rather than enumerating the specific actions the skill performs.

Suggestions

Expand the 'what' clause with concrete actions, e.g. "Write a failing test first, implement the minimal code to pass it, then refactor — one vertical slice at a time."

Add common trigger variations such as "write tests first" or "unit tests" to broaden natural keyword coverage.

DimensionReasoningScore

Specificity

"Test-driven development with red-green-refactor loop" names the domain and its core method but only 1-2 concrete actions — it doesn't enumerate what the skill actually does (write failing tests first, implement minimal code, refactor). Matches anchor 3 ('names domain and 1-2 concrete actions, not comprehensive'); not 4 because several specific actions are not listed.

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. Matches the anchor-5 example pattern exactly; third person throughout.

5 / 5

Trigger Term Quality

Natural triggers present: "build features or fix bugs using TDD", "red-green-refactor", "integration tests", "test-first development" — phrases users would genuinely say. Not 5 because common variations like "write tests first" or "unit tests" are missing.

4 / 5

Distinctiveness Conflict Risk

TDD is a clear niche with distinct, unambiguous triggers ("red-green-refactor", "test-first"); minimal overlap risk with generic testing or debugging skills.

5 / 5

Total

17

/

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: 1 possibly missing (scripts/guards.config.sh)

Warning

Total

14

/

16

Passed

Repository

agranado2k/ai-report-platform

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.