CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

tdd-engineer

Test-Driven Development com red-green-refactor enforced. Trigger em: "tdd", "test-first", "red-green-refactor", "tracer bullet", "behavior test", "integration test", "tdd deep module", "interface design test".

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/37-tdd-engineer/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

62%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 delivers an exceptionally clear, well-validated TDD workflow with strong feedback loops and anti-rationalization guardrails — the process guidance is among the most actionable of its kind. Its weaknesses are verbosity (duplicated checklists and an XP tangent re-explaining known concepts) and a monolithic structure whose referenced deep-dive files are absent from the bundle.

Suggestions

Cut the 'XP' section to a short pointer list mapping each practice to its policy file, and merge the near-duplicate 'Saidas Esperadas', 'Evidencia de Conclusao', and 'Checklist Por Ciclo' checklists into one — roughly 60-80 lines could be removed without losing any actionable guidance.

Trim the 'Filosofia' section: Claude already knows what good vs. bad tests are; keep only the kit-specific rules (no internal-collaborator mocks, no private-method tests, spec-reading names).

Create the referenced docs/skill-guides/*.md files (or remove the dangling references, including tdd-deep-modules.md which is marked 'a criar conforme demanda') so the 'Material Adicional' pointers resolve within the bundle.

DimensionReasoningScore

Conciseness

At ~240 lines the body contains several padded sections explaining concepts Claude already knows: the 'Filosofia' section re-explains what good vs. bad tests are, and the ~15-line 'XP' section explains pair programming, CI, sustainable pace, and YAGNI before mapping them to kit policies. Content is also repeated nearly verbatim across 'Saidas Esperadas', 'Evidencia de Conclusao', and 'Checklist Por Ciclo' (e.g., 'nenhum teste mocka colaborador interno', 'testes leem como spec'). This matches anchor 2 ('noticeably verbose; several unnecessary explanations or padded sections') rather than 3, because the padding and duplication go beyond occasional tightening opportunities — though the core workflow sections themselves are tight and imperative, keeping it above anchor 1's severe padding.

2 / 5

Actionability

For an instruction-only process skill, the guidance is concrete and specific: explicit RED→GREEN loop patterns, a planning checklist with the exact key question to ask, hard rules ('Nunca refactore enquanto RED', 'um teste por vez', 'so codigo suficiente para passar o teste atual'), and a decision procedure for broken tests after refactor. It falls short of anchor 5 only in minor gaps — e.g., no concrete example of a test name/file layout beyond the 'user can X when Y' pattern — and is clearly above anchor 3, where guidance would be pseudocode-level or missing key details.

4 / 5

Workflow Clarity

The process is explicitly sequenced (Fase 1 Planning → Fase 2 Tracer Bullet → Fase 3 Loop Incremental → Fase 4 Refactor) with validation at each step: verify the RED failure demonstrates the missing behavior, run tests after each refactor step, a per-cycle checklist, and an 'Evidencia de Conclusao' gate. Error-recovery feedback loops are spelled out ('Se um refactor quebrar um teste que passava: investigue regressao... Corrija ou reverta'), plus an anti-rationalization table for failure modes. This matches anchor 5's 'clear sequence with explicit validation steps; feedback loops for error recovery; checklists for complex processes'; anchor 4 would require missing or merely implicit checkpoints, which is not the case.

5 / 5

Progressive Disclosure

The SKILL.md is monolithic — no references/, scripts/, or assets/ bundle exists, and the files it points to (docs/skill-guides/tdd-approved-fixtures.md, tdd-mocking.md, tdd-refactoring.md, architecture-and-evidence.md) are not present in the bundle, with tdd-deep-modules.md even marked 'a criar conforme demanda'. References are clearly signaled one level deep in 'Material Adicional', and in-section headers are decent, but self-contained content that could live in separate files (the XP essay, interface heuristics, the full anti-rationalization table) is inlined, and several pointers are dangling. This sits at anchor 3 ('some structure; references present but content that should be separate is inline') — above anchor 2 because navigation within the file is real and references are not buried, below anchor 4 because the referenced files largely don't exist in the bundle.

3 / 5

Total

14

/

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.

The description states a clear TDD niche with an explicit, well-chosen trigger list that includes the main natural synonyms. Its main weakness is a thin 'what' — a single clause that doesn't enumerate the skill's concrete capabilities, leaving it informative but not comprehensive.

DimensionReasoningScore

Specificity

"Test-Driven Development com red-green-refactor enforced" names the domain and a single concrete capability (enforcing the red-green-refactor cycle) but lists no further actions such as writing minimal implementation, refactoring after green, or generating test reports. This matches the anchor 'Names domain and 1-2 concrete actions, but not comprehensive' — not 4, which requires several specific actions, and not 2, since the action stated is concrete rather than generic.

3 / 5

Completeness

Both parts are present: the 'what' is "Test-Driven Development com red-green-refactor enforced" and the 'when' is explicit trigger guidance ("Trigger em: 'tdd', 'test-first', ..."), so the missing-'Use when' cap at 3 does not apply. However, the 'what' is a single thin clause with no enumerated capabilities, keeping it at anchor 4 ('both present; could be more explicit or specific') rather than 5, which demands a fully concrete statement of both.

4 / 5

Trigger Term Quality

The trigger list ("tdd", "test-first", "red-green-refactor", "tracer bullet", "behavior test", "integration test") covers the main natural synonyms a user would say, but misses common variations like "write tests first", "unit testing", or "test coverage", and "tdd deep module" / "interface design test" are unnatural phrasings users would rarely utter. Good coverage with a few natural terms missing fits anchor 4; it is clearly above anchor 3's partial coverage but short of anchor 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

Triggers like "tdd", "red-green-refactor", and "tracer bullet" carve out a clear TDD niche, but generic testing terms such as "integration test" and "behavior test" could also fire a general QA/testing skill in the same kit (the body itself references a QA skill 05). Mostly distinct with minor overlap risk against closely related skills fits anchor 4; anchor 5 would require no meaningful overlap.

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

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

metadata_version

'metadata.version' is missing

Warning

Total

14

/

16

Passed

Repository

felvieira/claude-skills-fv

Path

skills/37-tdd-engineer/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.