BB huawei-cloud-modelarts-training-diagnosis
Huawei Cloud ModelArts training job fault diagnosis skill. Uses hcloud CLI to call ModelArts training job log/event APIs, analyzes training job failures/timeouts/stuck jobs, locates customer training code issues, and provides diagnosis conclusions with fix suggestions and confidence levels. Scenarios: training job failure (status.phase=Failed), timeout (Timeout), abnormal (Abnormal), stuck jobs. Triggers: training job failure, training job timeout, training job stuck, ModelArts training diagnosis, 训练任务失败排查, 训练作业异常分析.
As a process B 77/100 · Nearly there — weak spots: when it triggers, running it twice
The same skill appears in 1 more place: ClawHub
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The skill contains commands that delete files, rewrite disks or execute code fetched from the network. The agent may run them without asking if it believes the instructions require it.
Replace destructive commands with safe equivalents that ask for confirmation, scope them to one folder, and stop piping curl into a shell: pin a version and a checksum.
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 · 5
✓ No critical or high findings
Medium and low: 5
-
medium Dangerous commands
cmd-privilegereferences/cli-installation-guide.md:49Privilege escalation / world-writable permissionssudo mv hcloud /usr/local/bin/
-
medium Dangerous commands
cmd-privilegereferences/cli-installation-guide.md:54Privilege escalation / world-writable permissionssudo mv hcloud /usr/local/bin/
-
medium Dangerous commands
cmd-privilegereferences/cli-installation-guide.md:73Privilege escalation / world-writable permissionssudo mv hcloud /usr/local/bin/
-
medium Dangerous commands
cmd-privilegereferences/cli-installation-guide.md:78Privilege escalation / world-writable permissionssudo mv hcloud /usr/local/bin/
-
medium Dangerous commands
cmd-privilegereferences/cli-installation-guide.md:157Privilege escalation / world-writable permissionssudo bash ./hcloud_install.sh
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 77/100
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 4 mutating operations with no state check
- 60Tools and files. Uses tools (python) that frontmatter does not declare
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 79 steps
- 100Result and completion. Output format and completion criterion are stated
- 100Failures and branches. 6 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3367 tokens
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 11 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
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +1No license
- +2Single-language instructions
- +3Description length 522: enough signal without eating the budget
- +4Structure: 38 headings
- +3Step-by-step instructions: 79 items
- +3Output format is stated explicitly
- +4Has examples (14 code blocks)
- +4Reference files are cited in the instructions (8 of 8)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 79.