AB alibabacloud-waf-quick-showcase
Solution skill for using WAF to protect web applications on ECS. Used for quickly deploying network environments including VPC, security groups, and ECS instances, and integrating WAF for web application protection. Trigger words: "WAF protection", "ECS web protection", "Web Application Firewall", "website security"
As a process B 70/100 · Nearly there — weak spots: result and completion, when it triggers
How to improve
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- 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 · 6
✓ No critical or high findings
Medium and low: 6
-
low Dangerous commands
cmd-privilegereferences/cli-installation-guide.md:30Privilege escalation / world-writable permissions (documentation of a security skill)sudo mv aliyun /usr/local/bin/
security skill -
low Dangerous commands
cmd-privilegereferences/cli-installation-guide.md:45Privilege escalation / world-writable permissions (documentation of a security skill)sudo mv aliyun /usr/local/bin/
security skill -
low Dangerous commands
cmd-privilegereferences/cli-installation-guide.md:58Privilege escalation / world-writable permissions (documentation of a security skill)sudo mv aliyun /usr/local/bin/
security skill -
low Dangerous commands
cmd-privilegereferences/cli-installation-guide.md:71Privilege escalation / world-writable permissions (documentation of a security skill)sudo mv aliyun /usr/local/bin/
security skill
A further 2 matches are quotations in this security skill's documentation and are not counted as findings.
Files scanned: 7. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 5665 tokens (recommended < 5000); move details to references/
Process rating: all ten parameters 70/100
- 20When it triggers. No condition that starts the skill
- 40Result and completion. Does not say what the result is
- 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
- 70Inputs and preconditions. Inputs and preconditions are listed
- 70Execution cost. Instruction body is 5665 tokens
- 100Steps. 5 steps
- 100Failures and branches. 17 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 10 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 317: enough signal without eating the budget
- +4Structure: 26 headings
- +3Step-by-step instructions: 5 items
- +4Has examples (17 code blocks)
- +4Reference files are cited in the instructions (5 of 5)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 83.