Sendpulse
v1.0.2SendPulse integration. Manage data, records, and automate workflows. Use when the user wants to interact with SendPulse data.
⭐ 0· 117·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 (SendPulse integration) align with the instructions: using the Membrane CLI to discover connectors, create a connection, run actions, and proxy API requests to SendPulse. Nothing requested (no env vars, no config paths) appears unrelated to that purpose.
Instruction Scope
SKILL.md only instructs the agent/user to install/run the Membrane CLI, log in, create/connect a SendPulse connector, list/run actions, and optionally proxy requests. It does not instruct reading unrelated local files, harvesting environment variables, or transmitting unrelated data. The proxy capability lets you call arbitrary SendPulse endpoints via Membrane, which is expected for this integration.
Install Mechanism
Install is via npm (npm install -g @membranehq/cli) and also suggests npx usage. NPM global installs execute third-party code on the host (moderate risk), but this is a conventional install method for CLIs and the package is from the @membranehq namespace referenced in the docs. No arbitrary download URLs or archive extraction are used.
Credentials
The skill declares no required environment variables or secrets and explicitly instructs the user to rely on Membrane for auth (do not ask the user for API keys). That is proportionate for a connector-based integration.
Persistence & Privilege
always is false and the skill is user-invocable; it does not request permanent presence or ask to modify other skills or system-wide settings. The Membrane CLI will hold auth state locally as part of normal operation, which is expected.
Assessment
This skill is instruction-only and simply tells you how to use the Membrane CLI to connect to SendPulse. Before installing: (1) Confirm you trust the @membranehq CLI package and review its source (it will run code on your machine when installed globally). (2) Understand that authentication is done via Membrane in a browser flow and the CLI will store session tokens locally—treat those like any other CLI credentials. (3) The skill can proxy arbitrary SendPulse API calls via your Membrane connection, so only grant access you are comfortable with. If you prefer, inspect the Membrane CLI repository and privacy/security docs (getmembrane.com / the linked GitHub) before proceeding.Like a lobster shell, security has layers — review code before you run it.
latestvk972fnerbkhsxdddfejkb73tg1842xzc
License
MIT-0
Free to use, modify, and redistribute. No attribution required.