tdd-workflow

Use this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests.

Quality

61%

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

Quality

Content

60%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 highly actionable with abundant executable examples and a clear multi-step TDD workflow, but it is heavily padded with redundant explanation and is a monolithic single file that should split detailed patterns into reference files.

Suggestions

Trim redundant explanation of concepts Claude already knows (definitions of unit/integration/E2E tests, the generic 10-item best-practices list) to improve conciseness.

Extract the lengthy testing patterns, mocking examples, and E2E specs into separate reference files (e.g. PATTERNS.md, MOCKING.md) and link to them one level deep from SKILL.md.

Add an explicit validation feedback loop ('If tests fail: fix the code, re-run npm test, only proceed when green') to strengthen workflow_clarity toward 5.

Dimension	Reasoning	Score
Conciseness	The 400-line body extensively re-states concepts Claude already knows (what unit/integration/E2E tests are, generic best-practice lists, mocking basics) and pads with redundant section headers, making it noticeably verbose.	2 / 5
Actionability	It provides fully executable, copy-paste-ready code for unit, integration, and E2E tests plus concrete commands (npm test, npm run test:coverage) and a coverage-threshold JSON config covering the common cases.	5 / 5
Workflow Clarity	The seven-step TDD workflow is clearly sequenced with run-tests checkpoints (Steps 3, 5, 7) and an explicit refactor step, though error-recovery feedback loops when tests fail are only implicit.	4 / 5
Progressive Disclosure	The skill is a monolithic single-file wall of text with no references or bundle files; large blocks like the extensive code patterns and best-practices lists that belong in separate reference files are inlined in SKILL.md.	2 / 5
	Total	13 / 20 Passed

Description

63%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 cleanly states both what the skill does and when to use it, with a concrete 80% coverage requirement. Its main weaknesses are moderate trigger-term coverage and significant overlap with generic coding-skills triggers.

Suggestions

Add explicit trigger terms users naturally say, such as 'writing tests', 'test coverage', or 'TDD', to improve trigger_term_quality.

Tighten the 'when' clause to emphasize test-first intent (e.g. 'Use when the task requires test-driven development') to reduce overlap with generic coding skills.

Include the third-person form consistently; the current phrasing ('Use this skill when...') leans toward second-person guidance, which slightly weakens specificity.

Dimension	Reasoning	Score
Specificity	The description names the domain and several concrete actions ('writing new features, fixing bugs, or refactoring code') with a specific coverage requirement ('80%+ coverage including unit, integration, and E2E tests'), but coverage of actions is somewhat narrow relative to the full TDD scope.	4 / 5
Completeness	It has both a clear 'what' ('Enforces test-driven development with 80%+ coverage') and an explicit 'when' ('Use this skill when writing new features, fixing bugs, or refactoring code'), though the 'when' clause could be more comprehensive.	4 / 5
Trigger Term Quality	It includes natural user phrases like 'writing new features', 'fixing bugs', and 'refactoring code', but misses common synonyms ('tests', 'test coverage', 'writing tests') and tool-specific terms a user would naturally say.	3 / 5
Distinctiveness Conflict Risk	The triggers ('writing new features, fixing bugs, refactoring') are broad and overlap with general coding skills, so it could fire for non-TDD coding tasks; it is somewhat distinct via the TDD/coverage emphasis but conflict risk remains moderate.	3 / 5
	Total	14 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: affaan-m/ECC
Path: .kiro/skills/tdd-workflow/SKILL.md
Commit: d8409a4

Reviewed: 1 day 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.