SKILLEMALL.ai

BF vmware-monitor

Use this skill for safe, read-only queries of VMware infrastructure — no destructive operations exist in the codebase; a test enforces it. Directly handles: a one-glance cross-cluster health summary, object-centered VM/host/datastore investigation drill-downs (correlating surrounding infrastructure + recent events), a cross-vCenter "what needs attention now?" rollup, list VMs/hosts/datastores/clusters, active alarms, recent events, VM details. Always use vmware-monitor when the user asks to "list VMs", "check vSphere alarms", "show host status", "is anything on fire", "what needs attention now", "what is happening around this VM/host/datastore", "investigate this VM" — or needs read-only VMware info before making changes. Do NOT use for any write operations — this skill is read-only and has no code path that creates, modifies, or deletes a vSphere resource. For VM modifications use vmware-aiops, for networking use vmware-nsx, for metrics/capacity use vmware-aria. For load balancing/AVI/AKO use vmware-avi.

ClawHub Agent Skills author: wei zhou v1.11.3 MIT-0 9 files body ≈ 5 591 tokens Open the sourceclawhub.ai analyzed 27 h ago

Use this skill for safe, read-only queries of VMware infrastructure — no destructive operations exist in the codebase; a test enforces it.

As a process F 47/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
85/100
safety, quality, tests
Safety 60%
93
Quality 40%
74
Run on models
none yet
Process rating
F
47/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 · 3

✓ No critical or high findings

Medium and low: 3
  • medium Broad scope meta-broad-allowed-tools SKILL.md:1
    Broad tool permissions pre-approved: Bash
    allowed-tools: Bash
  • low Exfiltration read-dotenv references/cli-reference.md:163
    Reads a .env file
    cp .env.example ~/.vmware-monitor/.env
  • low Exfiltration read-dotenv references/setup-guide.md:74
    Reads a .env file
    cp .env.example ~/.vmware-monitor/.env

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

Against the Agent Skills spec

  • warning body-long SKILL.md body ≈ 5591 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 47/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
  • 30Running it twice. 15 mutating operations with no state check
  • 50Failures and branches. 0 branches, has a failure section
  • 70Execution cost. Instruction body is 5591 tokens
  • 100Steps. 48 steps
  • 100When it triggers. States when to use and when not to
  • 100Consistency. Name and required fields are in place
  • 100Progress reporting. Reports progress
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
  • low 13 top-level sections: this looks like several domains in one skill
  • low The response is described with custom markup (5 tags): a typed call is more reliable
  • medium 3 test cases, all positive: not one "should refuse" or "should ask first"

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 1020: 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: 28 headings
  • +3Step-by-step instructions: 48 items
  • +4Has examples (3 code blocks)
  • +4Reference files are cited in the instructions (6 of 6)

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

External checks

ClawHub: clean
This is a coherent read-only VMware monitoring skill, with clearly disclosed credential, local logging, optional daemon, and webhook behavior.
LLM: benign (medium) · VirusTotal: · 12 Sept 2026