Mailcoach
v1.0.2Mailcoach integration. Manage Users, EmailLists, Campaigns, Templates, Automations. Use when the user wants to interact with Mailcoach data.
⭐ 0· 108·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
Name/description (Mailcoach integration) matches the instructions: all actions are performed via the Membrane CLI and proxy to Mailcoach. No unrelated credentials, binaries, or config paths are requested.
Instruction Scope
The SKILL.md confines actions to using the Membrane CLI (login, connection list, action list/run, and proxy requests). It does not instruct the agent to read arbitrary files or system credentials. Note: most operations will route requests and credentials through Membrane's servers (the doc repeatedly says Membrane handles auth), so users should be aware that Mailcoach data and tokens will be managed by that third party.
Install Mechanism
There is no automated install spec; the doc instructs the user to install the official @membranehq/cli via npm (npm install -g). Installing a global npm package from the public registry is common for CLIs but carries the usual tradeoffs (requires privilege to install globally and trust in the package publisher). No downloads from arbitrary URLs or archive extraction are suggested.
Credentials
The skill declares no required environment variables or credentials. All authentication is delegated to Membrane's connection flow rather than asking for API keys locally, which is proportionate to the described purpose.
Persistence & Privilege
The skill does not request permanent presence (always:false) and does not instruct modification of other skills or global agent settings. It is instruction-only and will act only when invoked.
Assessment
This skill is an instruction-only integration that uses the Membrane CLI to operate on Mailcoach data. Before installing or using it: 1) Confirm you trust Membrane (https://getmembrane.com) because the CLI and proxy mean Membrane's servers will see and manage your Mailcoach credentials and API requests. 2) Verify the npm package publisher (@membranehq) and consider running the CLI in a user-level environment rather than as root. 3) Prefer creating a dedicated Membrane connection with least privilege for the work you need, and avoid copying production credentials into local files. 4) If you require stronger guarantees, review Membrane's privacy/security docs and the referenced repository code before use.Like a lobster shell, security has layers — review code before you run it.
latestvk97etk8t1p6a4d0t4mmatmcsan8433r9
License
MIT-0
Free to use, modify, and redistribute. No attribution required.