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.

Quality

79%

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/common/common-tdd/SKILL.md

The canonical home for this skill is common-tdd in HoangNguyen0403/agent-skills-standard

SKILL.md
Quality
Evals
Security

Quality

Content

85%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.

The body is an exemplar of lean, high-density process guidance: a well-sequenced RED-GREEN-REFACTOR loop with explicit validation gates, error-recovery loops, and concrete schemas and guard IDs throughout. Its one real structural weakness is navigation — only one of eight reference files is linked from SKILL.md, so most of the bundle is invisible to a reader.

Suggestions

Add a short 'References' section in SKILL.md that lists all bundle files with one-line descriptions (e.g. test_runners.md for runner commands, anti-patterns.md and testing_anti_patterns.md for smell examples, tdd_patterns.md and aaa_methodology.md for pattern guidance) so the other seven files are discoverable.

Dedicate a single clearly-signaled pointer per topic instead of only the two mentions of quality-contract.md, and note when each reference should be consulted (e.g. 'read test_runners.md before deriving the focused command in step 1').

DimensionReasoningScore

Conciseness

The body never explains concepts Claude already knows (no "what is a mock/TDD" padding) and every line carries a rule, classification, or guard ID (e.g. the RED taxonomy, the Test Intent Record fields, the banned-smell list). It fits anchor 5: lean, assumes competence, every token earns its place.

5 / 5

Actionability

Concrete guidance dominates: the full Test Intent Record schema inline, a six-way RED classification taxonomy, an exact migration rule ("<stem>.test.js exists, migrate and replace it with <stem>.test.ts"), literal commands ("git rev-parse HEAD", "fallback 120s"), and named guard IDs. Minor gaps — no example intent record or sample focused-test command inline, only via the reference file — hold it at anchor 4 rather than 5.

4 / 5

Workflow Clarity

The "Bounded loop" is a numbered six-step sequence with explicit validation checkpoints (classify RED, "Reject early zero-exit completions and no-listener runs", rerun the same command) and error-recovery feedback loops ("On unexpected_green, inspect existing coverage and remove redundant or weak case"; "Later edits invalidate affected proof only; rerun affected gates without weakening checks"). The five-gate Layered Acceptance Protocol with NOT APPLICABLE recording and timeout child-cleanup verification matches anchor 5's checklist-and-feedback standard.

5 / 5

Progressive Disclosure

Scored against the actual bundle: references/quality-contract.md is clearly signaled twice and exists, but 7 of the 8 bundle files (aaa_example.md, aaa_methodology.md, anti-patterns.md, best-practices.md, tdd_patterns.md, test_runners.md, testing_anti_patterns.md) are never referenced from the body, leaving them undiscoverable. This matches anchor 3 (references present but not clearly signaled, organization could be better) rather than 4, since orphaning the bulk of the bundle is more than a minor gap.

3 / 5

Total

17

/

20

Passed

Description

67%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.

The description is specific and mostly complete, clearly stating three concrete TDD actions and three applicable contexts. Its main weaknesses are trigger coverage — the natural phrases users would say when needing this skill ("write tests", "unit test", "failing test") are absent from the description text — and a "when" clause that is explicit but not phrased as standalone "Use when..." guidance.

Suggestions

Add an explicit trigger clause, e.g. "Use when writing new tests, fixing bugs test-first, or when the user mentions TDD, unit tests, or failing tests", to lift completeness and trigger coverage together.

Incorporate the natural trigger phrases currently stranded in metadata.triggers ("unit test", "write test", "failing test", "test coverage") into the description itself so users asking to "write a unit test" match naturally.

Consider naming one concrete outcome (e.g. the Test Intent Record) to sharpen distinctiveness against generic testing-skills.

DimensionReasoningScore

Specificity

"Selects the smallest test layer", "proves a distinct regression risk", and "runs bounded RED-GREEN-REFACTOR verification" list several specific actions across three named contexts (new behavior, bug fixes, test changes). Minor gaps keep it below 5: the actions are process-level rather than fully concrete capabilities.

4 / 5

Completeness

The "what" is clear ("Guides quality-first TDD... Selects... proves... runs...") and a "when" is explicitly present via "for new behavior, bug fixes, and test changes", so it exceeds anchor 3's weakly-implied "when". It falls short of anchor 5 because the trigger guidance is embedded in the what-sentence rather than concrete "Use when..." trigger phrases.

4 / 5

Trigger Term Quality

"TDD", "bug fixes", "test changes", and "RED-GREEN-REFACTOR" are relevant keywords, but the most natural user phrases — "write tests", "unit test", "failing test" — appear only in metadata.triggers, not in the description itself. Missing common variations matches anchor 3 rather than 4.

3 / 5

Distinctiveness Conflict Risk

"quality-first TDD", "distinct regression risk", and "RED-GREEN-REFACTOR" carve out a mostly distinct niche with specific process vocabulary. Minor overlap risk remains with generic testing or code-review skills because the description lacks fully separating trigger phrasing.

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

.agents/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.