Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Vagrant
v1.0.0Vagrant integration. Manage data, records, and automate workflows. Use when the user wants to interact with Vagrant data.
⭐ 0· 58·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
Suspicious
medium confidencePurpose & Capability
The skill claims to provide a Vagrant integration and all runtime instructions use the Membrane CLI and Membrane-hosted connectors. That is coherent if Membrane actually implements a Vagrant connector. However, Vagrant is normally a local/CLI VM tool without a standard network API; the SKILL.md does not explain how Membrane will reach a user's Vagrant environment (local agent, VPN, or remote service). This missing explanation is a notable gap.
Instruction Scope
The SKILL.md stays within a narrow scope: install the Membrane CLI, authenticate, create a connection to the Vagrant connector, list actions, run actions, or proxy requests via Membrane. It does not instruct the agent to read unrelated files or env vars. The proxy feature (membrane request) can send arbitrary requests through Membrane — useful for integrations but also a high-capability feature, so the skill should document limits and where traffic is routed.
Install Mechanism
No install spec in registry, but instructions tell the user to run `npm install -g @membranehq/cli`. A global npm install is a standard but privileged operation (writes to system locations). The package is from the npm registry (public) — moderate risk but expected for a CLI. There is no download from unknown hosts or archive extraction in the skill itself.
Credentials
The skill does not request environment variables or credentials directly; it relies on Membrane's browser-based login flow. That is proportionate. However, it does not state whether the connector requires installation of a local agent or access to local Vagrant binaries/configs — if that is required, additional permissions or local access would be needed and should be declared.
Persistence & Privilege
always:false and no declared config path/auto-enabled behavior. The skill does not request persistent elevated privileges or the ability to modify other skills. The Membrane CLI will store auth state locally as normal for CLIs, which is expected.
What to consider before installing
This skill uses the Membrane service and asks you to install their global CLI and log in via a browser. Before installing, confirm with the skill author or Membrane documentation how the Vagrant connector works: specifically, does Membrane require a local agent or network access to your machine to control local Vagrant instances, or does it only target remote Vagrant-like services? Understand that the CLI will store auth tokens locally and that the `membrane request` proxy can forward arbitrary requests through Membrane — verify which endpoints it will contact and whether any sensitive internal endpoints could be exposed. If you are uncomfortable granting a third-party proxy capability to your environment, or installing a global npm package, do not install. If you proceed, limit usage to a non-sensitive environment and review Membrane's privacy/security docs and the @membranehq/cli package source before authenticating.Like a lobster shell, security has layers — review code before you run it.
latestvk97fwgxp85pp0vzab71ahxhqbh844942
License
MIT-0
Free to use, modify, and redistribute. No attribution required.