What is Melo automation via Rube MCP?

A workflow that uses Rube MCP to discover Melo tool schemas, manage Melo connections, and execute tools via the Melo toolkit.

Do I always need to search tools first?

Yes, to fetch current tool schemas and avoid hardcoding tool slugs.

What happens if tool schemas change?

RUBE_SEARCH_RULES will reflect changes; you should re-run it before execution and adapt tool_slug and arguments accordingly.

melo-automation

Scanned

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

Files (1)

SKILL.md

2.8 KB

Melo Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/melo

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Melo operations through Composio's Melo toolkit via Rube MCP. This skill orchestrates tool discovery, connection management, and execution flows, ensuring you always reference up-to-date tool schemas by calling RUBE_SEARCH_TOOLS first.

How This Skill Works

Core workflow: Discover Melo tools with RUBE_SEARCH_TOOLS, then check the connection status with RUBE_MANAGE_CONNECTIONS. When ready, execute the selected tool via RUBE_MULTI_EXECUTE_TOOL using the discovered tool_slug and schema compliant arguments, always including memory and a session_id.

When to Use It

When you need up-to-date Melo tool schemas, so you never hardcode slugs.
When initiating a Melo workflow that requires a confirmed ACTIVE connection.
When orchestrating multiple Melo tools in a single session.
When updating a Melo automation after tool schema changes.
When handling Melo tool results that require pagination during discovery.

Quick Start

Step 1: Add the Rube MCP endpoint (https://rube.app/mcp) as your MCP server and verify availability with RUBE_SEARCH_TOOLS.
Step 2: Call RUBE_MANAGE_CONNECTIONS with toolkit melo and ensure the session shows ACTIVE.
Step 3: Discover tools with RUBE_SEARCH_TOOLS, choose a tool_slug, and execute it with RUBE_MULTI_EXECUTE_TOOL using memory and your session_id.

Best Practices

Always call RUBE_SEARCH_TOOLS to fetch current tool schemas before execution.
Verify RUBE_MANAGE_CONNECTIONS reports ACTIVE before running tools.
Use exact field names and types from search results to ensure schema compliance.
Always include a memory object in RUBE_MULTI_EXECUTE_TOOL, even if empty.
Reuse session IDs within a workflow and generate new ones for new workflows.

Example Use Cases

Discovered a Melo tool slug from RUBE_SEARCH_TOOLS and ran a data-pipeline step with matching arguments.
Chained Melo tools in a single session using RUBE_MULTI_EXECUTE_TOOL and remembered state via memory.
Validated an ACTIVE Melo connection before executing any tool.
Updated an automation after a tool schema change by re-running RUBE_SEARCH_TOOLS to fetch new slugs.
Handled pagination tokens when listing Melo tools to ensure complete discovery.

Frequently Asked Questions

Add this skill to your agents