Vetty
v1.0.0Vetty integration. Manage data, records, and automate workflows. Use when the user wants to interact with Vetty data.
⭐ 0· 66·0 current·0 all-time
byVlad Ursul@gora050
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The skill claims to integrate with Vetty via the Membrane CLI and all required actions in SKILL.md are about installing/using that CLI. No unrelated environment variables, binaries, or config paths are requested.
Instruction Scope
Instructions are limited to installing and using the Membrane CLI, creating connections, running actions, and proxying requests to Vetty. Be aware that using the CLI will transmit data and API requests through Membrane's servers (intended behavior), so data shared with Vetty will also pass through Membrane.
Install Mechanism
No registry install spec exists, but SKILL.md instructs installing @membranehq/cli via npm (global install / npx). This is a typical approach, but installing global npm packages carries the usual supply-chain risks; verify the package and publisher (@membranehq) before installing.
Credentials
The skill requests no local env vars or secrets; authentication is performed via Membrane's browser login and managed server-side. This is proportionate to the stated purpose, though it implies Membrane will hold credentials and perform API calls on the user's behalf.
Persistence & Privilege
The skill is instruction-only, has no install spec in the registry, and does not request always:true. Running the CLI may create standard user config (expected), but the skill itself does not demand elevated or persistent platform privileges.
Assessment
This skill is coherent: it tells you to install and use the Membrane CLI to access Vetty, and it doesn't ask for unrelated secrets. Before installing, verify the npm package owner (@membranehq) and prefer using npx or containerized environments if you want to avoid a global install. Remember that connecting will allow Membrane to store/mediate credentials and see the data you send to Vetty — confirm you trust Membrane and review permission scopes when authorizing the connector. Finally, run CLI commands manually the first time to inspect outputs and confirm behavior before giving an agent autonomous control.Like a lobster shell, security has layers — review code before you run it.
latestvk977jb4ry30khfqw54dv4znqt9844nsx
License
MIT-0
Free to use, modify, and redistribute. No attribution required.