What is mailcoach-automation used for?

It automates Mailcoach tasks via Composio's Rube MCP integration, handling discovery, connection, and execution.

Do I need API keys to use this skill?

No API keys are required; you add the MCP endpoint as the server (no keys needed) and proceed.

How do I handle changes to tool schemas?

Always call RUBE_SEARCH_TOOLS to fetch current schemas and avoid hardcoding slugs or arguments; update your workflow accordingly.

mailcoach-automation

Scanned

npx machina-cli add skill ComposioHQ/awesome-claude-skills/mailcoach-automation --openclaw

Files (1)

SKILL.md

2.9 KB

Mailcoach Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/mailcoach

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["mailcoach"]
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 Mailcoach-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `mailcoach`
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

Source

git clone https://github.com/ComposioHQ/awesome-claude-skills/blob/master/composio-skills/mailcoach-automation/SKILL.mdView on GitHub

Overview

Automate Mailcoach operations through Composio's Mailcoach toolkit via Rube MCP. This skill enables discovering current tool schemas, establishing an active connection, and executing Mailcoach tasks without manual steps. It emphasizes always querying tool schemas first to prevent hardcoding slugs.

How This Skill Works

First, use RUBE_SEARCH_TOOLS to fetch current tool slugs and input schemas for Mailcoach tasks. Then verify or establish an ACTIVE connection to Mailcoach with RUBE_MANAGE_CONNECTIONS for the mailcoach toolkit. Finally, execute the chosen tool via RUBE_MULTI_EXECUTE_TOOL, supplying the memory payload and the session_id.

When to Use It

Set up a new Mailcoach workflow by discovering available tools and establishing a connection to Mailcoach.
Run automation where tool schemas may change and you must fetch current slugs before execution.
Verify an ACTIVE connection is present before any execution to avoid failures.
Chain multiple Mailcoach tools within a single session to complete end-to-end tasks.
Perform bulk operations or campaigns by using discovered tool slugs and memory payloads.

Quick Start

Step 1: Ensure RUBE_SEARCH_TOOLS responds and that you have an ACTIVE Mailcoach connection via RUBE_MANAGE_CONNECTIONS.
Step 2: Discover available Mailcoach tools with RUBE_SEARCH_TOOLS to obtain slugs and input schemas.
Step 3: Execute a chosen tool with RUBE_MULTI_EXECUTE_TOOL, providing the discovered slug, memory, and the current session_id.

Best Practices

Always call RUBE_SEARCH_TOOLS before executing to get up-to-date tool slugs and schemas.
Verify RUBE_MANAGE_CONNECTIONS reports an ACTIVE status prior to execution.
Use exact field names and types from the search results; avoid hardcoding.
Include a non-null memory payload in every RUBE_MULTI_EXECUTE_TOOL call (even if empty).
Reuse session IDs within a workflow to maintain context and enable step chaining.

Example Use Cases

Discover Mailcoach tools for a new campaign workflow, connect to Mailcoach, then execute the campaign creation tool with the required arguments.
Connect to Mailcoach, fetch the latest subscriber-management tools, and bulk add subscribers from a list using the discovered tool slug.
Fetch tool schemas with RUBE_SEARCH_TOOLS, confirm ACTIVE connection, and run a tool that updates campaign status in a multi-step flow.
Paginate through tool schemas when there are many tools, then select and execute a specific tool within the same session.
Reuse a session to sequentially run tools: discovery -> connection check -> execution to complete a multi-tool Mailcoach workflow.

Frequently Asked Questions

Add this skill to your agents