AD test-gen
为已有项目生成单元测试和 E2E 测试。分析设计文档和函数签名（黑盒）， 评审可测试性设计缺陷，生成测试代码并产出覆盖率报告。 Use when: "generate tests", "add tests", "补测试", "生成单测", "write unit tests", "add e2e tests", "测试覆盖率"。 Proactively suggest when user has an existing project with insufficient test coverage and asks about quality or stability.
As a process D 41/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 6. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 41/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 40Consistency. Frontmatter name (test-gen) differs from the folder (gen-test)
- 60Tools and files. Uses tools (python, node) that frontmatter does not declare
- 100Steps. 102 steps
- 100Execution cost. Instruction body is 2420 tokens
- 100Running it twice. No mutating operations
- low 11 top-level sections: this looks like several domains in one skill
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +5Description quotes 4 example trigger phrases
- +3Description length 288: enough signal without eating the budget
- +4Structure: 31 headings
- +3Step-by-step instructions: 102 items
- +4Has examples (13 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 89.