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

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable with a clear, well-validated TDD workflow and strong command/code guidance. It loses points on conciseness (generic best-practice padding) and progressive disclosure (monolithic, no reference files).

Suggestions

Move 'Best Practices,' 'Common Testing Mistakes,' and 'Success Metrics' into a reference file or trim them, since they restate knowledge Claude already has.

Split the large inline sections (Mocking External Services, Test File Organization, CI/CD Integration) into one-level-deep reference files and link to them from SKILL.md to improve progressive disclosure.

Trim the closing 'Remember' paragraph and other restatement prose to reduce token cost without losing the actionable workflow.

Dimension	Reasoning	Score
Conciseness	The body is very long; much is genuinely non-obvious (RED-gate definitions, Bun-vs-npm runner matrix, plan safety), but sections like 'Best Practices,' 'Common Testing Mistakes,' 'Success Metrics,' and closing prose restate concepts Claude already knows, so it is mostly efficient with unnecessary padding rather than fully lean.	2 / 3
Actionability	It provides executable TypeScript/Bun/Playwright code, a resolved test-runner command matrix, real coverage-threshold JSON, and copy-paste-ready patterns with concrete placeholders resolved in Step 0.	3 / 3
Workflow Clarity	Steps 0–8 are clearly sequenced with explicit RED and GREEN validation gates, per-stage checkpoint commits, and feedback loops ('do not edit production code until RED confirmed,' re-validate on failure), matching the clear-sequence-with-explicit-validation anchor.	3 / 3
Progressive Disclosure	No bundle files exist and the skill is a single monolithic document with no external references; large chunks (mocking patterns, test-file organization, CI/CD) that could be split out are inline, so it has some structure but no one-level-deep reference split.	2 / 3
	Total	10 / 12 Passed

Description

92%

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, trigger-rich, and explicitly answers both what and when, scoring near the top. Its main weakness is generic triggers that could collide with other development skills.

Suggestions

Tighten the triggers to emphasize TDD-specific phrasing (e.g., 'when the user wants tests written first' or 'when following a red-green-refactor cycle') to reduce overlap with general coding skills.

Lead with the distinguishing behavior ('Enforces a test-first red-green-refactor cycle') before the generic triggers so the niche is front-loaded.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ('writing new features, fixing bugs, or refactoring code') plus a measurable enforcement constraint ('80%+ coverage including unit, integration, and E2E tests'), matching the multiple-specific-actions anchor.	3 / 3
Completeness	An explicit 'Use this skill when...' clause answers 'when,' and 'Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests' answers 'what,' satisfying both halves explicitly.	3 / 3
Trigger Term Quality	Phrases like 'writing new features,' 'fixing bugs,' and 'refactoring code' are natural terms users would actually say, giving good coverage rather than jargon or generic terms.	3 / 3
Distinctiveness Conflict Risk	The triggers ('writing new features, fixing bugs, refactoring code') are broad and could overlap with general coding or other dev skills, even though the TDD-plus-coverage niche narrows it; not clearly distinct enough for a 3.	2 / 3
	Total	11 / 12 Passed

Validation

75%

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

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (584 lines); consider splitting into references/ and linking	Warning
metadata_version	'metadata.version' is missing	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	12 / 16 Passed

Repository: ysyecust/everything-claude-code
Commit: a9cbecb

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.