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

80%

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

88%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 exceptionally lean, prescriptive process document with explicit validation checkpoints, error-recovery loops, and concrete guard rules for a TDD workflow. Its only real weaknesses are the absence of any inline example (intent record or command) and the orphaning of most of the bundle's reference files, which receive no navigation pointers from SKILL.md.

DimensionReasoningScore

Conciseness

The body never explains concepts Claude already knows (no definition of TDD, mocking, or test structure) and every line is a project-specific rule, classification, or guard — e.g. "Setup errors (syntax, import, missing modules, broken fixture) are invalid_red, NOT behavioral RED." Nothing can be trimmed without losing a directive, matching the lean/efficient anchor; not 4 because there is no over-explanation anywhere to cut.

5 / 5

Actionability

Highly concrete directives throughout: an enumerated RED classification taxonomy, an exact Test Intent Record field list, specific banned APIs ("it.skip, it.only, fit, fdescribe, @Ignore"), a 120s fallback timeout, and "foreground, sequential, single-run mode". Falls short of the fully-executable 5 anchor because no sample intent record, example command, or code snippet appears inline — all examples are deferred to references/quality-contract.md.

4 / 5

Workflow Clarity

The Bounded loop is a numbered 6-step sequence with explicit validation at every step — RED classification enum with remediation ("On unexpected_green, inspect existing coverage and remove redundant or weak case"), rerun-same-command verification after GREEN and REFACTOR, and an escalation ladder — and the Layered Acceptance Protocol adds a 5-stage gate checklist with recorded PASS/FAIL/NOT RUN/NOT APPLICABLE states. This matches the anchor requiring explicit validation steps, error-recovery feedback loops, and checklists; not 4 because no validation checkpoint is missing.

5 / 5

Progressive Disclosure

The body is a lean overview that appropriately defers bulk detail to a clearly signaled, one-level-deep reference ("see references/quality-contract.md for schema" / "for full taxonomy, schemas, and anti-pattern examples"), and nothing that belongs in a separate file is inlined. However, scoring against the actual bundle structure: 7 of the 8 reference files (test_runners.md, tdd_patterns.md, anti-patterns.md, best-practices.md, aaa_example.md, aaa_methodology.md, testing_anti_patterns.md) are never referenced from SKILL.md, so most of the bundle is undiscoverable — more than the trivial gap a 5 allows but short of the inline-bloat/buried-reference failures that define 3.

4 / 5

Total

18

/

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.

The description communicates a distinct, specific TDD capability with named actions and strong core trigger terms, but it entirely lacks an explicit 'when to use this' clause, which caps completeness at 3. Adding a 'Use when...' sentence with natural trigger phrases would lift the description substantially.

Suggestions

Add an explicit trigger clause, e.g. "Use when writing tests for new behavior, fixing bugs test-first, or when the user mentions TDD, red-green-refactor, or failing tests."

Include natural trigger synonyms such as "test-first", "write a failing test", or "unit test" to broaden keyword coverage.

Ground the capability in user-observable terms (e.g. "writes the failing test first, then implements just enough code to pass it") instead of abstract labels like "proves a distinct regression risk".

DimensionReasoningScore

Specificity

Quotes: "Selects the smallest test layer", "proves a distinct regression risk", "runs bounded RED-GREEN-REFACTOR verification" — several specific named actions beyond just naming the domain ("quality-first TDD for new behavior, bug fixes, and test changes"), matching the several-specific-actions anchor. Not 5 because the actions remain at a methodological/abstract level rather than concrete user-observable operations; not 3 because three distinct actions are explicitly listed.

4 / 5

Completeness

The "what" is clearly answered (guides TDD, selects test layer, proves regression risk, runs bounded verification), but there is no "Use when..." clause or equivalent explicit trigger guidance in the description — "for new behavior, bug fixes, and test changes" only weakly implies when. Per the judging guidelines, a missing explicit trigger clause caps completeness at 3; not 4 because the 'when' is nowhere stated explicitly.

3 / 5

Trigger Term Quality

"TDD" and "RED-GREEN-REFACTOR" are exactly the natural phrases a user would say when they need this skill, reinforced by scenario terms "new behavior, bug fixes, and test changes" and "regression". A few natural variants are missing ("test-first", "write a failing test", "unit test"), so it lands on good-coverage-with-a-few-missing rather than comprehensive.

4 / 5

Distinctiveness Conflict Risk

The "quality-first TDD" / "RED-GREEN-REFACTOR" framing carves a clear niche with minimal overlap against unrelated skills. "test changes" and "bug fixes" broaden it slightly toward generic test-editing and general testing skills, giving minor overlap risk with closely related skills rather than the minimal conflict risk of a 5; well above the generic overlap of a 3.

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.