Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Vmware Storage
v1.5.11Use this skill whenever the user needs to manage VMware storage — datastores, iSCSI targets, and vSAN clusters. Directly handles: browse datastores, scan for...
⭐ 0· 361·0 current·0 all-time
by@zw008
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
medium confidencePurpose & Capability
The declared binary (vmware-storage), primary env var (VMWARE_STORAGE_CONFIG), and config files (~/.vmware-storage/config.yaml and ~/.vmware-storage/.env) are coherent with a CLI tool that manages vSphere storage. Requested capabilities (datastore browsing, iSCSI, vSAN checks) match the description and referenced CLI commands.
Instruction Scope
SKILL.md and references are prescriptive about using a local MCP stdio tool and vSphere API only, but they also reference a webhook_url (notify.webhook_url) in config.example.yaml while elsewhere claiming "No webhooks or outbound network calls — this skill is local-only." Additionally, the runtime/audit/policy files live under ~/.vmware (e.g., ~/.vmware/audit.db and ~/.vmware/rules.yaml) rather than the ~/.vmware-storage directory declared in requires.config; that means the skill will read/write to a sibling user directory (~/.vmware) not listed in the skill's declared config paths. These are scope/information-surface inconsistencies the user should understand before installing.
Install Mechanism
This is an instruction-only skill with no install spec or embedded code; that minimizes supply-chain risk from the skill bundle itself. The CLI binary 'vmware-storage' must be installed by the user (uv tool / pip / source). The installer notes are standard and expected for this type of tool.
Credentials
The declared environment variables (VMWARE_STORAGE_CONFIG and per-target VMWARE_<TARGET>_PASSWORD variables via .env) are appropriate for vSphere access. However, the skill also depends on/creates audit and policy files in ~/.vmware (e.g., ~/.vmware/audit.db, ~/.vmware/rules.yaml) which are not listed in the requires.config entries; this grants the skill read/write access to an additional user-owned directory outside the declared ~/.vmware-storage path and could overlap with other companion skills' data. The .env file holding passwords is expected, but ensure its permissions (600) and that only trusted accounts can read it.
Persistence & Privilege
The skill is not always-enabled and is user-invocable (normal). It requires a local CLI and expects to be registered as an MCP stdio tool in agent configs (examples provided). Autonomous invocation is allowed (platform default) — which is normal — but remember that if the agent can invoke the skill it will have access to the vSphere credentials provided via environment/.env. There is no evidence the skill modifies other skills' configs, but it does write audit logs to ~/.vmware/audit.db (local persistence).
What to consider before installing
This skill is broadly consistent with a VMware storage CLI, but review a few things before installing: 1) Inspect the vmware-storage binary/source from the referenced GitHub repo (uv/pip installs pull external code). 2) Confirm whether your environment will allow the skill to access ~/.vmware (audit DB and rules) in addition to ~/.vmware-storage — the skill will read/write there even though only ~/.vmware-storage is listed in some places. 3) Check for any configured webhook URL in your config.yaml (the docs include a webhook field despite a claim of "no webhooks"). 4) Keep the ~/.vmware-storage/.env file permissions to 600 and limit who can read it; the tool expects per-target passwords in environment variables. 5) If you allow an agent to invoke this skill, be aware the agent gains the ability to perform storage write actions (iscsi add/remove/enable) using the provided credentials; require dry-run and double-confirmations for write operations and audit the ~/.vmware/audit.db for operations. If possible, review the vmware-policy code (vmware-policy dependency) and the GitHub repo history to ensure no unexpected network callbacks or third-party telemetry are present.Like a lobster shell, security has layers — review code before you run it.
latestvk972bz7eje9ce6dd18ksy70egs84zj35
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
🗄️ Clawdis
OSmacOS · Linux
Binsvmware-storage
EnvVMWARE_STORAGE_CONFIG
Config~/.vmware-storage/config.yaml, ~/.vmware-storage/.env
Primary envVMWARE_STORAGE_CONFIG