← Back to Skills Marketplace
6270
Downloads
0
Stars
0
Active Installs
111
Versions
Install in OpenClaw
/install vmware-monitor
Description
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.
Usage Guidance
Install with a dedicated read-only VMware account, avoid administrator credentials, prefer a secret manager over storing passwords in .env, and enable webhooks or the daemon only when you are comfortable sending operational details such as hostnames, IPs, usernames, alarms, and event text to that destination.
Capability Assessment
Credentials
The skill can reveal sensitive infrastructure inventory, events, logs, sessions, hostnames, IPs, and usernames, but this is expected for VMware monitoring and is disclosed with least-privilege guidance.
Install Mechanism
Installation uses the normal uv/PyPI package path and documentation includes pinned examples; the skill relies on an external Python package rather than bundling implementation code in the artifact.
Instruction Scope
The routing language includes broad phrases such as "is anything on fire," but the surrounding context ties them to VMware infrastructure triage and repeatedly excludes vSphere write operations.
Persistence & Privilege
Local config, credential, audit, snapshot, and daemon files are disclosed; the daemon and Slack/Discord webhooks are opt-in and user-started, with no autostart behavior shown.
Purpose & Capability
The stated purpose is read-only VMware vCenter/ESXi monitoring, and the documented capabilities align with that purpose: inventory, alarms, events, performance, capacity, sessions, host logs, health summaries, and investigations.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install vmware-monitor - After installation, invoke the skill by name or use
/vmware-monitor - Provide required inputs per the skill's parameter spec and get structured output
Version History
v2.4.2
An unreadable host is not reported as down (hosts_unreadable); NTP/inventory no longer call it unreachable; a login refused with NoPermission gets the no-role error
v2.4.1
Fixes from real-hardware testing: ESXi backup history, newest-first active tasks, honest capacity note, cluster moid, error hints
v2.4.0
Roles for network callers (HLD §18): declares role metadata so vmware-policy 1.24.0 can limit each token to a role's tools and targets.
v2.3.1
An account that logs in but has no vSphere role is named with a fix instead of failing obscurely (AIops#47); needs vmware-policy 1.23.0 (/healthz, audit correlation id). attention never reports OK when a target could not be read.
v2.3.0
Session pools: calls on one target run side by side over HTTPS (HLD §16 D-13(2)); needs vmware-policy 1.22.0. get_access_info self-diagnosis.
v2.2.0
mcp --transport https: serve MCP over HTTPS with bearer tokens (HLD §16)
v2.1.0
mcp --expose read / --allow-write: offer only read tools plus chosen write tools
v2.0.0
2.0: MCP tools renamed verb-first (see RELEASE_NOTES for the old -> new table); requires vmware-policy >= 1.18
v1.16.0
MCP instructions now name the configured targets and how to choose one; a config that cannot be read says so instead of falling silent.
v1.15.1
A stop signal always ends the server (bounded logout); active_tasks prints its unreadable-task note beside the table
v1.15.0
Results name the target that answered (default_target, target field, instructions list targets); active_tasks counts unreadable tasks; Stopping the MCP server now logs out its vCenter session.
v1.14.0
Stale alarms re-checked (license alarm cleared by evidence; unknown keeps severity), appliance alarms labelled, attention counts overlapping ESXi/vCenter hosts once, capacity views explained, perf vms balloon/swap, deployment-size without traceback.
v1.13.1
CLI reads are audited under their MCP tool names; every CLI command declares what it reaches (needs vmware-policy 1.15.0)
v1.13.0
health sensors say why a host has none; NTP source mismatch; over-committed datastores in the summary
v1.12.0
Stale-alarm verdicts, newest-first event reads with windows and routine folding, real event names ranked, grouped host logs, sessions and license assignments.
v1.11.3
host_log_scan reads host logs for the first time (0 findings before, 131 live after); unreadable logs are reported instead of looking clean; the daemon reports each line once and only critical host-log lines page the webhook; standalone hosts are no longer counted as clusters.
v1.11.2
a dropped connection no longer keeps itself alive
v1.11.1
the window this does not cover, said out loud
v1.11.0
an open backup is not a failed one
v1.10.0
_is_cluster used a leaf type name pyVmomi never reports, so every bundle lost its cluster context; event catalogue recovers 1887 extended ids; bundles no longer crash on standalone ESXi; vLCM stops counting unscannable hosts as non-compliant
Metadata
Frequently Asked Questions
What is 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. It is an AI Agent Skill for Claude Code / OpenClaw, with 6270 downloads so far.
How do I install vmware-monitor?
Run "/install vmware-monitor" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is vmware-monitor free?
Yes, vmware-monitor is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does vmware-monitor support?
vmware-monitor is cross-platform and runs anywhere OpenClaw / Claude Code is available (macos, linux).
Who created vmware-monitor?
It is built and maintained by wei zhou (@zw008); the current version is v2.4.2.
More Skills