Mailbluster
v1.0.2Mailbluster integration. Manage Campaigns, Templates. Use when the user wants to interact with Mailbluster data.
⭐ 0· 100·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 match the instructions: the SKILL.md explains how to use the Membrane CLI to manage Mailbluster campaigns/templates. Requiring a Membrane account and network access is coherent; no unrelated credentials or services are demanded.
Instruction Scope
Instructions are limited to installing and using the Membrane CLI, listing/connecting actions, and proxying API calls through Membrane. The document does not instruct reading local unrelated files, exporting environment variables, or transmitting data to unexpected endpoints.
Install Mechanism
The skill is instruction-only (no automatic install). It recommends installing @membranehq/cli via npm (-g). Installing a global npm package is a common but non-trivial operation (writes to disk, modifies PATH); this is expected for a CLI-based integration but users should only install packages from sources they trust.
Credentials
No environment variables or local secrets are requested. Authentication is delegated to Membrane's login flow (browser-based), which explains why no API keys are listed. This is proportionate to the stated purpose, but it does mean credentials are managed server-side by Membrane.
Persistence & Privilege
always: false and no install spec means the skill does not request persistent/system-wide privileges. There is no instruction to modify other skill configs or system-wide agent settings.
Assessment
This skill simply documents using the Membrane CLI to access Mailbluster and does not ask for local secrets. Before installing or running commands: 1) Confirm you trust the @membranehq/cli npm package and the getmembrane.com domain (review the package and repo if possible). 2) Prefer installing the CLI manually yourself (not via an agent action) so you can review install output. 3) Understand that Membrane will manage Mailbluster credentials server-side (you'll complete auth in a browser)—if you have privacy or compliance concerns, review Membrane's security/privacy docs. 4) If you allow an agent to run these commands, explicitly authorize each command because global npm installs and CLI logins modify your environment and may create remote credentials.Like a lobster shell, security has layers — review code before you run it.
latestvk97778zqxmajd0svqk6qdq9a9h843fgp
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
