BF huawei-cloud-obs-list-excel
Query OBS bucket and object listings, then export them to an Excel (.xlsx) report. Triggers include: "list OBS buckets", "export OBS to Excel", "OBS inventory", "列出OBS存储桶", "导出OBS列表", "OBS报表".
Query OBS bucket and object listings, then export them to an Excel (.xlsx) report. Triggers include: "list OBS buckets", "export OBS to Excel", "OBS…
As a process F 43/100 · Will not run — References files that are not bundled: references/cli-installation-guide.md
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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 · 0
✓ No critical or high findings
Files scanned: 10. 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: Query OBS bucket and object listings, then export them to an Excel… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value - warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
missing-refreference to a missing file: references/cli-installation-guide.md
Process rating: all ten parameters 43/100
- 0Tools and files. 1 referenced file(s) missing: references/cli-installation-guide.md
- 0Result and completion. Does not say what the result is
- 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
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 16 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 814 tokens
- 100Running it twice. No mutating operations
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
- -32 of 3 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +5Description quotes 5 example trigger phrases
- +3Description length 192: enough signal without eating the budget
- +4Structure: 11 headings
- +3Step-by-step instructions: 16 items
- +4Has examples (4 code blocks)
- +4Reference files are cited in the instructions (3 of 4)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 62.