CtrlK
BlogDocsLog inGet started
Tessl Logo

tdd-workflow

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

55

Quality

63%

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

The canonical home for this skill is jbvc/agents-tdd-workflow

SKILL.md
Quality
Evals
Security

Quality

Content

70%

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-organized, clearly sequenced TDD overview with strong workflow clarity and clean structure, but much of it restates textbook concepts Claude already knows and offers principles rather than concrete executable guidance. Tightening toward project-specific, actionable steps would improve conciseness and actionability.

Suggestions

Trim or condense restatements of well-known concepts (Three Laws, AAA pattern, YAGNI) in favor of project-specific workflow guidance Claude would not already infer.

Add at least one concrete executable example (e.g., a sample failing test and the minimal implementation that makes it pass) to raise actionability.

Provide explicit error-recovery guidance for when a refactor breaks a test (e.g., revert, fix, re-run) rather than only stating tests must stay green.

DimensionReasoningScore

Conciseness

The body uses lean tables and short bullets rather than verbose prose, but it restates concepts Claude already knows (Three Laws of TDD, AAA pattern, YAGNI, the basic cycle), so it is mostly efficient with some unnecessary restatement.

2 / 3

Actionability

Guidance is largely abstract principles ('Write production code only to make a failing test pass', 'Don't optimize yet') with no executable code or commands, though test-name examples and the do/don't anti-patterns table add some concrete specificity.

2 / 3

Workflow Clarity

The RED -> GREEN -> REFACTOR -> Repeat cycle is a clearly sequenced workflow with an explicit validation checkpoint ('All tests must stay green') and a built-in feedback loop, matching the clear-sequence-with-validation anchor.

3 / 3

Progressive Disclosure

No bundle files exist and none are needed; the single self-contained file is well-organized into ten numbered sections with clear headers, no monolithic prose wall and no deep reference nesting.

3 / 3

Total

10

/

12

Passed

Description

57%

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 to a distinct TDD niche but is minimal: it names the domain and cycle yet omits concrete actions and any explicit 'Use when' trigger guidance. Expanding it with concrete actions and a trigger clause would raise completeness and trigger coverage.

Suggestions

Add a 'Use when ...' clause listing natural triggers (e.g., 'Use when practicing Test-Driven Development, writing tests before implementation, or following the RED-GREEN-REFACTOR cycle').

Enumerate concrete actions instead of the abstract 'workflow principles' phrasing (e.g., 'write failing tests first, implement minimal code to pass, then refactor').

Include common trigger variations such as 'TDD', 'test-first development', and 'write tests before code' to improve trigger-term coverage.

DimensionReasoningScore

Specificity

Names the domain ('Test-Driven Development workflow principles') and a specific methodology ('RED-GREEN-REFACTOR cycle') that implies actions, but lists no concrete actions, matching the 'names domain and some actions, but not comprehensive' anchor.

2 / 3

Completeness

States the 'what' (TDD workflow principles) but the description field lacks any 'Use when...' trigger clause; per the guidelines a missing when-clause caps completeness at 2.

2 / 3

Trigger Term Quality

'Test-Driven Development' and 'RED-GREEN-REFACTOR' are natural terms a user would say, but coverage is thin with missing common variations such as 'TDD', 'test-first', or 'write tests before code'.

2 / 3

Distinctiveness Conflict Risk

'Test-Driven Development' and 'RED-GREEN-REFACTOR' are highly specific to a clear TDD niche and are unlikely to trigger for unrelated skills, matching the distinct-niche anchor.

3 / 3

Total

9

/

12

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.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

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

Warning

frontmatter_unknown_keys

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

Warning

Total

14

/

16

Passed

Repository
vudovn/ag-kit
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.