Vmware
v1.0.0VMware integration. Manage data, records, and automate workflows. Use when the user wants to interact with VMware data.
⭐ 0· 101·0 current·0 all-time
byMembrane Dev@membranedev
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name and description state a VMware integration and the SKILL.md explains use of the Membrane CLI to manage VMware resources. The declared requirements (none) match the bundle (instruction-only). The need to install a CLI and have a Membrane account is coherent with the stated purpose.
Instruction Scope
Instructions are concrete CLI steps for discovering connectors, creating connections, listing actions, running actions, and proxying requests to VMware via Membrane. They do not instruct the agent to read unrelated files, access unrelated credentials, or exfiltrate data beyond calls to Membrane/VMware. The proxy feature gives broad access to VMware APIs, which is expected for this integration.
Install Mechanism
There is no install spec in the skill bundle, but the SKILL.md tells users to run `npm install -g @membranehq/cli`. Installing a global npm package is a common way to get a CLI but does run third‑party code on the host; this instruction is proportionate to the described workflow but users should verify the package's provenance before installing.
Credentials
The skill itself requests no env vars or credentials. However, it requires a Membrane account and browser-based authentication so the user will grant Membrane access to VMware resources. That is coherent for this connector, but it means you must trust Membrane (their service will hold or broker credentials and perform API requests on your behalf).
Persistence & Privilege
The skill does not request always:true, does not alter other skills' configs, and is instruction-only (no code that writes persistent agent config). Autonomous invocation is allowed by default but is not combined with other concerning privileges.
Assessment
This skill appears to do what it says: it tells you to install the Membrane CLI and to authenticate via Membrane to manage VMware via proxy/actions. Before installing or using it: 1) Verify the @membranehq/cli npm package and the Membrane service (check official repo, package integrity, and reviews). 2) Consider using a least-privilege VMware service account when connecting rather than admin credentials. 3) Be aware that Membrane will broker API calls and hold or exchange credentials — only use it if you trust that vendor. 4) Installing a global npm package runs third-party code on your system; audit or sandbox as appropriate. 5) If operating in a highly sensitive environment, test in a non-production environment first and review audit logs in VMware and Membrane for unexpected activity.Like a lobster shell, security has layers — review code before you run it.
latestvk975ytsd7mgdje6yrs9gxqbrqn84hz5g
License
MIT-0
Free to use, modify, and redistribute. No attribution required.