$ ~/registry/skill/composiohq-composio-skills-mailbluster-automation

SKILL

mailbluster-automation

Name: mailbluster-automation
Author: Composio

Automate Mailbluster marketing tasks via Rube MCP using current tool schemas.

Stars

★ 67,763

Source

GitHub

Updated

2026-07-15

// securityCaution

Prompt only, no code
Open source
Community-trusted· 64.7k

Summary

This skill appears to be mainly an open-source prompt/instruction wrapper with no declared local secrets, file permissions, or native code execution, so its overall risk is relatively low. The main caution is that it relies on external Rube MCP and a Mailbluster authorization flow, where actual data access and network egress would occur.

CredentialsCaution

The material says no API keys are needed, but it requires an active Mailbluster connection via `RUBE_MANAGE_CONNECTIONS` and directs users to complete auth through a returned link. So while there is no local static secret, there is still the normal risk of third-party delegated tokens/sessions being granted and potentially misused.

Network egressCaution

The README explicitly requires adding the remote MCP endpoint `https://rube.app/mcp` and using Composio/Rube to invoke Mailbluster tools. Therefore, task inputs, tool arguments, session information, and potentially Mailbluster data may be transmitted through declared external services. No clear unrelated exfiltration red flag is shown, but this is a standard external SaaS/MCP egress scenario.

Code executionLow risk

Based on the provided material, this is a prompt-only skill description that mainly instructs use of `RUBE_SEARCH_TOOLS`, `RUBE_MANAGE_CONNECTIONS`, and `RUBE_MULTI_EXECUTE_TOOL`. It does not declare that it starts local processes, runs scripts, or requests system-level execution privileges on its own.

Data accessCaution

The material does not show any need to read local files or broadly access device data, but once the Mailbluster connection is established, the skill can query or act on Mailbluster resources according to discovered tool schemas. The effective data-access scope depends on the permissions granted to the external connection and tool capabilities, so least privilege should be enforced.

Supply chainLow risk

The source is a public GitHub repository, the system marks it as open-source, and community signals are strong (64.7k stars). The visible skill content is mainly auditable documentation/prompting. Although the license and maintenance status are unclear, supply-chain risk is overall low in the absence of specific red flags.

Recommendations

Only connect this MCP endpoint after confirming you trust `rube.app`/Composio and their data-handling practices.
Grant the Mailbluster connection only the minimum required permissions, and regularly review/revoke unused authorization sessions.
Avoid sending unnecessary sensitive marketing data, customer lists, or internal notes in tool-call arguments.
Before production use, verify the actual tool schemas invoked by the skill, the account scopes involved, and available audit logging.

Audited by: gpt-5.4 · 2026-06-17

// install

Copy the install command and let the AI configure it · recommended for beginners

Please install the "mailbluster-automation" skill from askskill:
1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/mailbluster-automation/SKILL.md
2. Save it as ~/.claude/skills/mailbluster-automation/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// docs

Mailbluster Automation via Rube MCP

Automate Mailbluster operations through Composio's Mailbluster toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/mailbluster

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
Active Mailbluster connection via RUBE_MANAGE_CONNECTIONS with toolkit mailbluster
Always call RUBE_SEARCH_TOOLS first to get current tool schemas

Setup

Get Rube MCP: Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.

Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds
Call RUBE_MANAGE_CONNECTIONS with toolkit mailbluster
If connection is not ACTIVE, follow the returned auth link to complete setup
Confirm connection status shows ACTIVE before running any workflows

Tool Discovery

Always discover available tools before executing workflows:

RUBE_SEARCH_TOOLS
queries: [{use_case: "Mailbluster operations", known_fields: ""}]
session: {generate_id: true}

This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls.

Core Workflow Pattern

Step 1: Discover Available Tools

RUBE_SEARCH_TOOLS
queries: [{use_case: "your specific Mailbluster task"}]
session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["mailbluster"]
session_id: "your_session_id"

Step 3: Execute Tools

RUBE_MULTI_EXECUTE_TOOL
tools: [{
  tool_slug: "TOOL_SLUG_FROM_SEARCH",
  arguments: {/* schema-compliant args from search results */}
}]
memory: {}
session_id: "your_session_id"

Known Pitfalls

Always search first: Tool schemas change. Never hardcode tool slugs or arguments without calling RUBE_SEARCH_TOOLS
Check connection: Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing tools
Schema compliance: Use exact field names and types from the search results
Memory parameter: Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({})
Session reuse: Reuse session IDs within a workflow. Generate new ones for new workflows
Pagination: Check responses for pagination tokens and continue fetching until complete

Quick Reference

Operation	Approach
Find tools	`RUBE_SEARCH_TOOLS` with Mailbluster-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `mailbluster`
Execute	`RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs
Bulk ops	`RUBE_REMOTE_WORKBENCH` with `run_composio_tool()`
Full schema	`RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef`

Powered by Composio

Automate email validation and Mailboxlayer lookup workflows through Rube MCP.

ComposioGet→

$ loading_