AC huawei-cloud-account-onboarding
Checks Huawei Cloud real-name verification (实名认证) status and guides face-scan verification, read-only via hcloud: reads the account's verification state, and when unverified fetches the face-auth QR address, renders it in the terminal to scan by phone, then polls until verified. Use when the user mentions 华为云 / Huawei Cloud plus 实名认证/实名/认证状态/real-name verification, or a Huawei Cloud flow reports verification is required. Face-scan channel only; refuses ID, document, bank-card and SMS-code intake, refuses write operations (enterprise and certificate channels are console-only), and refuses non-Huawei-Cloud identity flows.
Checks Huawei Cloud real-name verification (实名认证) status and guides face-scan verification, read-only via hcloud: reads the account's verification state, and…
As a process C 52/100 · Has gaps — weak spots: result and completion, inputs and preconditions, failures and branches
How to improve
- 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 · 5
✓ No critical or high findings
Medium and low: 5
-
low Secrets in code
secret-high-entropy-tokenscripts/package-lock.json:40High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…qkQ+BMQq…Lqg==",
detector -
low Secrets in code
secret-high-entropy-tokenscripts/package-lock.json:72High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…Lkx+esve…s1Q==",
detector -
low Secrets in code
secret-high-entropy-tokenscripts/package-lock.json:88High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…7xp+Ksxi…Vkw==",
detector -
low Secrets in code
secret-high-entropy-tokenscripts/package-lock.json:280High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…TZM+N3P0…O90+1bZv…F8A/HQ==",
detector -
low Secrets in code
secret-high-entropy-tokenscripts/package-lock.json:376High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…mVs+YKyp…f7g==",
detector
Files scanned: 7. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 52/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 60Tools and files. Uses tools (node) that frontmatter does not declare
- 70When it triggers. States when to use, but not when not to
- 100Steps. 7 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 221 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
- +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
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +3Description length 627: enough signal without eating the budget
- +4Structure: 4 headings
- +3Step-by-step instructions: 7 items
- +4Reference files are cited in the instructions (2 of 2)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 87.