Brevo Automation
v0.1.0Automate Brevo (Sendinblue) tasks via Rube MCP (Composio): manage email campaigns, create/edit templates, track senders, and monitor campaign performance. Always search tools first for current schemas.
⭐ 0· 1.2k·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
medium confidencePurpose & Capability
Name/description match the instructions: all actions are calls to Rube MCP tool actions (BREVO_*). The skill does not request unrelated credentials, binaries, or installs, and requires an existing Rube MCP connection which is consistent with the stated purpose.
Instruction Scope
Instructions stay within the Brevo-via-Rube scope (list/update campaigns, templates, senders, A/B testing). The SKILL.md directs adding an external MCP endpoint (https://rube.app/mcp) and following returned auth links to perform Brevo OAuth — this is expected for an MCP-based integration but it does instruct the agent/user to point their client at an external server, which is a meaningful trust decision.
Install Mechanism
Instruction-only skill with no install spec and no files to write or run locally. This is the lowest-risk install profile.
Credentials
No environment variables, credentials, or config paths are requested. Authentication is expected to be done via Rube's connection management (auth link/OAuth), which is proportionate to the described function.
Persistence & Privilege
always:false and no install/setup that modifies other skills or system settings. The skill can be invoked autonomously by the agent (platform default) but does not request elevated or persistent privileges itself.
Assessment
This skill appears internally consistent and uses Rube MCP tool calls as described, but before installing: 1) Verify you trust the MCP provider (rube.app) — adding an MCP endpoint hands that server the ability to mediate requests and authentication flows. 2) Confirm the Brevo authentication happens via the standard OAuth/auth link flow and that tokens remain under your control (inspect any returned connection metadata). 3) Prefer installing only if you know or can vet the MCP server (source/homepage is missing). 4) Consider testing in a low-risk account first and limit autonomous invocation until you’re comfortable with the tool behaviors.Like a lobster shell, security has layers — review code before you run it.
latestvk970nx46p30x6y76cqvke86w4s80m7bm
License
MIT-0
Free to use, modify, and redistribute. No attribution required.