test-driven-development

在实现任何功能或修复 bug 时使用，在编写实现代码之前

Quality

51%

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 ./skills/test-driven-development/SKILL.md

Quality

Content

77%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 highly actionable with a clear, validated red-green-refactor workflow and concrete executable examples. Its main weaknesses are a dangling reference to a missing writing-good-tests.md file and notable redundancy between the excuses and danger-signals sections.

Suggestions

Add the missing writing-good-tests.md bundle file (or remove the dangling reference) so the link at line 211 resolves.

Merge or trim the overlapping '常见借口' table and '危险信号' list to remove redundancy and save tokens.

Consider moving the large excuses/danger-signals reference material into a separate file to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete examples and no padding of basic concepts, but the '常见借口' table and '危险信号' list cover overlapping ground and the excuse rebuttals are long; the redundancy could be tightened.	3 / 5
Actionability	Fully executable TypeScript test and implementation examples plus concrete `npm test path/to/test.test.ts` commands, with Good/Bad contrasts and a worked bug-fix walkthrough covering the common TDD cases.	5 / 5
Workflow Clarity	The red-green-refactor cycle is clearly sequenced with explicit '必须执行' validation checkpoints (验证红灯/验证绿灯), feedback loops for each failure mode, and a final verification checklist.	5 / 5
Progressive Disclosure	Good section structure, but the single referenced file (writing-good-tests.md) does not exist in the bundle, and large tables (excuses, danger signals) that could live in separate files are inlined.	3 / 5
	Total	16 / 20 Passed

Description

25%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 functions as a trigger condition only, stating when to use the skill but never what it does. It also omits the skill's most natural trigger terms (test/TDD), relying on generic task language that overlaps heavily with other coding skills.

Suggestions

Add an explicit 'what' clause stating the skill's actions, e.g., 'Guide test-driven development: write a failing test first, then write minimal code to make it pass.'

Include the natural trigger terms users would actually say — 'write tests', 'testing', 'TDD', 'test-driven' — so the skill activates on the right requests.

Narrow the trigger from 'implementing any feature or fixing any bug' to contexts where writing tests first is the goal, to reduce overlap with general coding skills.

Dimension	Reasoning	Score
Specificity	Names the user's task domain ('实现任何功能或修复 bug') but never states the skill's own concrete actions (e.g., writing a failing test first); the skill's capabilities are unstated rather than concretely listed.	2 / 5
Completeness	Provides a clear 'when' ('在实现任何功能或修复 bug 时使用...在编写实现代码之前') but no explicit 'what'; only the 'when' is present without describing what the skill does.	2 / 5
Trigger Term Quality	Includes generic task terms ('实现功能', '修复 bug') but omits the core natural triggers a user would say for this skill — 'test', 'testing', 'TDD', 'write tests first' never appear.	2 / 5
Distinctiveness Conflict Risk	'实现任何功能或修复 bug' is very broad and would overlap with most coding skills; the 'before writing implementation code' qualifier narrows it only slightly, leaving high conflict risk.	2 / 5
	Total	8 / 20 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
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 1 missing	Warning

	Total	12 / 16 Passed

Repository: jnMetaCode/superpowers-zh
Path: skills/test-driven-development/SKILL.md
Commit: c68725b

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.