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 ./eval/archives/grill-test-20261013/application/skills/tdd/SKILL.md
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 tightly written, directive body with a clear loop structure and genuinely useful anti-pattern guidance. Its one significant defect is that both of its external references (tests.md, mocking.md) are dangling — the promised examples and mocking guidelines simply don't exist in the skill bundle.

Suggestions

Create the referenced files (tests.md with worked good/bad test examples, mocking.md with mocking guidelines) or remove the references from the body so no navigation path dead-ends.

Add an explicit red-phase checkpoint to the loop rules, e.g. 'Run the test and confirm it fails for the expected reason before writing any implementation.'

Trim the near-duplicate statement between the 'What a good test is' and 'Seams' sections (both assert tests go through public interfaces, not internals).

DimensionReasoningScore

Conciseness

The body is lean and assumes competence, teaching by example rather than explanation (e.g. the tautological-test tell 'expect(add(a, b)).toBe(a + b)'). Minor redundancy: 'Tests verify behavior through public interfaces, not implementation details' in the first section largely repeats 'Tests live at seams, never against internals' in the seams section. Not 5: a few sentences could be tightened.

4 / 5

Actionability

Concrete directives throughout — 'Write the failing test first, then only enough code to pass it', the exact question to ask ('What's the public interface, and which seams should we test?'), and a diagnostic 'tell' for each anti-pattern. Not 5: the strongest concrete material (worked examples of good tests, mocking guidelines) is delegated to tests.md and mocking.md, which do not exist in the bundle.

4 / 5

Workflow Clarity

The loop is clearly sequenced (agree seams with the user → write failing test → minimal implementation → repeat), with an explicit pre-cycle checkpoint ('No test is written at an unconfirmed seam') and explicit routing of refactoring to the review stage. Not 5: there is no explicit checkpoint to run the test and confirm it is actually red before implementing.

4 / 5

Progressive Disclosure

Sections are well organized and references are clearly signaled ('See [tests.md](tests.md) for examples and [mocking.md](mocking.md) for mocking guidelines'), but neither referenced file exists — there are no references/, scripts/, or assets/ directories in the bundle. Not 4/5: a signposted reference that leads nowhere is a real navigation gap, and this skill clearly needs those external files for its examples.

3 / 5

Total

15

/

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, well-triggered description with an explicit and specific 'Use when' clause. Its main weakness is a thin 'what' — it names the methodology but not what the skill contributes to it (test-quality guidance, seam selection, anti-patterns).

Suggestions

Expand the 'what' half to one clause naming what the skill contributes, e.g. 'Test-driven development: rules for the red-green loop, what a good test is, where tests go (seams), and anti-patterns.'

Add common synonyms such as 'write tests first' or 'TDD' to the trigger clause to catch users who use those phrasings.

DimensionReasoningScore

Specificity

The description names the domain ("Test-driven development") and 1-2 concrete actions ("build features or fix bugs test-first"), but does not enumerate the skill's actual coverage (good-test criteria, seams, anti-patterns, loop rules). Not 4: it does not list several specific actions the way the anchor-4 example does.

3 / 5

Completeness

The 'when' is explicit with three concrete trigger conditions ("Use when the user wants to build features or fix bugs test-first, mentions 'red-green-refactor', or wants integration tests"), and the 'what' is stated but is a bare domain label. Not 5: the what-side is thinner than the anchor-5 example, which lists multiple capabilities; not 3 because 'when' is explicit, not weakly implied.

4 / 5

Trigger Term Quality

Natural user phrasings are present — "red-green-refactor", "build features", "fix bugs", "test-first", "integration tests" — which users wanting TDD would realistically say. Not 5: common synonyms like "write tests first", "unit tests", or the bare acronym "TDD" are missing.

4 / 5

Distinctiveness Conflict Risk

The test-first framing and the distinctive "red-green-refactor" marker give it a clear niche with minimal conflict risk. Not 5: the trigger "wants integration tests" could pull in users who simply want tests written rather than TDD methodology.

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

rpamis/comet

Path

eval/archives/grill-test-20261013/application/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.