CC huawei-cloud-partner-scout
Huawei Cloud BSS partner-scope read-only scout (not AWS/Azure; refuses write ops, pricing quotes, real-name review): sub-customers, partner/customer/indirect-partner balances, account flows, adjust records, indirect partners, coupon quotas, coupons, sub-customer bills, customer resources, orders, refunds via huaweicloudsdkbss SDK (KooCLI 7.2.12 ships BSS operations — `hcloud BSS <Operation>` mirrors the same partner endpoints; SDK mode is the verified path used in this skill). Triggers include: "华为云伙伴", "解决方案提供商", "总经销商", "客户列表", "账户余额", "欠费", "收支明细", "云经销商", "经销商", "代金券额度", "优惠券", "客户消费账单", "子客户账单", "月度账单", "消费子客户", "包年包月资源", "按需资源", "资源列表", "订单列表", "订单详情", "退款详情", "客户订单", "partner customer list", "partner balance", "coupon quota", "sub-customer bill", "customer order". Refuses: pay, refund, unsubscribe, create, update, delete, grant, reclaim.
Huawei Cloud BSS partner-scope read-only scout (not AWS/Azure; refuses write ops, pricing quotes, real-name review): sub-customers…
As a process C 63/100 · Has gaps — References files that are not bundled: references/semantic/models/*.yml, references/cli-installation-guide.md, references/models/*.yml
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: 17. 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") - warning
missing-refreference to a missing file: references/semantic/models/*.yml - warning
missing-refreference to a missing file: references/cli-installation-guide.md - warning
missing-refreference to a missing file: references/models/*.yml
Process rating: all ten parameters 63/100
- 0Tools and files. 3 referenced file(s) missing: references/semantic/models/*.yml, references/cli-installation-guide.md, references/models/*.yml
- 30Running it twice. 7 mutating operations with no state check
- 50When it triggers. No condition that starts the skill
- 50Failures and branches. 0 branches, has a failure section
- 70Inputs and preconditions. Inputs and preconditions are listed
- 70Execution cost. Instruction body is 4954 tokens
- 100Steps. 19 steps
- 100Result and completion. Output format and completion criterion are stated
- 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 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)
- +3Description length 856: 120–800 characters recommended
- +1No license
- +2Single-language instructions
- +5Description quotes 8 example trigger phrases
- +4Structure: 25 headings
- +3Step-by-step instructions: 19 items
- +3Output format is stated explicitly
- +4Has examples (13 code blocks)
- +4Reference files are cited in the instructions (5 of 5)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 72.