SKILLEMALL.ai

BF vmware-aiops

Use this skill whenever the user needs to manage VMs in VMware/vSphere/ESXi — it's the entry point for all VM operations. Directly handles: power on/off, clone, snapshot, migrate, deploy from OVA or templates, run commands inside VMs, batch operations, cluster management, vCenter alarm acknowledgment, a one-glance cluster-health triage ("is anything on fire?"), and VM/host/datastore investigation drill-downs. Always use this skill for any "power on", "clone", "deploy", "migrate", "batch", "guest exec", "alarm", or VM lifecycle task, and for triage like "is anything on fire" / "what needs attention now" / "investigate this VM", when the context is explicitly VMware, vSphere, or ESXi. Do NOT use for general read-only queries (inventory/events/VM details — use vmware-monitor), NSX networking (use vmware-nsx), storage/iSCSI/vSAN (use vmware-storage), or Kubernetes cluster lifecycle (use vmware-vks). For multi-step workflows use vmware-pilot. For load balancing/AVI/AKO use vmware-avi.

ClawHub Claude Code author: wei zhou v1.9.0 MIT-0 8 files body ≈ 5 584 tokens Open the sourceclawhub.ai analyzed 28 h ago

Directly handles: power on/off, clone, snapshot, migrate, deploy from OVA or templates, run commands inside VMs, batch operations, cluster management, vCenter…

As a process F 53/100 · Will not run — References files that are not bundled: ../vmware-pilot/SKILL.md, ../vmware-policy/SKILL.md

ProcedureKubernetesGitHubInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
B
87/100
safety, quality, tests
Safety 60%
95
Quality 40%
74
Run on models
none yet
Process rating
F
53/100
Will not run
References files that are not bundled: ../vmware-pilot/SKILL.md, ../vmware-policy/SKILL.md
Tools and files w 18
0
Result and completion w 14
0
Inputs and preconditions w 11
0
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. The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
  2. The text references files that are not there: add them or drop the references.
For the model run — optional
  • 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: 7. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning body-long SKILL.md body ≈ 5584 tokens (recommended < 5000); move details to references/
  • warning missing-ref reference to a missing file: ../vmware-pilot/SKILL.md
  • warning missing-ref reference to a missing file: ../vmware-policy/SKILL.md
  • note frontmatter-key unknown frontmatter key "installer"

Process rating: all ten parameters 53/100

Will not run. References files that are not bundled: ../vmware-pilot/SKILL.md, ../vmware-policy/SKILL.md
  • 0Tools and files. 2 referenced file(s) missing: ../vmware-pilot/SKILL.md, ../vmware-policy/SKILL.md
  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 70Execution cost. Instruction body is 5584 tokens
  • 85Steps. 57 steps, 1 vague phrases
  • 100When it triggers. States when to use and when not to
  • 100Failures and branches. 1 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
  • low 13 top-level sections: this looks like several domains in one skill
  • low The response is described with custom markup (12 tags): a typed call is more reliable
  • medium 4 test cases, all positive: not one "should refuse" or "should ask first"
  • low No test case covers injection arriving through data

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 994: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +5Description quotes 8 example trigger phrases
  • +4Description says when NOT to use the skill
  • +4Structure: 25 headings
  • +3Step-by-step instructions: 57 items
  • +4Has examples (3 code blocks)
  • +4Reference files are cited in the instructions (4 of 5)

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

External checks

ClawHub: suspicious
This skill is not evidently malicious, but it gives agents broad VMware control that can make destructive infrastructure and guest-OS changes without enforced approval.
LLM: suspicious (high) · 12 Sept 2026