CF alibabacloud-ecs-gpu-diagnosis
Diagnose GPU issues on Alibaba Cloud ECS GPU instances: GPU device status, driver issues, and GPU hardware failures. Use when users ask to check the GPU status of their GPU instances, detect whether the GPU device is visible, verify that the GPU driver is installed correctly, or troubleshoot GPU anomalies such as GPU not visible or deep learning task failures. Run Console Diagnosis or Cloud Assistant Diagnosis (RunCommand) to detect GPU hardware failures, perform batch diagnosis of GPU servers, or create scheduled (periodic) diagnosis tasks via CreateCommand and InvokeCommand with Cron. Single-instance diagnosis runs Console Diagnosis and Cloud Assistant Diagnosis in parallel; batch and scheduled diagnosis use Cloud Assistant Diagnosis only. Supports streaming output of diagnostic results.
As a process F 64/100 · Will not run — References files that are not bundled: references/how-to-implement-by-common-sdk.md
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
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- 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 · 7
✓ No critical or high findings
Medium and low: 7
-
medium Dangerous commands
cmd-privilegereferences/cli-installation.md:17Privilege escalation / world-writable permissionssudo mv aliyun /usr/local/bin/
-
medium Dangerous commands
cmd-privilegereferences/cli-installation.md:22Privilege escalation / world-writable permissionssudo mv aliyun /usr/local/bin/
-
medium Dangerous commands
cmd-privilegereferences/cli-installation.md:31Privilege escalation / world-writable permissionssudo mv aliyun /usr/local/bin/
-
medium Dangerous commands
cmd-privilegereferences/cli-installation.md:36Privilege escalation / world-writable permissionssudo mv aliyun /usr/local/bin/
-
medium Dangerous commands
cmd-privilegereferences/cli-installation.md:72Privilege escalation / world-writable permissionstar -xzf aliy…tgz && sudo mv aliyun /usr/local/bin/
-
low Obfuscation
obf-base64-blobSKILL.md:177Long base64-looking blob (quoted — discussed, not commanded)--command-content 'aWYg…IDI+JjE7…hlY
quoted -
low Obfuscation
obf-base64-blobSKILL.md:281Long base64-looking blob (quoted — discussed, not commanded)--command-content 'aWYg…IDI+JjE7…hlY
quoted
Files scanned: 4. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 8114 tokens (recommended < 5000); move details to references/ - warning
missing-refreference to a missing file: references/how-to-implement-by-common-sdk.md
Process rating: all ten parameters 64/100
- 0Tools and files. 1 referenced file(s) missing: references/how-to-implement-by-common-sdk.md
- 40Execution cost. Instruction body is 8114 tokens: crowds the task out of the window
- 50When it triggers. No condition that starts the skill
- 60Result and completion. Output format stated, no completion criterion
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 80 steps
- 100Failures and branches. 20 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- high The skill tells the model to perform an irreversible action with no human approval
- 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
- +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 800: enough signal without eating the budget
- +4Structure: 11 headings
- +3Step-by-step instructions: 80 items
- +3Output format is stated explicitly
- +4Has examples (22 code blocks)
- +4Reference files are cited in the instructions (2 of 2)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 75.