Emailoctopus

v1.0.2

Emailoctopus integration. Manage Lists, Campaigns, Templates. Use when the user wants to interact with Emailoctopus data.

0· 87·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/description (Emailoctopus integration) matches the instructions: it tells the agent to use the Membrane CLI to connect, list actions, run actions, and proxy requests to EmailOctopus. No unrelated credentials, binaries, or config paths are requested.
Instruction Scope
SKILL.md stays on-topic: it instructs installing the Membrane CLI, logging in, creating a connector, listing/running actions, and using a proxy for raw API calls. It does not instruct reading local secrets, unrelated files, or exfiltrating data to unexpected endpoints.
Install Mechanism
No install spec in the skill bundle (instruction-only). The doc recommends installing a third-party npm package globally (npm install -g @membranehq/cli). This is expected for a CLI-based integration but carries the usual risks of installing global npm packages (review source/maintainers before installing).
Credentials
The skill declares no required env vars, no primary credential, and relies on Membrane to manage auth. Requested access is proportional to the purpose; there are no unexplained SECRET/TOKEN requirements.
Persistence & Privilege
always is false and autonomous invocation is allowed (platform default). The skill does not request persistent system-wide changes or access to other skills' configs. Behavior is appropriate for a connector/integration skill.
Assessment
This skill is an instruction-only guide to using the Membrane CLI to manage EmailOctopus resources. Before installing or running commands: 1) Verify you trust the @membranehq/cli npm package and review its npm/github pages and maintainer reputation; global npm installs affect your system PATH and should be reviewed. 2) Understand that authentication is performed via Membrane (browser login), so you will authorize a remote service to act on your EmailOctopus account—review Membrane's privacy/security docs and the connector's requested scopes. 3) Avoid running CLI commands copied from unknown sources in high-privilege environments; if you need stricter isolation, run the CLI in a dedicated environment/container. If you want additional assurance, ask the skill author for a link to the exact npm package/release and the connector's requested scopes to confirm minimal permissions.

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

latestvk97eggknxdsh15mpmpe6z0em2x843kqc

License

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

Comments