BF test-case-design
This skill should be used when generating test cases, writing test cases, designing test cases, supplementing exception scenarios and boundary values, designing complex interaction test cases, or outputting standardized test cases for specific scenarios or features, such as: functional testing, compatibility testing, adaptation testing, API testing, UI visual testing, mobile/App/mini-program/H5/desktop/PC Web testing, AI Agent testing, linkage testing, or routing testing. It only focuses on writing test cases and does not involve test plans, test strategies, or automation scripts.
As a process F 26/100 · Will not run — References files that are not bundled: references/platform/{platform}.md, references/checklists/{platform}-checklist.md
How to improve
- 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 · 2
✓ No critical or high findings
Medium and low: 2
-
low Risky intent
intent-offensive-securityreferences/core-capabilities/api-testing.md:75Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (test fixture / example file)| Unauthorized Access | Horizontal privilege escalation (IDOR, modifying resource ID to access others' data), vertical privilege escalation (using normal Token to access admin APIs) |
fixture -
low Risky intent
intent-offensive-securitySKILL.md:29Offensive-security / dual-use content (legitimate for authorised testing; review intended use)❌ Cannot generate: Test plans, test strategies, test planning documents, penetration testing execution, vulnerability scanning, performance/stress testing (concurrency/stress/load), automation scripts
Files scanned: 20. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Nested mappings are not allowed in compact mappings at line 2, column 14: description: This skill should be used when generating test cases, writing test… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value - warning
missing-refreference to a missing file: references/platform/{platform}.md - warning
missing-refreference to a missing file: references/checklists/{platform}-checklist.md
Process rating: all ten parameters 26/100
- 0Tools and files. 2 referenced file(s) missing: references/platform/{platform}.md, references/checklists/{platform}-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
- 30Running it twice. 2 mutating operations with no state check
- 40Consistency. Frontmatter name (test-case-design) differs from the folder (software-test-case-design)
- 85Steps. 18 steps, 1 vague phrases
- 100Execution cost. Instruction body is 910 tokens
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 587: 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: 61.