Vmware Monitor

Use this skill for safe, risk-free queries of VMware infrastructure — code-level enforced safety means no destructive operations exist in the codebase. Direc...

Before installing/using this skill: 1) Verify the package source and publisher: confirm the PyPI package and GitHub repo (https://github.com/zw008/VMware-Monitor) match and review recent commits/maintainers. 2) Confirm the installer path you plan to use (PyPI vs GitHub vs npx) and prefer pinned versions from a trusted index. 3) Inspect the code (or ask for a vetted review) to ensure no unexpected network callbacks or write operations exist — SKILL.md claims read-only but you should validate. 4) Use least-privilege vCenter accounts (read-only) for monitoring; do not store highly privileged credentials in the .env. 5) Ensure ~/.vmware-monitor/.env is chmod 600 and that you are comfortable with an audit DB at ~/.vmware/audit.db. 6) Disable or carefully configure webhooks; only point them to endpoints you control and verify payload contents in a test environment. 7) Clarify the metadata inconsistencies (manifest says no install spec but SKILL.md lists installer; primaryEnv points to a config path) with the publisher before trusting in production. If you cannot validate the package origin and code, treat it as untrusted and avoid installing with production credentials.

Type: OpenClaw Skill Name: vmware-monitor Version: 1.5.15 The vmware-monitor skill is a comprehensive read-only infrastructure monitoring tool for VMware vCenter and ESXi environments. It demonstrates strong security awareness by including built-in prompt injection mitigation (wrapping vSphere data in boundary markers), mandatory audit logging via the vmware-policy dependency, and explicit warnings against disabling SSL verification in production. All tools and CLI commands (found in SKILL.md and cli-reference.md) are strictly limited to data retrieval and monitoring, with no evidence of destructive capabilities, unauthorized data exfiltration, or malicious intent.