Wave Financial
v1.0.0Wave Financial integration. Manage data, records, and automate workflows. Use when the user wants to interact with Wave Financial data.
⭐ 0· 27·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 Wave Financial and the SKILL.md consistently instructs use of the Membrane CLI to connect to Wave, run pre-built actions, and proxy raw API requests. Requesting a Membrane account and network access is expected for this purpose.
Instruction Scope
Instructions are focused on installing and using the Membrane CLI (npm install -g @membranehq/cli), logging in, creating connections, listing/running actions, and proxying requests to the Wave API. These steps match the stated intent. Note: proxying arbitrary paths via `membrane request` will send data to Membrane for forwarding — users should be aware that API requests and responses traverse a third party.
Install Mechanism
There is no platform install spec in the registry (instruction-only), but the SKILL.md directs installing @membranehq/cli globally via npm, which is a public registry package. Installing npm packages globally executes third-party code on the host — expected for a CLI but a moderate operational risk the user should consider.
Credentials
The skill declares no required environment variables or credentials; instead it relies on Membrane-managed authentication (browser-based login). That is proportionate to its purpose. It does not request unrelated credentials or config paths.
Persistence & Privilege
The skill is not marked always:true and does not request system-level persistence. It only instructs the user to install and run a CLI; it does not attempt to modify other skills or system-wide agent settings.
Assessment
This skill appears internally consistent: it uses the Membrane CLI to access Wave data and does not ask for unrelated secrets. Before installing, confirm you trust Membrane (getmembrane.com) because authentication and API traffic will be routed through their service. Be aware that `npm install -g @membranehq/cli` runs third‑party code on your machine; prefer installing in a scoped environment or reviewing the package if you have security concerns. When running `membrane request` avoid issuing commands that expose unrelated sensitive data, and restrict the Membrane connection to only the Wave account/businesses you intend to share.Like a lobster shell, security has layers — review code before you run it.
latestvk974b8bxqpkhhazpmtdmtz17vx8442h2
License
MIT-0
Free to use, modify, and redistribute. No attribution required.