CtrlK
BlogDocsLog inGet started
Tessl Logo

tdd-workflow

Test-Driven Development workflow principles. RED-GREEN-REFACTOR cycle.

46

Quality

48%

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 ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/tdd-workflow/SKILL.md

The canonical home for this skill is tdd-workflow in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

65%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 content is lean and well-structured into clear TDD phases using tables and bullets, with excellent navigation for a single-file skill. Its weakness is actionability and workflow validation: it describes principles without executable examples or explicit checkpoints to confirm a test fails then passes.

Suggestions

Add one short runnable test example showing the RED-GREEN-REFACTOR transition in a real language (e.g., a pytest snippet that fails, passes, then is refactored).

Insert explicit validation checkpoints, such as 'Confirm the new test fails before implementing' and 'Re-run the full suite before leaving REFACTOR'.

Trim minor glosses like the 'YAGNI' expansion and the closing epigraph to tighten token efficiency.

DimensionReasoningScore

Conciseness

The body is almost entirely compact tables and short bullets that assume Claude already knows TDD, with only minor over-explanation (e.g., the 'YAGNI' gloss and the epigraph), fitting 'efficient; minor instances of over-explanation that could be trimmed'.

4 / 5

Actionability

It gives concrete principles and rules per phase, but no executable code, commands, or worked test examples — the guidance is specific yet not directly runnable, matching 'some concrete guidance but incomplete; pseudocode instead of executable code'.

3 / 5

Workflow Clarity

The RED-GREEN-REFACTOR sequence is clearly laid out, but there are no validation checkpoints confirming the test actually fails in RED or stays green in REFACTOR, so it sits at 'steps listed but validation gaps; checkpoints missing or implicit'.

3 / 5

Progressive Disclosure

This is a compact single-file skill under ~150 lines with no external bundle; sections are well-organized into clearly headed numbered topics, so per the simple-skill note progressive disclosure can score 5 with just well-organized sections.

5 / 5

Total

15

/

20

Passed

Description

32%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 correctly identifies the TDD niche with a recognizable cycle name, but it states a concept rather than concrete actions and entirely omits any 'Use when...' trigger guidance, which caps completeness low. It is distinct from unrelated skills yet underspecified for routing.

Suggestions

Replace 'workflow principles' with concrete actions, e.g. 'Guide test-first development: write a failing test, implement minimal code, then refactor.'

Add an explicit trigger clause such as 'Use when writing new features, fixing bugs, or establishing test coverage via the RED-GREEN-REFACTOR cycle.'

Include natural user-facing phrases ('write tests first', 'failing test', 'make it pass') alongside 'TDD' to improve trigger term coverage.

DimensionReasoningScore

Specificity

The phrase 'Test-Driven Development workflow principles' names the domain and the RED-GREEN-REFACTOR cycle, but lists no concrete actions (e.g., writing tests, running them, refactoring) — it only states a concept, matching the 'names the domain but actions are minimal or generic' anchor.

2 / 5

Completeness

The description gives a vague 'what' ('workflow principles' + cycle name) and no 'when' guidance at all, matching the 'has a vague what and no when' anchor rather than the clearer score-3 'what' example.

2 / 5

Trigger Term Quality

'Test-Driven Development', 'TDD', and 'RED-GREEN-REFACTOR' are domain keywords, but there are only one or two such terms and none are the natural trigger phrases a user would say (e.g., 'write tests first', 'failing test'), so it falls just below the midpoint anchor.

2 / 5

Distinctiveness Conflict Risk

'Test-Driven Development' and 'RED-GREEN-REFACTOR cycle' form a fairly distinct niche with its own trigger vocabulary; overlap risk is limited to closely related testing/coding skills, fitting the 'mostly distinct; minor overlap risk' anchor.

4 / 5

Total

10

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
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.