SKILLEMALL.ai
GitHub ↗ RU Sign in

BB proxmox-aiops

Use this skill whenever the user needs to manage VMs and containers on Proxmox VE — list/inspect/configure VMs, power and lifecycle (start/stop/shutdown/reboot/reconfigure/clone/delete/migrate), snapshots (create/delete/list/rollback), disk grow/move, vzdump backups (create/list/restore), LXC containers (list/start/stop), cluster/node status, cluster resource inventory, async task polling + logs, free-VMID lookup, HA status, resource pools, firewall inspection, guest-agent ping, and storage listing. Also use it to diagnose cluster health — rank nodes by CPU/memory/disk pressure and scan guests for saturation (read-only RCA). Always use this skill for "list proxmox vms", "start proxmox vm", "stop proxmox vm", "proxmox snapshot", "proxmox backup", "restore proxmox vm", "resize proxmox disk", "proxmox vm status", "migrate proxmox vm", "proxmox container", "proxmox ha", "proxmox pool", "proxmox firewall", "list proxmox storage", "proxmox node pressure", or "why is proxmox slow" when the context is explicitly Proxmox / Proxmox VE / PVE. Do NOT use for non-Proxmox hypervisors, Kubernetes, or cloud providers. Broad coverage of common Proxmox operations, with a built-in governance harness (audit, token budget, undo, risk-tier labels).

ClawHub Claude Code author: wei zhou v0.13.1 MIT-0 6 files body ≈ 3 192 tokens Open the sourceclawhub.ai↗ analyzed 2 d ago

Use this skill whenever the user needs to manage VMs and containers on Proxmox VE — list/inspect/configure VMs, power and lifecycle…

As a process B 67/100 · Nearly there — weak spots: result and completion, inputs and preconditions, running it twice

AnalyzerKubernetesGitHubAI and agentstype 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
81/100
safety, quality, tests
Safety 60%
95
Quality 40%
59
Run on models
none yet
Process rating
B
67/100
Nearly there
Result and completion w 14
0
Inputs and preconditions w 11
0
Running it twice w 4
30
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.

Broad scope 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 asks for more than the task needs: broad tool access, credential environment variables, binaries. Every extra permission widens the damage from a mistake or a compromise.

For the author

Narrow allowed-tools and the variable list to the minimum; replace binaries with readable sources or scripts.

How to improve

  1. Shorten the description to 1024 characters.
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 · 1

✓ No critical or high findings

Medium and low: 1
  • medium Broad scope meta-broad-allowed-tools SKILL.md:1
    Broad tool permissions pre-approved: Bash
    allowed-tools: Bash

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

Against the Agent Skills spec

  • error description-long description is 1247 chars, limit 1024
  • note frontmatter-key unknown frontmatter key "slug"
  • note frontmatter-key unknown frontmatter key "displayName"
  • note frontmatter-key unknown frontmatter key "summary"
  • note frontmatter-key unknown frontmatter key "homepage"
  • note frontmatter-key unknown frontmatter key "installer"

Process rating: all ten parameters 67/100

  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 30Running it twice. 12 mutating operations with no state check
  • 50Failures and branches. 0 branches, has a failure section
  • 100Tools and files. Tools declared in frontmatter
  • 100Steps. 34 steps
  • 100When it triggers. States when to use and when not to
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 3192 tokens
  • 100Progress reporting. Reports progress
  • low 11 top-level sections: this looks like several domains in one skill
  • low The response is described with custom markup (15 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

  • +3Description length 1246: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • -44 reference files, but SKILL.md never points to them: the model will not open them
  • +2Single-language instructions
  • +5Description quotes 16 example trigger phrases
  • +4Description says when NOT to use the skill
  • +4Structure: 20 headings
  • +3Step-by-step instructions: 34 items
  • +4Has examples (3 code blocks)
  • +1License stated

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

External checks

ClawHub: suspicious
This Proxmox administration skill is purpose-aligned, but it needs Review because it can make destructive infrastructure changes and its setup leaves credential handling, TLS, and package provenance risks under user control.
LLM: suspicious (medium) · 12 Sept 2026