Vryno
v1.0.0Vryno integration. Manage data, records, and automate workflows. Use when the user wants to interact with Vryno data.
⭐ 0· 92·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
Benign
medium confidencePurpose & Capability
Name/description claim Vryno integration and the SKILL.md exclusively documents using the Membrane CLI to connect to Vryno and run actions — this is coherent. Minor mismatch: the registry metadata declares no required binaries, but the instructions assume npm/node (for `npm install -g @membranehq/cli` and `npx`) will be available.
Instruction Scope
Runtime instructions are scoped to installing/using the Membrane CLI, authenticating via browser, discovering connections/actions, running actions, and proxying API requests through Membrane. The instructions do not ask the agent to read local files, access unrelated env vars, or exfiltrate data outside of Membrane/Vryno — though proxying allows arbitrary Vryno API paths to be sent through Membrane (expected for this integration).
Install Mechanism
There is no formal install spec in the registry; the SKILL.md recommends `npm install -g @membranehq/cli` (and uses `npx`). Global npm installs run third-party code and write to disk; this is common but worth verifying. Prefer `npx` or verifying the package source if you want to avoid a global install.
Credentials
The skill declares no required environment variables and the docs explicitly instruct not to ask users for API keys, relying on Membrane to manage auth. That is proportionate to the described functionality. Note: using Membrane means data and auth flows go through Membrane's service.
Persistence & Privilege
The skill is instruction-only, requests no special system persistence, and is not marked always:true. It does not modify other skills or request system-wide settings.
Assessment
This skill appears to do what it says: it instructs the agent to use the Membrane CLI to connect to and call Vryno. Before installing or running commands: 1) Verify you trust the @membranehq/cli npm package and the Membrane service (homepage: getmembrane.com); global `npm install -g` executes third-party code—prefer `npx` or a container if you want to avoid global installs. 2) Understand that Membrane will proxy your Vryno API calls and handle credentials server-side, so Vryno data will flow through Membrane; review their privacy/security docs and the scopes requested during browser login. 3) Note the registry metadata omitted required binaries (npm/node) implied by the instructions—make sure your environment meets those requirements. If you need higher assurance, request a formal install spec or a signed package/source for the CLI before proceeding.Like a lobster shell, security has layers — review code before you run it.
latestvk97dm4xh9372g283q0577q8qrd84gn40
License
MIT-0
Free to use, modify, and redistribute. No attribution required.