Upwave
v1.0.0Upwave integration. Manage data, records, and automate workflows. Use when the user wants to interact with Upwave data.
⭐ 0· 61·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 are consistent with the instructions: the SKILL.md documents how to connect to Upwave using the Membrane CLI and run actions or proxy requests. There are no unrelated required environment variables, binaries, or config paths.
Instruction Scope
Instructions are limited to installing and using the Membrane CLI, creating/using a connection to Upwave, listing actions, running actions, and proxying API requests. The skill does not instruct reading arbitrary local files or accessing unrelated credentials.
Install Mechanism
The skill is instruction-only (no install spec), but the SKILL.md tells users to install the Membrane CLI via npm (npm install -g @membranehq/cli). This is expected for a CLI-based integration but means users will pull a package from the npm registry — verify the package and its publisher if you care about supply-chain risk.
Credentials
No environment variables, primary credential, or config paths are required by the skill. It explicitly instructs to let Membrane handle credentials and not to ask users for API keys, which is proportional to the described functionality.
Persistence & Privilege
The skill is not set to always:true and is user-invocable. It does not request persistent system-wide changes or access to other skills' configs. Autonomous invocation is allowed (platform default), but there are no additional privilege escalations requested by the skill itself.
Assessment
This skill appears coherent: it just tells the agent how to use the Membrane CLI to interact with Upwave. Before installing/using it: (1) confirm you trust Membrane (https://getmembrane.com) and the @membranehq/cli npm package (check the npm publisher and repository), (2) be aware the CLI will open browser-based auth flows and will proxy requests to Upwave on your behalf, so only connect accounts you trust, and (3) if you are uncomfortable with an agent making live changes, avoid enabling autonomous invocation or require explicit user confirmation before running actions that modify data.Like a lobster shell, security has layers — review code before you run it.
latestvk976wna505t6s4cyx25d2bgx2d84adk0
License
MIT-0
Free to use, modify, and redistribute. No attribution required.