agent-mail-automation
npx machina-cli add skill ComposioHQ/awesome-claude-skills/agent-mail-automation --openclawAgent Mail Automation via Rube MCP
Automate Agent Mail operations through Composio's Agent Mail toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/agent_mail
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Agent Mail connection via
RUBE_MANAGE_CONNECTIONSwith toolkitagent_mail - Always call
RUBE_SEARCH_TOOLSfirst 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_TOOLSresponds - Call
RUBE_MANAGE_CONNECTIONSwith toolkitagent_mail - 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: "Agent Mail 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 Agent Mail task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["agent_mail"]
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_CONNECTIONSshows ACTIVE status before executing tools - Schema compliance: Use exact field names and types from the search results
- Memory parameter: Always include
memoryinRUBE_MULTI_EXECUTE_TOOLcalls, 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 Agent Mail-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit agent_mail |
| 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/agent-mail-automation/SKILL.mdView on GitHub Overview
Automate Agent Mail operations through Composio's Agent Mail toolkit via Rube MCP. The workflow relies on discovering current tool schemas with RUBE_SEARCH_TOOLS, establishing a connection via RUBE_MANAGE_CONNECTIONS, and executing tools with RUBE_MULTI_EXECUTE_TOOL.
How This Skill Works
Technically, you first discover available Agent Mail tools with RUBE_SEARCH_TOOLS, then verify the connection with RUBE_MANAGE_CONNECTIONS, and finally execute a chosen tool via RUBE_MULTI_EXECUTE_TOOL using the discovered tool_slug and matching schema arguments. Tool schemas are dynamic, so never hardcode slugs or fields; always reference the current schemas.
When to Use It
- When starting a new Agent Mail automation workflow and you need up-to-date tool schemas
- When performing recurring Agent Mail operations across many messages or mailboxes (bulk automation)
- When verifying the Agent Mail connection status before running workflows
- When chaining multiple Agent Mail tools within a single session for a complex task
- When onboarding or migrating to new Agent Mail tools from the Composio toolkit
Quick Start
- Step 1: Ensure Rube MCP is connected and RUBE_SEARCH_TOOLS responds
- Step 2: Discover Agent Mail tools with RUBE_SEARCH_TOOLS using the Agent Mail use case
- Step 3: Connect and then execute a tool with RUBE_MULTI_EXECUTE_TOOL using the discovered slug and memory
Best Practices
- Always run RUBE_SEARCH_TOOLS before each workflow to fetch current tool schemas
- Check that RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools
- Use exact field names and types from the search results; avoid guesswork
- Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty
- Reuse session IDs within a workflow and generate new ones for new workflows; watch for pagination in tool listings
Example Use Cases
- Automate daily Agent Mail triage to route messages to agents based on subject and sender
- Batch process multiple emails with a single workflow to create tickets in a support system
- Sync Agent Mail with a ticketing system by mapping tool outputs to required fields
- Generate a daily email activity summary and export it to a dashboard
- Onboard new tools by discovering schemas and wiring them into a workflow without hardcoding
