CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

tdd

Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.

Quality

75%

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/cloud-profile/skills/tdd/SKILL.md

The canonical home for this skill is tdd in mattpocock/skills

SKILL.md
Quality
Evals
Security

Quality

Content

71%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 tight, doctrine-heavy body that is genuinely actionable — it tells the agent exactly what to ask the user, what rules bind every loop cycle, and how to recognize anti-patterns, with a clean section structure. The weaknesses are moderate: it spends a few tokens re-teaching TDD fundamentals, the loop sequence is distributed across sections with no error-recovery path, and its two referenced files (tests.md, mocking.md) are missing from the bundle, breaking the progressive-disclosure chain.

Suggestions

Include tests.md and mocking.md in the bundle (e.g., under references/) or remove the links — the body's concrete examples of good tests and mocking guidance currently point to files that don't exist.

Present the loop as one explicit ordered sequence (read CONTEXT.md → agree seams with user → red → green → repeat per slice → refactor via code-review) instead of distributing it across the 'Seams' and 'Rules of the loop' sections.

Trim the re-statements of fundamentals Claude already knows (e.g., 'TDD is the red → green loop' as an opener and 'Code can change entirely; tests shouldn't') and keep only the project-specific rules.

DimensionReasoningScore

Conciseness

The ~30-line body is lean and directive with no padding; phrases like 'Tests verify behavior through public interfaces, not implementation details' and 'TDD is the red → green loop' restate fundamentals Claude already knows, and 'Code can change entirely; tests shouldn't' is redundant with the sentence before it. Not 5: those few tokens of over-explanation could be trimmed; not 3: the bulk is project doctrine (seam confirmation, tracer bullets, refactoring exclusion) that Claude cannot infer, not generic filler.

4 / 5

Actionability

Concrete, executable guidance throughout for an instruction-only skill: a literal question to ask ("What's the public interface, and which seams should we test?"), a concrete anti-example ("expect(add(a, b)).toBe(a + b)"), a diagnostic tell ("the test breaks when you refactor but behavior hasn't changed"), a worked test-name example ("user can checkout with valid cart"), and a concrete pre-step ("read `CONTEXT.md` (if it exists)"). Not 5: no example of a full good test or a complete vertical slice in the body — those are deferred to referenced files that are not present in the bundle; not 3: the guidance is specific and directly executable, not pseudocode or high-level hints.

4 / 5

Workflow Clarity

The loop sequence is clear from the rules — confirm seams with the user, red ("Write the failing test first"), green ("only enough code to pass it"), one vertical slice at a time, repeat — with an explicit validation checkpoint ("No test is written at an unconfirmed seam") and an explicit handoff for refactoring to the code-review skill. Not 5: the sequence must be assembled from four separate sections rather than stated as an ordered loop, and there is no guidance for the error path (what to do when the test won't go green or the seam proves wrong); not 3: the key checkpoints are explicit, not implicit.

4 / 5

Progressive Disclosure

Good structure for a short skill: the body is a concise overview of doctrine with clearly signaled, one-level-deep references ('See [tests.md](tests.md) for examples and [mocking.md](mocking.md) for mocking guidelines') and well-organized sections. Not 5: the two referenced files are not present in the bundle (no references/ directory and no tests.md or mocking.md anywhere), so the promised examples and mocking guidelines are unreachable; not 3: what is inline is appropriately placed and the references are clearly signaled rather than buried.

4 / 5

Total

16

/

20

Passed

Description

70%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 concise, third-person description with an explicit and well-phrased 'Use when' trigger clause covering natural terms like 'red-green-refactor' and 'integration tests'. Its main weakness is the terse 'what' — a bare methodology name that doesn't convey the skill's actual content (test quality, seams, anti-patterns, loop rules) — plus a missing 'TDD' abbreviation synonym.

Suggestions

Expand the 'what' beyond the bare methodology name, e.g., 'Test-driven development: rules for the red-green loop — what a good test is, where tests go (seams), and loop discipline. Use when...'

Add the abbreviation 'TDD' and the phrase 'unit tests' to the trigger clause to catch the most common ways users name this workflow.

DimensionReasoningScore

Specificity

The description names the domain distinctly ("Test-driven development") and includes one concrete action framing ("build features or fix bugs test-first"), but these are trigger conditions rather than statements of what the skill provides (e.g., test-quality criteria, seam selection, loop rules). Not 4: no list of several specific capabilities; not 2: the domain is named precisely and a concrete action phrase is present, unlike the purely generic 'Processes PDF files' anchor.

3 / 5

Completeness

Both parts are present: the 'what' is stated explicitly ("Test-driven development.") and the 'when' is fully explicit with concrete trigger phrases ("Use when the user wants to build features or fix bugs test-first, mentions 'red-green-refactor', or wants integration tests"). Not 5: the 'what' is a bare methodology name and never states the skill's actual scope (good-test criteria, seams, anti-patterns, loop rules); not 3: 'when' is explicit and specific, not weakly implied.

4 / 5

Trigger Term Quality

Good natural keyword coverage: "test-first", "red-green-refactor", "build features", "fix bugs", "integration tests" are phrases users would actually say. Not 5: common synonyms/variants are missing — notably the abbreviation "TDD", "unit tests", and "write tests first"; not 3: coverage goes well beyond 'some relevant keywords'.

4 / 5

Distinctiveness Conflict Risk

Clear niche (test-first development) with distinct triggers like "red-green-refactor" and "test-first". Minor overlap risk remains: "wants integration tests" could pull this skill for users who just want tests written without the TDD loop, and "build features or fix bugs" is broad phrasing shared with general development skills. Not 5: that residual overlap with a general testing skill; not 3: the core triggers are far more distinctive than 'Works with document files'.

4 / 5

Total

15

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 2 missing

Warning

Total

15

/

16

Passed

Repository

BigSimmo/PsychSift

Path

.claude/cloud-profile/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.