CD test-case-design
这项技能应在为特定场景或者功能生成测试用例、编写测试用例、设计测试用例、补充异常场景和边界值、设计复杂交互测试用例、输出标准化测试用例,比如:功能测试、兼容性测试、适应性测试、API 测试、UI 可视化测试、移动端/应用/小程序/H5/桌面/PC 网页测试、AI agent测试、联动测试或路由测试等场景中使用。仅专注于编写测试用例,不涉及测试计划、测试策略或自动化脚本。
这项技能应在为特定场景或者功能生成测试用例、编写测试用例、设计测试用例、补充异常场景和边界值、设计复杂交互测试用例、输出标准化测试用例,比如:功能测试、兼容性测试、适应性测试、API 测试、UI 可视化测试、移动端/应用/小程序/H5/桌面/PC 网页测试、AI…
As a process D 35/100 · Unfinished process — References files that are not bundled: references/core-capabilities/functional-testing.md中的第一部分:测试用例设计方法+第二部分:测试用例质量标准, references/platform/{平台}.md, references/checklists/common-checklist.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 · 1
✓ No critical or high findings
Medium and low: 1
-
low Risky intent
intent-offensive-securityskill-card.md:17Offensive-security / dual-use content (legitimate for authorised testing; review intended use)QA engineers, product teams, and developers use this skill to turn software features, APIs, agent behaviors, and platform requirements into executable Markdown test case tables. It focuses on test cas
Files scanned: 20. 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: references/core-capabilities/functional-testing.md中的第一部分:测试用例设计方法+第二部分:测试用例质量标准 - warning
missing-refreference to a missing file: references/platform/{平台}.md - warning
missing-refreference to a missing file: references/checklists/common-checklist.md中的一、功能测试检查清单 - warning
missing-refreference to a missing file: references/checklists/{平台}-checklist.md
Process rating: all ten parameters 35/100
- 0Tools and files. 4 referenced file(s) missing: references/core-capabilities/functional-testing.md中的第一部分:测试用例设计方法+第二部分:测试用例质量标准, references/platform/{平台}.md, references/checklists/common-checklist.md中的一、功能测试检查清单
- 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
- 100Steps. 18 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 554 tokens
- 100Running it twice. No mutating operations
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)
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +3Description length 186: enough signal without eating the budget
- +4Structure: 5 headings
- +3Step-by-step instructions: 18 items
Quality base 70; lint remarks subtract, signals add up to 100. Result: 56.