Neverbounce
v1.0.2Neverbounce integration. Manage data, records, and automate workflows. Use when the user wants to interact with Neverbounce data.
⭐ 0· 123·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
medium confidencePurpose & Capability
The name/description (Neverbounce integration) aligns with the instructions (use Membrane to call Neverbounce). However, the skill metadata declares no required binaries while SKILL.md repeatedly instructs installing and using the 'membrane' CLI — a metadata mismatch to be aware of.
Instruction Scope
SKILL.md stays on-task: it describes installing Membrane CLI, authenticating via browser, creating connections, listing/running actions, and proxying requests to Neverbounce. It does not instruct reading unrelated files or exfiltrating secrets; it explicitly advises not to ask users for API keys.
Install Mechanism
There is no formal install spec in the registry (instruction-only). The doc tells users to run 'npm install -g @membranehq/cli' — a typical public npm install but one that modifies global system state. Because installs are manual (not automated by the skill) the risk is moderate; verify the '@membranehq/cli' package and its provenance before installing globally.
Credentials
The skill requests no environment variables or credentials in metadata. Authentication is delegated to Membrane and performed interactively in-browser, which is proportionate for a connector-style integration.
Persistence & Privilege
always:false and default invocation settings are used. The skill does not request persistent system-wide privileges or attempt to modify other skills' configs.
Assessment
This skill appears to do what it says: drive Neverbounce via the Membrane CLI. Before installing/using it: (1) verify the @membranehq/cli package (check npm and the GitHub repo) and prefer installing it in a controlled environment rather than globally on a shared machine; (2) confirm you are comfortable authenticating your Membrane account in-browser (Membrane will hold the Neverbounce credentials); (3) note the registry metadata omits the 'membrane' binary requirement — expect to install that CLI; and (4) if you have concerns about autonomous agent actions, restrict the agent's permission to invoke skills or review activity logs when first using the connector.Like a lobster shell, security has layers — review code before you run it.
latestvk977grqc0d5b9hcz9aefac7m098439e5
License
MIT-0
Free to use, modify, and redistribute. No attribution required.