CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

tdd

测试驱动开发。适用于用户想用先写测试的方式构建功能或修复缺陷、提到 “red-green-refactor”,或需要集成测试时。

Quality

75%

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 ./skills/engineering/tdd/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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.

A lean, opinionated, genuinely actionable TDD reference with concrete gates, a copy-paste question, and precise loop rules — let down mainly by its bundle: both referenced detail files (tests.md, mocking.md) are missing, so the promised examples and mocking rules are inaccessible. The workflow is clear but never assembled into one explicit start-to-finish sequence.

Suggestions

Ship the referenced files or remove the links: neither tests.md nor mocking.md exists in the bundle, so "示例见 [tests.md](tests.md)" and "mocking 规则见 [mocking.md](mocking.md)" are dangling references that break progressive disclosure entirely.

Add one inline example of a good specification-style test (e.g. the "user can checkout with valid cart" case as an actual test snippet) so the '什么是好 test' section is self-contained even if tests.md is unavailable.

Make the loop's validation step explicit — state 'run the test and confirm it fails before writing any implementation' — and consider a short numbered overview (explore → approve seams → red → green → repeat) so the full sequence doesn't have to be assembled from section order.

DimensionReasoningScore

Conciseness

The body is tight and opinionated, assumes competence ("TDD 是 red -> green loop" with no padding), and its concrete snippets like "expect(add(a, b)).toBe(a + b)" earn their place. Minor over-explanations could be trimmed — e.g. "因为它不关心 internal structure,所以能承受 refactors" and "你无法测试所有东西" state things Claude can infer — fitting 'efficient; minor instances of over-explanation'. Not anchor 5 because of those few inferable rationales; not anchor 3 because no section is padded or explains fundamentals Claude doesn't know.

4 / 5

Actionability

Highly concrete for an instruction-only skill: a copy-paste-ready question ("What's the public interface, and which seams should we test?"), a specific pre-test gate ("写任何 test 前,先写下要测试的 seams 并与用户确认"), an exact artifact spec ("给每个提议的 seam 加一行说明"), an exact tool invocation ("调用 Skill 工具并指定 codebase-design"), and unambiguous loop mechanics ("先写 failing test,再只写足够让它通过的代码"). Not anchor 5 because the promised examples — "示例见 [tests.md](tests.md)" — point to a file that does not exist in the bundle, leaving the '什么是好 test' section with no example; not anchor 3 because the guidance is far more executable than pseudocode-tier.

4 / 5

Workflow Clarity

A clear sequence is discernible: explore codebase / read GLOSSARY.md / respect ADRs → propose seams and get user confirmation (an explicit human checkpoint) → red before green ("先写 failing test") → minimal implementation → next slice, with refactoring explicitly routed to the code-review skill. Not anchor 5 because the end-to-end order is implied by section order rather than laid out as one explicit sequence, and there is no explicit 'run the test and confirm it fails' step; not anchor 3 because checkpoints (seam confirmation, red-first) are present and explicit rather than implicit. This is not a destructive/batch operation, so no cap applies.

4 / 5

Progressive Disclosure

The bundle contains only SKILL.md — no references/ directory, and neither of the two referenced files ([tests.md](tests.md), [mocking.md](mocking.md)) exists anywhere, so every external reference is dangling and the split-out content is unreachable (GLOSSARY.md is properly guarded with "如果存在"). The in-body structure and signaling are anchor-4 quality, but two-of-two broken references is a navigation failure beyond anchor 4's 'minor organization gaps'; not anchor 2 because the 38-line body is well-sectioned with nothing inlined that belongs in a separate file.

3 / 5

Total

15

/

20

Passed

Description

70%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.

A compact, honest description with an explicit and well-triggered 'use when' clause anchored by the distinctive red-green-refactor term. Its main weakness is a thin 'what' — it names TDD without stating what the skill provides — and a slightly over-broad integration-tests trigger that risks overlap with general testing skills.

Suggestions

Expand the 'what' beyond the methodology label, e.g. "测试驱动开发:定义什么是好 test、tests 应放在哪些 seams、anti-patterns 以及 red-green loop 的规则" — this would lift specificity from naming the domain to listing the skill's concrete capabilities.

Add the missing high-frequency trigger terms: the acronym "TDD" and "单元测试" (unit tests), which are among the most likely things a user would actually type.

Narrow or drop "或需要集成测试时" — needing integration tests does not imply wanting a test-first process; as written it invites conflicts with any general test-writing skill.

DimensionReasoningScore

Specificity

The description names the domain ("测试驱动开发") and gives one action-framing ("用先写测试的方式构建功能或修复缺陷" — build features or fix defects by writing tests first), but never states what the skill actually provides (test-quality criteria, seam placement, anti-patterns, loop rules). This matches 'names domain and 1-2 concrete actions, but not comprehensive' — above anchor 2 because it goes beyond a bare domain-plus-generic-verb, below anchor 4 because it lists no several specific actions.

3 / 5

Completeness

Both parts are present: what = "测试驱动开发" and an explicit, concrete when-clause ("适用于用户想用先写测试的方式构建功能或修复缺陷、提到 red-green-refactor,或需要集成测试时") with three trigger conditions. Not anchor 5 because the 'what' is a bare methodology label rather than a statement of the skill's concrete capabilities; not anchor 3 because the 'when' is explicit and specific, not merely implied.

4 / 5

Trigger Term Quality

Includes natural phrases users would actually say: "测试驱动开发", "先写测试", the exact ritual name "red-green-refactor", and "集成测试", plus use-case terms 构建功能/修复缺陷. Not anchor 5 because the most common synonyms are missing — the "TDD" acronym itself and "单元测试" (unit tests); not anchor 3 because coverage is well beyond 'some relevant keywords'.

4 / 5

Distinctiveness Conflict Risk

TDD is a clear niche and "先写测试" / "red-green-refactor" are distinctive triggers unlikely to fire for the wrong skill, fitting 'mostly distinct; minor overlap risk'. Not anchor 5 because the trigger "或需要集成测试时" (whenever integration tests are needed) is broad — a user wanting integration tests written without a TDD process would still trigger this, overlapping any general test-writing skill; not anchor 3 because the core triggers are clearly distinctive.

4 / 5

Total

15

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 2 missing

Warning

Total

15

/

16

Passed

Repository

vinvcn/mattpocock-skills-zh-CN

Path

skills/engineering/tdd/SKILL.md

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.