BC alibabacloud-ddoscoo-domain-configuration-backup
Alibaba Cloud DDoS Pro (ddoscoo) domain-level (Layer 7 website) configuration full export and import. Use for disaster recovery backup, configuration audit, rollback after misconfiguration, or batch import of domain settings. Covers 20 configuration dimensions in YAML v2.0 format. Triggers: DDoS domain config export, domain config import, domain config backup, domain config audit. Does NOT cover Layer 4 port forwarding (TCP/UDP) -- handled by `alibabacloud-ddoscoo-port-config-migration`.
Alibaba Cloud DDoS Pro (ddoscoo) domain-level (Layer 7 website) configuration full export and import.
As a process C 64/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The skill asks for more than the task needs: broad tool access, credential environment variables, binaries. Every extra permission widens the damage from a mistake or a compromise.
Narrow allowed-tools and the variable list to the minimum; replace binaries with readable sources or scripts.
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 · 7
✓ No critical or high findings
Medium and low: 7
-
medium Broad scope
meta-broad-allowed-toolsSKILL.md:1Broad tool permissions pre-approved: Bashallowed-tools: Bash Read Write AskUserQuestion
-
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 -
low Secrets in code
secret-high-entropy-tokenreferences/yaml-schema.md:92High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)http…d5: "$ReqV…md5"
quoted
A further 1 matches are quotations in this security skill's documentation and are not counted as findings.
Files scanned: 11. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 5094 tokens (recommended < 5000); move details to references/
Process rating: all ten parameters 64/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 7 mutating operations with no state check
- 40Result and completion. Does not say what the result is
- 70Execution cost. Instruction body is 5094 tokens
- 85Steps. 65 steps, 2 vague phrases
- 100Tools and files. Tools declared in frontmatter
- 100Failures and branches. 2 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- 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
- +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
- +2Single-language instructions
- +3Description length 492: enough signal without eating the budget
- +4Structure: 21 headings
- +3Step-by-step instructions: 65 items
- +4Has examples (9 code blocks)
- +4Reference files are cited in the instructions (8 of 8)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 79.