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

SKILL

bigmailer-automation

Name: bigmailer-automation
Author: Composio

Automate Bigmailer email marketing tasks and workflows through Rube MCP.

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 an open-source prompt-style wrapper, but its real actions depend on external Rube MCP and Bigmailer connections. The material does not show local code execution or built-in secrets for the skill itself, but it does route operations and potentially user data through third-party MCP services in the Composio/Bigmailer ecosystem, so the overall posture is caution rather than high risk.

CredentialsCaution

The material says 'no API keys needed', but actual use requires an ACTIVE Bigmailer connection via `RUBE_MANAGE_CONNECTIONS` and completing a returned auth link. This means credentials are not configured directly in the skill but delegated to an external Rube/Composio connection flow, creating normal OAuth/third-party connection scope and account misuse considerations.

Network egressCaution

The README explicitly requires adding the remote MCP endpoint `https://rube.app/mcp` and using it to discover tools, manage connections, and execute Bigmailer actions. User inputs, session IDs, tool arguments, and potentially business data would be sent to Rube/Composio and then used against Bigmailer, which is normal egress aligned with the stated functionality.

Code executionLow risk

Based on the material, the skill itself is a prompt/workflow instruction set and does not include auditable local script installation, shell execution, process spawning, or requests for system-level capabilities. The actual execution happens in external MCP tool calls rather than within the skill package itself.

Data accessCaution

The skill itself does not declare local file or local directory access, but its purpose is to 'Automate Bigmailer operations' and it supports bulk operations and remote workbench calls. Therefore, it may access and modify email marketing data, contacts, or campaign configurations in the Bigmailer account through external services, with scope determined by the granted connection permissions.

Supply chainLow risk

The source is an open-source GitHub repository with strong community trust (64.7k stars), which are clear risk-reducing signals. The material does not show closed-source binaries, suspicious install scripts, or unrelated high-privilege requests; limitations are that the license is unspecified, maintenance status is unknown, and the actual server-side logic of Rube/Composio cannot be fully audited from this README alone.

Recommendations

Only connect `https://rube.app/mcp` if Bigmailer automation is actually needed, and review its privacy and data-handling documentation.
Use a least-privilege account when authorizing via `RUBE_MANAGE_CONNECTIONS`, and avoid granting unnecessary write access to marketing data.
Before bulk or mutating actions, validate discovered tools and parameters in a low-risk test account.
Make sure the Rube/Composio to Bigmailer authorization is revocable, and periodically remove unused sessions or connections.

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 "bigmailer-automation" skill from askskill:
1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/bigmailer-automation/SKILL.md
2. Save it as ~/.claude/skills/bigmailer-automation/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// docs

Bigmailer Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/bigmailer

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
Active Bigmailer connection via RUBE_MANAGE_CONNECTIONS with toolkit bigmailer
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 bigmailer
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: "Bigmailer 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 Bigmailer task"}]
session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["bigmailer"]
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 Bigmailer-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `bigmailer`
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 Mailsoftly email tasks and workflows through Rube MCP.

ComposioGet→

$ loading_