CC testany-case-writing
Testany platform case 编写助手 - 将传统测试场景拆解为 Testany platform cases,并生成可注册的 case packages
Testany platform case 编写助手 - 将传统测试场景拆解为 Testany platform cases,并生成可注册的 case packages
As a process C 56/100 · Has gaps — References files that are not bundled: ../testany-guide/references/task-handoff.md, ../testany-guide/references/automation-model.md, ../testany-guide/references/delivery-verification.md
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The text references files that are not there: add them or drop the references.
- 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: 9. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
missing-refreference to a missing file: ../testany-guide/references/task-handoff.md - warning
missing-refreference to a missing file: ../testany-guide/references/automation-model.md - warning
missing-refreference to a missing file: ../testany-guide/references/delivery-verification.md - warning
missing-refreference to a missing file: ../testany-case/references/executors.md
Process rating: all ten parameters 56/100
- 0Tools and files. 4 referenced file(s) missing: ../testany-guide/references/task-handoff.md, ../testany-guide/references/automation-model.md, ../testany-guide/references/delivery-verification.md
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 50Failures and branches. 0 branches, has a failure section
- 60Result and completion. Output format stated, no completion criterion
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 117 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1991 tokens
- 100Running it twice. No mutating operations
- low 12 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
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Description length 84: 120–800 characters recommended
- +1No license
- +2Single-language instructions
- +4Structure: 28 headings
- +3Step-by-step instructions: 117 items
- +3Output format is stated explicitly
- +4Has examples (1 code blocks)
- +4Reference files are cited in the instructions (2 of 2)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 67.