Vectera

v1.0.0

Vectera integration. Manage data, records, and automate workflows. Use when the user wants to interact with Vectera data.

0· 33·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
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The skill is described as a Vectera integration and all runtime instructions show how to use the Membrane CLI to connect to Vectera, discover actions, run actions, and proxy requests. Requiring a Membrane account and network access is coherent with the stated purpose.
Instruction Scope
SKILL.md confines its instructions to installing and using the Membrane CLI, creating/using a connector, running actions, and proxying requests. It does not instruct reading unrelated files, requiring additional environment variables, or sending data to unexpected endpoints. It does require interactive browser-based authentication (or a headless completion flow).
Install Mechanism
There is no formal install spec in the registry (instruction-only), but the docs recommend installing @membranehq/cli globally via npm (npm install -g). This is a reasonable instruction for CLI use, but global npm installs execute code from the public registry and may require elevated privileges; consider using npx or a local install if you prefer not to install global binaries.
Credentials
The skill declares no required env vars or credentials and explicitly advises against asking users for API keys. Authentication is performed via Membrane's browser-based flow, meaning Membrane (the third-party service) will hold the Vectera tokens — this is expected but worth noting from a privacy/trust perspective.
Persistence & Privilege
The skill does not request always: true or any elevated persistent presence, and it does not modify other skills or system-wide agent settings. Autonomous invocation is allowed (platform default), which is normal for skills.
Assessment
This skill appears coherent: it uses the Membrane CLI as a proxy to access Vectera and does not ask for unrelated credentials. Before installing/using it, verify you trust Membrane (getmembrane.com and the referenced GitHub repo), because Membrane will hold access tokens and proxy requests to Vectera. If you prefer not to install global npm packages, use npx @membranehq/cli or a local install. During login you'll grant access via a browser consent flow — review the permissions shown. If you need stricter control, consider reviewing Membrane's privacy/security docs and the connector's requested scopes before proceeding.

Like a lobster shell, security has layers — review code before you run it.

latestvk97d2cmm0spw6zcwhk6xcv0nh58476he

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments