SKILLEMALL.ai
RU Sign in

BB huawei-cloud-dws-cpu-diag

DWS cluster CPU high root cause diagnosis skill, based on KooCLI v3.2.0+ and DWS Autopilot MCP Server. Automatically collects CPU metrics, analyzes root causes (customer-side / system-side), and outputs a standardized diagnosis report. Applicable to DWS cluster CPU usage too high, CPU alarms, CPU load anomaly scenarios. Trigger words: "CPU高", "CPU告警", "CPU诊断", "CPU使用率过高", "CPU满", "high CPU", "CPU alarm", "CPU diagnosis"

ClawHub Agent Skills author: huaweicloud-skills-team v1.0.0 MIT-0 6 files body ≈ 7 392 tokens Open the sourceclawhub.ai↗ analyzed 2 d ago

DWS cluster CPU high root cause diagnosis skill, based on KooCLI v3.2.0+ and DWS Autopilot MCP Server. Automatically collects CPU metrics, analyzes root…

As a process B 73/100 · Nearly there — weak spots: running it twice, progress reporting

AnalyzerAI and agentsData and analyticstype and topics are labelled automatically from the skill text
Runs in: OpenClaw Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) Goose OpenCode
JSON
Technical rating
B
78/100
safety, quality, tests
Safety 60%
75
Quality 40%
83
Run on models
none yet
Process rating
B
73/100
Nearly there
Progress reporting w 2
0
Running it twice w 4
30
When it triggers w 12
50
the three weakest of ten parameters · all ten

What is at stake

Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.

Dangerous commands medium severity

Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.

If you install

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.

For the author

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

  1. The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
For the model run — optional
  • 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-privilege references/cli-installation-guide.md:27
    Privilege escalation / world-writable permissions
    sudo mv hcloud /usr/local/bin/
  • medium Dangerous commands cmd-privilege references/cli-installation-guide.md:36
    Privilege escalation / world-writable permissions
    sudo mv hcloud /usr/local/bin/
  • medium Dangerous commands cmd-privilege references/cli-installation-guide.md:45
    Privilege escalation / world-writable permissions
    sudo mv hcloud /usr/local/bin/
  • medium Dangerous commands cmd-privilege references/cli-installation-guide.md:67
    Privilege escalation / world-writable permissions
    sudo mv obsu…64_*/obsutil /usr/local/bin/
  • medium Dangerous commands cmd-privilege references/cli-installation-guide.md:76
    Privilege escalation / world-writable permissions
    sudo mv obsu…64_*/obsutil /usr/local/bin/

Files scanned: 6. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning body-long SKILL.md body ≈ 7392 tokens (recommended < 5000); move details to references/
  • note frontmatter-key unknown frontmatter key "trigger"
  • note frontmatter-key unknown frontmatter key "input_schema"
  • note frontmatter-key unknown frontmatter key "output_schema"

Process rating: all ten parameters 73/100

  • 0Progress reporting. Says nothing while it works
  • 30Running it twice. 3 mutating operations with no state check
  • 50When it triggers. No condition that starts the skill
  • 60Steps. 77 steps, 4 vague phrases
  • 60Result and completion. Output format stated, no completion criterion
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 70Execution cost. Instruction body is 7392 tokens
  • 100Tools and files. Tools declared in frontmatter
  • 100Failures and branches. 3 branches, has a failure section
  • 100Consistency. Name and required fields are in place
  • 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)
  • +1No license
  • +2Single-language instructions
  • +5Description quotes 4 example trigger phrases
  • +3Description length 423: enough signal without eating the budget
  • +4Structure: 32 headings
  • +3Step-by-step instructions: 77 items
  • +3Output format is stated explicitly
  • +4Has examples (8 code blocks)
  • +4Reference files are cited in the instructions (4 of 4)

Quality base 70; lint remarks subtract, signals add up to 100. Result: 83.

External checks

ClawHub: suspicious
The core DWS CPU diagnosis workflow is mostly read-only, but the package includes unrelated OBS credential setup and risky secret-handling instructions that users should review before installing.
LLM: suspicious (high) · 7 Jul 2026