Vectorizedio
v1.0.0Vectorized.io integration. Manage data, records, and automate workflows. Use when the user wants to interact with Vectorized.io data.
⭐ 0· 28·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 name/description state this is a Vectorized.io integration and the SKILL.md consistently instructs the agent to use the Membrane CLI to interact with Vectorized.io. Required actions (installing @membranehq/cli, creating a connection, running actions or proxied requests) align with the stated purpose.
Instruction Scope
The runtime instructions stay on-topic: install the Membrane CLI, log in via browser, list connections/actions, run actions, and proxy requests. The instructions do not ask the agent to read unrelated files, environment variables, or send data to unexpected endpoints.
Install Mechanism
This is an instruction-only skill (no code files). It asks users to install the Membrane CLI via 'npm install -g @membranehq/cli' which is a reasonable and expected mechanism for a CLI-based integration. Global npm installs carry standard supply-chain risk; verify the package name and publisher on the npm registry before installing.
Credentials
The skill declares no required environment variables, no config paths, and no primary credential. It instructs using Membrane's browser-based login flow so secrets are managed server-side, which is consistent and proportionate for this integration.
Persistence & Privilege
The skill is not forced-always (always: false) and is user-invocable. It does not request permanent agent presence or modification of other skills' configs. Autonomous invocation is allowed by default but is not combined with other concerning privileges.
Assessment
This skill appears coherent for integrating Vectorized.io via the Membrane platform. Before installing: (1) verify the @membranehq/cli package on the npm registry and confirm the publisher is legitimate, (2) be comfortable performing a global npm install or install locally instead, (3) confirm the Membrane homepage/repo (getmembrane.com and the referenced GitHub) are the official sources, and (4) avoid entering sensitive credentials outside the official Membrane browser login flow. If you need higher assurance, review Membrane's privacy/auth documentation and inspect the npm package contents or the upstream GitHub repo before installing.Like a lobster shell, security has layers — review code before you run it.
latestvk97ds5ymjqq7667t7hrca340y1847drm
License
MIT-0
Free to use, modify, and redistribute. No attribution required.