What are the prerequisites for mezmo-automation?

RUBE_SEARCH_TOOLS must be available, a Mezmo connection must be ACTIVE via RUBE_MANAGE_CONNECTIONS with toolkit 'mezmo', and you should always search for current tool schemas before running workflows.

Do I need API keys to use this skill?

No API keys are required for the MCP endpoint; you add the MCP server (https://rube.app/mcp) in your client configuration and proceed.

How do I handle changes in tool schemas?

Always call RUBE_SEARCH_TOOLS before executing tools to get the latest tool slugs and input schemas; do not hardcode tool slugs or arguments.

mezmo-automation

Scanned

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

Files (1)

SKILL.md

2.8 KB

Mezmo Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/mezmo

Prerequisites

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

Step 2: Check Connection

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

Overview

This skill automates Mezmo operations using Composio's Mezmo toolkit through Rube MCP. It emphasizes discovering current tool schemas with RUBE_SEARCH_TOOLS before running workflows and requires an active Mezmo connection.

How This Skill Works

Start by discovering available Mezmo tools with RUBE_SEARCH_TOOLS to fetch up-to-date tool slugs and input schemas. Then confirm an ACTIVE Mezmo connection with RUBE_MANAGE_CONNECTIONS and execute the chosen tool via RUBE_MULTI_EXECUTE_TOOL using the discovered slug, passing schema-compliant arguments and a memory object. The session_id from the search results can be reused within a workflow, and you should handle pagination if tool listings are long.

When to Use It

You need to automate a Mezmo operation and must fetch current tool schemas first.
You want to verify the Mezmo connection is ACTIVE before executing tools.
You want to execute a tool discovered by a slug obtained from RUBE_SEARCH_TOOLS.
You are chaining multiple Mezmo tool executions in a single workflow using the same session.
You must handle schema changes or pagination when listing available tools.

Quick Start

Step 1: Verify Rube MCP is connected and that RUBE_SEARCH_TOOLS responds.
Step 2: Use RUBE_SEARCH_TOOLS to discover Mezmo tools and capture a tool_slug and session_id.
Step 3: Ensure the Mezmo connection is ACTIVE with RUBE_MANAGE_CONNECTIONS and run RUBE_MULTI_EXECUTE_TOOL with memory and the discovered tool slug.

Best Practices

Always call RUBE_SEARCH_TOOLS first to get current tool schemas.
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing any tools.
Use exact field names and types from search results to ensure schema compliance.
Include memory in every RUBE_MULTI_EXECUTE_TOOL call, even if empty (memory: {}).
Reuse session IDs within a workflow and generate new ones for separate runs; monitor pagination tokens.

Example Use Cases

Example 1: Automate a Mezmo ingestion job by discovering TOOL_SLUG_FROM_SEARCH and passing required arguments from the search results.
Example 2: Reuse an existing session to run two Mezmo tools sequentially in a single workflow.
Example 3: Validate ACTIVE connection status before executing any Mezmo operation and re-establish if needed.
Example 4: Update a workflow when tool schemas change by re-running RUBE_SEARCH_TOOLS to fetch new schemas.
Example 5: Execute a batch of Mezmo tasks via RUBE_REMOTE_WORKBENCH using run_composio_tool() for bulk processing.

Frequently Asked Questions

Add this skill to your agents