CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

common-tdd

Guides quality-first TDD for new behavior, bug fixes, and test changes. Selects the smallest test layer, proves a distinct regression risk, and runs bounded RED-GREEN-REFACTOR verification.

60

Quality

76%

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

Quality

Content

77%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, well-sequenced TDD workflow with excellent validation checkpoints and feedback loops. The main weaknesses are a bundle where 7 of 8 reference files are orphaned from SKILL.md navigation and a body claim that quality-contract.md holds 'runner examples' that it does not contain.

Suggestions

Add a short index of the remaining reference files (e.g., test_runners.md, tdd_patterns.md, anti-patterns.md, best-practices.md) with one-line descriptions so they are discoverable from SKILL.md.

Either add actual runner command examples to quality-contract.md or link test_runners.md where 'runner examples' are promised, so the body's reference claim is accurate.

De-duplicate the coverage-percentage and duplicate-check rules between the body and quality-contract.md, keeping the rule in one place.

DimensionReasoningScore

Conciseness

The body is lean and imperative with no padding or explanation of concepts Claude already knows. It is not a 5 because some guidance repeats across sections (coverage-percentage rules and duplicate-checking appear in both the body and the reference), and a few jargon-dense lines could be tightened.

4 / 5

Actionability

Concrete procedural guidance throughout: a numbered bounded loop, an exact 120-second timeout fallback, a RED classification taxonomy with next actions, and explicit escalation rungs. It falls short of 5 because no example focused-run commands are given, and the promised 'runner examples' are absent from quality-contract.md.

4 / 5

Workflow Clarity

The bounded loop is a clear RED -> GREEN -> REFACTOR sequence with explicit validation at every step: RED classification into four statuses, an unexpected_green feedback loop that triggers coverage inspection, rerunning the same command after GREEN and REFACTOR, and a gated escalation ladder.

5 / 5

Progressive Disclosure

The body appropriately keeps detail in the one clearly signaled reference (references/quality-contract.md), but the bundle contains 8 reference files and 7 of them (e.g., test_runners.md, tdd_patterns.md, best-practices.md) are never referenced from SKILL.md, leaving most of the bundle undiscoverable — more than a minor organization gap, so not 4.

3 / 5

Total

16

/

20

Passed

Description

66%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, third-person description with concrete actions and good natural trigger terms in a distinct TDD niche. Its main gap is the absence of an explicit 'Use when...' trigger clause, which caps completeness at 3.

Suggestions

Append an explicit trigger clause, e.g. 'Use when writing or changing tests, fixing bugs test-first, or when the user mentions TDD, failing tests, or test coverage.'

Fold one or two natural synonyms (e.g., 'unit test', 'write tests') from the metadata keywords into the description itself to lift trigger-term coverage.

DimensionReasoningScore

Specificity

The description lists several specific actions ('Selects the smallest test layer', 'proves a distinct regression risk', 'runs bounded RED-GREEN-REFACTOR verification') in the TDD domain. It falls short of 5 because coverage is not comprehensive — what 'quality-first' enforcement entails is implied rather than enumerated.

4 / 5

Completeness

The 'what' is clearly stated, but there is no 'Use when...' clause or equivalent explicit trigger guidance; 'for new behavior, bug fixes, and test changes' names scope rather than trigger conditions, so completeness is capped at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Natural trigger terms like 'TDD', 'bug fixes', 'test changes', 'regression', and 'RED-GREEN-REFACTOR' are present and would be said by users needing this skill. A few common natural terms ('unit test', 'write tests', 'test coverage') appear only in the metadata keywords, not the description itself, keeping it below 5.

4 / 5

Distinctiveness Conflict Risk

The TDD focus with specific triggers (regression risk, smallest test layer, RED-GREEN-REFACTOR) carves a distinct niche with minimal conflict risk. Minor overlap remains with generic testing or code-review skills, so it does not reach 5.

4 / 5

Total

15

/

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

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository

HoangNguyen0403/agent-skills-standard

Path

.github/skills/common/common-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.