tdd

Boundary-focused TDD workflow enforcing L3/L4 altitude testing, property-based tests, and phase separation. Use when implementing features that require writing tests and code.

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./tiles/crafter/skills/tdd/SKILL.md

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 a well-structured, actionable TDD process with strong workflow sequencing, explicit validation checkpoints, and clean progressive disclosure into two real reference files. The only slack is light over-explanation in the opener and a few verbose steps.

Dimension	Reasoning	Score
Conciseness	Mostly tight procedural instruction that assumes Claude's competence, with minor over-explanation in the philosophical opener ('TDD is a design technique...') and a few verbose step descriptions that could be trimmed.	4 / 5
Actionability	Provides concrete templates (session-log entry format, [TEST] comments with ZOMBIES annotations) and specific sequenced steps; no inline code examples, but code is appropriately deferred to boundary-testing.md for this instruction-oriented skill.	4 / 5
Workflow Clarity	Clear Plan -> Implementation -> Final Evaluation sequence with explicit predict/confirm validation checkpoints, feedback loops (run tests after each simplification and refactor), and a ZOMBIES completeness checklist for error recovery.	5 / 5
Progressive Disclosure	Overview body with well-signaled one-level-deep references to real bundle files (references/boundary-testing.md, references/zombies.md); detailed code and heuristics are appropriately split into those files for easy navigation.	5 / 5
	Total	18 / 20 Passed

Description

75%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 well-structured with an explicit 'Use when' clause, naming concrete testing techniques that give it a clear niche. Its main weakness is a generic when-clause and reliance on metadata for the richest trigger synonyms.

Suggestions

Tighten the when-clause with concrete trigger phrases, e.g. 'Use when the user asks to write tests first, do red-green-refactor, or implement a feature test-first.'

Fold one or two natural synonyms (e.g. 'test driven development', 'red green refactor') into the description text itself rather than only metadata.triggers.

Briefly signal the red/green/refactor cycle in the what-clause so the core TDD workflow is conveyed, not just the boundary-testing specialty.

Dimension	Reasoning	Score
Specificity	Lists several concrete techniques ('L3/L4 altitude testing, property-based tests, and phase separation') but does not enumerate the broader TDD workflow actions (red/green/refactor, minimal code), leaving minor coverage gaps.	4 / 5
Completeness	Explicitly answers both what (boundary-focused TDD workflow) and when ('Use when implementing features...'), but the when-clause is generic and could name concrete trigger phrases.	4 / 5
Trigger Term Quality	Includes natural terms 'TDD' and 'writing tests', but the richer synonyms ('test driven development', 'red green refactor', 'write tests first') appear only in metadata.triggers rather than the description itself.	4 / 5
Distinctiveness Conflict Risk	The boundary/altitude niche framing is distinct, yet the broad 'TDD workflow' and 'writing tests and code' framing carries minor overlap risk with general testing skills.	4 / 5
	Total	16 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
metadata_field	'metadata' should map string keys to string values	Warning

	Total	15 / 16 Passed

Repository: ericjohnolson/tessl-test
Path: tiles/crafter/skills/tdd/SKILL.md
Commit: 2a98cc1

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.