benchmark-email-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/benchmark-email-automation --openclawBenchmark Email Automation via Rube MCP
Automate Benchmark Email operations through Composio's Benchmark Email toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/benchmark_email
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Benchmark Email connection via
RUBE_MANAGE_CONNECTIONSwith toolkitbenchmark_email - 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 toolkitbenchmark_email - 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: "Benchmark Email 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 Benchmark Email task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["benchmark_email"]
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 Benchmark Email-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit benchmark_email |
| 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/benchmark-email-automation/SKILL.mdView on GitHub Overview
This skill automates Benchmark Email operations through Composio's Benchmark Email toolkit via Rube MCP. It emphasizes discovering current tool schemas before each workflow and ensuring a live ACTIVE connection prior to execution. By systematizing discovery, connection management, and execution, it reduces manual steps and errors.
How This Skill Works
You start by verifying Rube MCP availability with RUBE_SEARCH_TOOLS and discovering tool slugs for Benchmark Email tasks. Then you manage the Benchmark Email connection with RUBE_MANAGE_CONNECTIONS, ensure it is ACTIVE, and finally run the tool via RUBE_MULTI_EXECUTE_TOOL using the discovered slug and a memory payload.
When to Use It
- Automate a standard Benchmark Email workflow end-to-end (discover tools, connect, execute) for a new task.
- When tool schemas may change, always re-scan with RUBE_SEARCH_TOOLS before running workflows.
- Before any execution, verify the connection status is ACTIVE to avoid failed runs.
- Reuse a session ID across multiple steps in a single automation workflow for efficiency.
- Perform bulk Benchmark Email operations by integrating with RUBE_REMOTE_WORKBENCH and run_composio_tool.
Quick Start
- Step 1: Verify Rube MCP availability by calling RUBE_SEARCH_TOOLS.
- Step 2: Ensure Benchmark Email connection is ACTIVE via RUBE_MANAGE_CONNECTIONS.
- Step 3: Discover tools with RUBE_SEARCH_TOOLS, then execute a tool with RUBE_MULTI_EXECUTE_TOOL using the discovered slug and memory: {}.
Best Practices
- Always call RUBE_SEARCH_TOOLS first to get current tool slugs and schemas.
- Check that RUBE_MANAGE_CONNECTIONS reports ACTIVE before executing tools.
- Use exact field names and types from the search results to ensure schema compliance.
- Include the memory parameter in RUBE_MULTI_EXECUTE_TOOL calls, even if empty.
- Reuse session IDs within a workflow and generate a new one only for new workflows.
Example Use Cases
- Automate a monthly Benchmark Email campaign: discover tools, connect to the benchmark_email toolkit, and execute the send tool with proper arguments.
- Update contact lists and trigger targeted emails by discovering the appropriate tool slugs and executing via RUBE_MULTI_EXECUTE_TOOL.
- Fetch current tool schemas with RUBE_SEARCH_TOOLS before building a new automation to avoid hardcoding slugs.
- Reuse a session ID across steps in a single workflow to optimize performance and avoid re-authentication.
- Perform bulk email operations by using RUBE_REMOTE_WORKBENCH and run_composio_tool across multiple tool slugs.
