BB huawei-cloud-dcs-query
Query Huawei Cloud DCS (Distributed Cache Service) instances, configurations, backups, slow logs, big key/hot key scan tasks, migration tasks, ACL accounts, IP whitelists, tags, quotas, and instance statistics. Provides read-only inspection capabilities for daily operations, performance troubleshooting, and compliance auditing. Triggers include: DCS query, list DCS instances, check Redis instance status, view cache configuration, backup records, slow logs, big key analysis, hot key analysis, migration task, ACL account, IP whitelist, instance quota, list DCS, query DCS, show DCS, DCS instance, Redis instance, 分布式缓存, DCS查询, DCS实例查询, 缓存实例.
Query Huawei Cloud DCS (Distributed Cache Service) instances, configurations, backups, slow logs, big key/hot key scan tasks, migration tasks, ACL accounts…
As a process B 67/100 · Nearly there — weak spots: result and completion, when it triggers
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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 Dangerous commands
cmd-privilegereferences/cli-installation-guide.md:12Privilege escalation / world-writable permissions (documentation of a security skill)sudo mv hcloud /usr/local/bin/
security skill -
low Dangerous commands
cmd-privilegereferences/cli-installation-guide.md:18Privilege escalation / world-writable permissions (documentation of a security skill)sudo mv hcloud /usr/local/bin/
security skill
Files scanned: 10. 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")
Process rating: all ten parameters 67/100
- 20When it triggers. No condition that starts the skill
- 40Result and completion. Does not say what the result is
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (python) that frontmatter does not declare
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 20 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1922 tokens
- 100Running it twice. No mutating operations
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
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
- -32 of 2 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 645: enough signal without eating the budget
- +4Structure: 17 headings
- +3Step-by-step instructions: 20 items
- +4Has examples (3 code blocks)
- +4Reference files are cited in the instructions (5 of 5)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 73.