Rube MCP is an MCP server endpoint (https://rube.app/mcp) that lets you discover and manage Composio toolkit tools like Resend, enabling automated workflows.

Do I need API keys to use this skill?

No API keys are required. Add the Rube MCP endpoint to your client configuration and follow the setup steps to authorize and connect.

How do I handle schema changes?

Always run RUBE_SEARCH_TOOLS to fetch current tool slugs and input schemas before executing any tool; don't hardcode slugs or argument names.

resend-automation

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

Files (1)

SKILL.md

2.8 KB

Resend Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/resend

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["resend"]
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 Resend-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `resend`
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/resend-automation/SKILL.mdView on GitHub

Overview

This skill automates Resend operations using Composio's Resend toolkit through the Rube MCP. It emphasizes always querying current tool schemas with RUBE_SEARCH_TOOLS and validating an ACTIVE connection via RUBE_MANAGE_CONNECTIONS before workflow execution.

How This Skill Works

You first verify MCP connectivity by calling RUBE_SEARCH_TOOLS. Then you discover available Resend tool slugs and their input schemas, ensure the connection status is ACTIVE via RUBE_MANAGE_CONNECTIONS, and finally execute the chosen tool with RUBE_MULTI_EXECUTE_TOOL, supplying a memory object and session_id. The discovery response provides slugs, schemas, and recommended execution plans to guide the run.

When to Use It

When starting a new Resend automation, first discover tools with RUBE_SEARCH_TOOLS to obtain current tool schemas.
When integrating Resend via Rube MCP into an existing workflow, verify the connection is ACTIVE with RUBE_MANAGE_CONNECTIONS before executing tools.
When you need to run multiple Resend tools in sequence, follow the Core Workflow Pattern: Discover, Check, Execute, reusing session IDs where appropriate.
When processing large batches of recipients, leverage multi-tool execution or bulk ops while ensuring a memory object is provided.
When tool schemas change or results are paginated, re-run RUBE_SEARCH_TOOLS to refresh slugs and arguments.

Quick Start

Step 1: Ensure Rube MCP is connected and RUBE_SEARCH_TOOLS responds.
Step 2: RUBE_MANAGE_CONNECTIONS to attach the resend toolkit and verify ACTIVE.
Step 3: Use RUBE_SEARCH_TOOLS to discover available Resend tools, then run RUBE_MULTI_EXECUTE_TOOL with a discovered slug and memory.

Best Practices

Always call RUBE_SEARCH_TOOLS first to fetch the latest tool schemas.
Check that RUBE_MANAGE_CONNECTIONS reports ACTIVE before any execution.
Use exact field names and types from the search results; avoid hardcoding slugs or arguments.
Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty.
Reuse session IDs within a workflow; generate a new session_id for new workflows.

Example Use Cases

Discover and run a welcome_email tool for a new user using RUBE_MULTI_EXECUTE_TOOL with user_id and template_id.
Retry a failed campaign by discovering the retry_campaign tool and executing with the failed_campaign_id.
Batch resend: discover a bulk_resend tool and pass a list of recipient_ids in the arguments.
Validate that the resend connection is ACTIVE before running update_contact_preferences.
Paginate through recipients and run batch_send across pages using pagination tokens from RUBE_SEARCH_TOOLS results.

Frequently Asked Questions

Add this skill to your agents