Unbounce
v1.0.2Unbounce integration. Manage data, records, and automate workflows. Use when the user wants to interact with Unbounce data.
⭐ 0· 77·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 (Unbounce integration) match the instructions: all runtime steps use the Membrane CLI to discover and run Unbounce actions or proxy API requests. No unrelated services, env vars, or system paths are requested.
Instruction Scope
Instructions stay within the integration scope (install Membrane CLI, login, create/connect to Unbounce, list/run actions, or proxy requests). One important runtime detail: requests and auth are proxied through Membrane’s service (per the docs). That means Unbounce data and credentials are handled by Membrane servers during flows that use 'membrane request' or connections—this is expected but relevant for privacy/security decisions.
Install Mechanism
The skill is instruction-only (no install spec). It instructs users to install the @membranehq/cli package via npm (global or npx). Installing a public npm package is a common pattern but carries the usual supply-chain risk—verify the package and repository authenticity before installing globally.
Credentials
The skill declares no required environment variables or local credentials and explicitly advises using Membrane-managed connections rather than asking for API keys. Requested access (a Membrane account and network) is proportional to the stated purpose.
Persistence & Privilege
The skill does not request always:true and does not modify other skills or system-wide settings. It allows normal autonomous invocation (platform default).
Assessment
This skill is coherent with its description: it relies on the Membrane CLI to connect to Unbounce and does not ask for unrelated credentials. Before installing or using it, verify the @membranehq/cli package and its GitHub repo (owner, recent commits, npm publisher) to ensure you trust the code and publisher. Remember that connections and proxied requests go through Membrane’s servers—if your data is sensitive, review Membrane’s privacy/security posture and the Unbounce connection scopes before granting access. When installing, prefer using npx for one-off runs or inspect the package contents rather than doing a blind global npm install.Like a lobster shell, security has layers — review code before you run it.
latestvk97fjdwtwetrw7a13fynr41swh842t3b
License
MIT-0
Free to use, modify, and redistribute. No attribution required.