$ ~/registry/skill/composiohq-composio-skills-mezmo-automation

SKILL

mezmo-automation

Name: mezmo-automation
Author: Composio

Automate Mezmo tasks via Rube MCP using current tool schemas first.

Stars

★ 67,763

Source

GitHub

Updated

2026-07-15

// securityCaution

Prompt only, no code
Open source
Community-trusted· 64.7k

Summary

This skill itself is an open-source prompt/instruction set with no direct local execution or explicit secret collection, so overall risk is low. The main consideration is its reliance on external Rube MCP and Composio/Mezmo authorization flows, where real data access and actions occur through third-party remote services.

CredentialsCaution

The metadata says there are no local keys, but the README requires creating a Mezmo connection via `RUBE_MANAGE_CONNECTIONS` and completing authentication through a returned auth link, implying third-party hosted Mezmo tokens/connection state are involved. The skill text does not directly ask users to reveal secrets, but normal risks remain around delegated third-party access and over-scoped authorization.

Network egressCaution

The README instructs users to add the remote MCP endpoint `https://rube.app/mcp` and use Composio's Mezmo toolkit for tool discovery and execution; therefore task content, parameters, session IDs, and connection status may be sent to the declared third-party service. No other anomalous or unrelated egress endpoints are shown, but this remote data transmission clearly exists.

Code executionLow risk

The system flags this as `prompt-only`, and the material does not describe spawning local processes, shell execution, script installation, or system command access. This skill behaves more like usage instructions for external MCP tools than a local code-execution component.

Data accessCaution

Its stated purpose is to 'Automate Mezmo operations' via interfaces such as `RUBE_SEARCH_TOOLS`, `RUBE_MULTI_EXECUTE_TOOL`, and `RUBE_REMOTE_WORKBENCH`, which can query or perform bulk actions on Mezmo resources. There is no stated local filesystem access, but data and configuration inside the connected Mezmo account may be read, modified, or processed in bulk depending on the permissions granted to the Mezmo connection.

Supply chainCaution

Positive signals include a GitHub open-source source and strong community trust (64.7k stars); the skill itself is also documentation-like and easy to inspect. However, the license is undeclared, maintenance status is unknown, and the effective capability depends on external Rube/Composio services rather than fully auditable local code in the repository, so supply-chain transparency is not complete.

Recommendations

Only add `https://rube.app/mcp` to your client if needed, and verify its official relationship to Composio/Mezmo.
Apply least privilege when authorizing the Mezmo connection; prefer low-privilege or test accounts and avoid unnecessary write or bulk-operation scopes.
Before running `RUBE_MULTI_EXECUTE_TOOL` or bulk workflows, review the parameters, session data, and target resource scope being sent.
Ask the provider to clarify licensing, maintenance status, and data-handling practices, including how Rube/Composio store session data and OAuth credentials.

Audited by: gpt-5.4 · 2026-06-17

// install

Copy the install command and let the AI configure it · recommended for beginners

Please install the "mezmo-automation" skill from askskill:
1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/mezmo-automation/SKILL.md
2. Save it as ~/.claude/skills/mezmo-automation/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// docs

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

Automate Mem tasks through Rube MCP after checking current tool schemas first.

ComposioGet→

$ loading_