AB huawei-cloud-dws-list
List DWS (Data Warehouse Service) clusters under a Huawei Cloud tenant and return only the cluster names. Based on KooCLI (hcloud) DWS ListClusters API. Useful for daily inspection, resource inventory, and quick cluster overview. Triggers include: "查询DWS列表", "DWS集群列表", "列出DWS", "DWS集群名称", "list DWS clusters", "DWS cluster list", "show DWS names", "DWS inventory"
List DWS (Data Warehouse Service) clusters under a Huawei Cloud tenant and return only the cluster names.
As a process B 71/100 · Nearly there — weak spots: when it triggers, progress reporting
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 · 0
✓ No critical or high findings
Files scanned: 11. 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") - note
frontmatter-keyunknown frontmatter key "trigger" - note
frontmatter-keyunknown frontmatter key "input_schema" - note
frontmatter-keyunknown frontmatter key "output_schema"
Process rating: all ten parameters 71/100
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 70Inputs and preconditions. Inputs and preconditions are listed
- 85Steps. 28 steps, 1 vague phrases
- 100Result and completion. Output format and completion criterion are stated
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1526 tokens
- 100Running it twice. No mutating operations
- low The response is described with custom markup (4 tags): a typed call is more reliable
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)
- -31 of 3 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +5Description quotes 7 example trigger phrases
- +3Description length 364: enough signal without eating the budget
- +4Structure: 13 headings
- +3Step-by-step instructions: 28 items
- +3Output format is stated explicitly
- +4Has examples (4 code blocks)
- +4Reference files are cited in the instructions (5 of 5)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 78.