Vext
v1.0.2Vext integration. Manage data, records, and automate workflows. Use when the user wants to interact with Vext data.
⭐ 0· 88·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 Vext and its SKILL.md exclusively instructs use of the Membrane CLI (membrane) to create connections, run actions, and proxy API requests — this is consistent. Minor mismatch: the instructions expect npm/npx to be available for installing/running @membranehq/cli, but 'required binaries' in the registry metadata lists none.
Instruction Scope
Instructions focus on installing and using the Membrane CLI, logging in, creating connections, listing/running actions, and proxying requests to Vext. They do not instruct reading arbitrary local files or exfiltrating environment variables. Network access and a Membrane account are explicitly required.
Install Mechanism
There is no automated install spec (instruction-only). SKILL.md recommends installing @membranehq/cli via npm -g or using npx — a public npm package. This is a common pattern but implies downloading third-party code at runtime; the skill itself does not bundle or auto-install code.
Credentials
The skill declares no required environment variables or credentials and explicitly instructs not to ask users for API keys, instead relying on Membrane's connection flow. Requested access is proportionate to the described function.
Persistence & Privilege
The skill is instruction-only, has no install-time persistence, and does not request elevated or system-wide privileges. always:false (default) and standard autonomous invocation settings are in place.
Assessment
This skill is internally consistent: it expects you to install and use the Membrane CLI to manage Vext connections and run actions. Before installing or following the instructions: 1) Be prepared to run npm or npx (.e.g. have Node/npm installed) or prefer npx to avoid a global install. 2) Verify you trust Membrane (@membranehq/cli on npm and the getmembrane.com service) because the CLI will handle authentication and forward requests to Vext on your behalf. 3) Use a test account or least-privilege workspace when first trying the connector, and avoid running commands that send sensitive data until you confirm behavior. 4) If you need higher assurance, review the @membranehq/cli package source and Membrane's docs/terms and confirm connector IDs before connecting.Like a lobster shell, security has layers — review code before you run it.
latestvk974a3p25y3d78x38m6jcnr7hh843fjg
License
MIT-0
Free to use, modify, and redistribute. No attribution required.