Mailercloud
v1.0.2Mailercloud integration. Manage Organizations, Users. Use when the user wants to interact with Mailercloud data.
⭐ 0· 135·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 (Mailercloud integration) matches the instructions: the SKILL.md describes using the Membrane CLI to connect to Mailercloud, run actions, and proxy API requests. Required capabilities (network + Membrane CLI) are appropriate for the stated purpose.
Instruction Scope
Instructions are narrowly scoped to installing and using the Membrane CLI, creating connections, listing actions, running actions, and proxying requests. They do not instruct reading unrelated files, environment variables, or sending data to unexpected endpoints. Authentication is browser-based via Membrane as described.
Install Mechanism
No install spec in the skill bundle itself, but the docs instruct `npm install -g @membranehq/cli`. A global npm install is a reasonable, common mechanism for a CLI but has moderate risk compared to instruction-only (it installs code system-wide). Users should verify the npm package identity (@membranehq) and trustworthiness before installing.
Credentials
The skill declares no required env vars, no config paths, and asks users to authenticate via Membrane rather than providing API keys. That matches the stated design (Membrane manages credentials server-side) and is proportionate.
Persistence & Privilege
The skill is instruction-only (no code files, no install hooks) and does not request always:true or persistent platform-level privileges. Default autonomous invocation is allowed but is the platform default and not combined with other concerning factors.
Assessment
This skill is an instructions document for using the Membrane CLI to manage Mailercloud, and it does not request local secrets. Before using: (1) verify you trust the Membrane project and the npm package @membranehq/cli (check the npm page and GitHub repo), (2) be aware installing a global npm package requires elevated permissions and will add a CLI to your system, and (3) when authenticating in the browser review the scopes/permissions requested for the Mailercloud connection since Membrane will act as an intermediary and have access to Mailercloud data. If you prefer not to install an extra CLI, consider interacting directly with Mailercloud using your own OAuth/API keys and verified tools.Like a lobster shell, security has layers — review code before you run it.
latestvk97drmwvx9frdxsmc0hn00trth842ftc
License
MIT-0
Free to use, modify, and redistribute. No attribution required.