Marketing Master Io
v1.0.2Marketing Master IO integration. Manage Leads, Persons, Organizations, Deals, Projects, Activities and more. Use when the user wants to interact with Marketi...
⭐ 0· 128·0 current·0 all-time
byMembrane Dev@membranedev
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description match the instructions: the skill tells the agent to use the Membrane CLI to connect to Marketing Master IO and run actions or proxy API calls. The resources referenced (Membrane CLI, Membrane proxy, Marketing Master IO) are coherent with the described functionality.
Instruction Scope
Instructions stay within scope (install and use Membrane CLI, create connections, list and run actions, proxy requests). Important privacy/security note: proxying via Membrane means request/response payloads and any data you send will transit Membrane's service; the SKILL.md does not enumerate where local CLI credentials are stored or retention policies.
Install Mechanism
No formal install spec is present (instruction-only), but SKILL.md recommends installing the @membranehq/cli npm package globally (npm install -g). Installing a global npm package writes code to disk and modifies PATH — this is a moderate-risk operation relative to an instruction-only skill. The package is named and appears traceable, but the skill does not embed an explicit verified install source or checksum.
Credentials
The skill does not request environment variables, local config paths, or unrelated credentials. It explicitly instructs not to ask users for API keys and instead create connections via Membrane, which is proportionate to its purpose.
Persistence & Privilege
always is false and there is no install-time behavior in the SKILL.md that modifies other skills or system-wide agent settings. The skill does not request permanent agent presence or elevated privileges.
Assessment
This skill appears coherent with its stated purpose, but before installing/run it: 1) Verify @membranehq/cli and getmembrane.com are the legitimate project (check npmjs.org and the GitHub repo). 2) Understand that Membrane acts as a proxy and will see request/response payloads and manage auth tokens — don't send secrets you don't want routed through that service. 3) Prefer using npx or a local install if you want to avoid a global npm install, and review where the Membrane CLI stores credentials on your machine. 4) If you need stricter data controls, create a low-permission Membrane account or test in a sandbox environment first.Like a lobster shell, security has layers — review code before you run it.
latestvk97dy4zxd39yae2rgeeb074dd9843ymb
License
MIT-0
Free to use, modify, and redistribute. No attribution required.