AF alibabacloud-ecs-linux-os-troubleshooting
Troubleshoot an Alibaba Cloud ECS Linux OS. Use when a user needs to diagnose a specified ECS Linux instance, such as instance stuck in Starting, boot stuck, SSH/VNC/Workbench login failure, network issues, disk/FS issues, performance anomalies, suspected mining or hidden processes, crash/hang, clock drift, or configuration not taking effect.
Troubleshoot an Alibaba Cloud ECS Linux OS.
As a process F 52/100 · Will not run — References files that are not bundled: references/<slug>.md, references/utils/<component-slug>.md
How to improve
- 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 · 2
✓ No critical or high findings
Medium and low: 2
-
low Risky intent
intent-offensive-securityreferences/utils/guestos-malware-mining.md:51Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (detector / deny-list definition)- Converge the risk surface immediately: temporarily restrict outbound traffic of the instance through security group rules, change the instance logon password, and replace the key pair to block conti
detector
A further 1 matches are quotations in this security skill's documentation and are not counted as findings.
Files scanned: 54. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: references/<slug>.md - warning
missing-refreference to a missing file: references/utils/<component-slug>.md
Process rating: all ten parameters 52/100
- 0Tools and files. 2 referenced file(s) missing: references/<slug>.md, references/utils/<component-slug>.md
- 0Result and completion. Does not say what the result is
- 30Running it twice. 6 mutating operations with no state check
- 50When it triggers. No condition that starts the skill
- 70Inputs and preconditions. Inputs and preconditions are listed
- 70Execution cost. Instruction body is 4001 tokens
- 85Steps. 52 steps, 2 vague phrases
- 100Failures and branches. 6 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Progress reporting. Reports progress
- low The response is described with custom markup (7 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)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 344: enough signal without eating the budget
- +4Structure: 15 headings
- +3Step-by-step instructions: 52 items
- +4Has examples (3 code blocks)
- +4Reference files are cited in the instructions (7 of 31)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 79.