Sendlane

v1.0.0

Sendlane integration. Manage Persons, Organizations, Lists, Tags, Broadcasts, Automations and more. Use when the user wants to interact with Sendlane data.

0· 78·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
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The name and description claim a Sendlane integration and all runtime instructions revolve around using the Membrane CLI to connect to Sendlane, list/run actions, and proxy requests. No unrelated services, binaries, or environment variables are requested.
Instruction Scope
SKILL.md stays on-topic: it tells the user/agent to install and use the Membrane CLI, perform login, create a Sendlane connection, run pre-built actions, or proxy raw API requests. It does not instruct reading unrelated files, harvesting environment variables, or exfiltrating data. Note: the doc includes commands that, if executed, will install a CLI and store auth state locally (membrane login).
Install Mechanism
There is no platform-level install spec (this is instruction-only), but the doc instructs users to run `npm install -g @membranehq/cli` or use `npx`. Installing a third-party npm package is a normal approach but carries the usual supply-chain considerations: verify the package and its publisher before installing globally.
Credentials
The skill requests no environment variables or credentials and explicitly instructs not to ask users for API keys, relying on Membrane to manage auth. It does require network access and a Membrane account, which are proportional to the stated purpose.
Persistence & Privilege
The skill is not marked always:true and does not request elevated or global agent configuration changes. It relies on the Membrane CLI and the user's Membrane login session; there is no indication it will modify other skills or system-wide settings.
Assessment
This skill appears coherent and uses Membrane to handle authentication and API proxying rather than asking you for Sendlane keys. Before installing or running the suggested commands: (1) verify the @membranehq/cli npm package and publisher (installing global npm packages writes to your system PATH), (2) be aware membrane login will open a browser and store auth state/tokens locally and that proxying requests will route data through Membrane's service—review Membrane's privacy/security docs and permissions for connectors, and (3) prefer using the provided Membrane connection flow rather than pasting API keys into the agent. If you do not trust Membrane/getmembrane.com or prefer direct control of credentials, do not run the CLI instructions and instead use a vetted alternative workflow.

Like a lobster shell, security has layers — review code before you run it.

latestvk9711p3hddeft72s87940k67q183j8ce

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments