home / skills / composiohq / awesome-claude-skills / melo-automation

melo-automation skill

safe

/melo-automation

This skill automates Melo tasks through Rube MCP, ensuring tool schemas are refreshed first for accurate workflow execution.

npx playbooks add skill composiohq/awesome-claude-skills --skill melo-automation

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

2.8 KB

---
name: melo-automation
description: "Automate Melo tasks via Rube MCP (Composio). Always search tools first for current schemas."
requires:
  mcp: [rube]
---

# Melo Automation via Rube MCP

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

**Toolkit docs**: [composio.dev/toolkits/melo](https://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.

1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `melo`
3. If connection is not ACTIVE, follow the returned auth link to complete setup
4. 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](https://composio.dev)*

Overview

This skill automates Melo operations using Composio’s Melo toolkit via the Rube MCP. It guides tool discovery, connection management, and safe execution patterns so you can run Melo workflows reliably. The focus is on always querying current tool schemas and reusing sessions for consistency.

How this skill works

The skill drives three core Rube MCP calls: RUBE_SEARCH_TOOLS to discover available Melo tools and their input schemas, RUBE_MANAGE_CONNECTIONS to verify the Melo connection is active, and RUBE_MULTI_EXECUTE_TOOL to run one or more tools using schema-compliant arguments. It enforces including memory, reusing session IDs within a workflow, and handling pagination when listing tools or responses.

When to use it

Automate Melo tasks that require dynamically discovered tool schemas
Run multi-step Melo workflows that call several composio tools in sequence
Perform bulk operations using run_composio_tool() via RUBE_REMOTE_WORKBENCH
Before any Melo execution to verify the connection is ACTIVE
When tool schemas may change between runs and you need current inputs

Best practices

Always call RUBE_SEARCH_TOOLS first — never hardcode tool slugs or argument shapes
Call RUBE_MANAGE_CONNECTIONS and confirm status is ACTIVE before executing tools
Include the memory parameter in RUBE_MULTI_EXECUTE_TOOL calls even if empty ({}).
Reuse a session_id across the workflow; generate a new session for a fresh workflow run
Watch for pagination tokens in search responses and fetch until complete

Example use cases

Discover Melo tool slugs and input fields, then execute a single tool to update Melo data
Verify and re-authenticate the Melo toolkit connection before running nightly automation
Run a bulk migration with RUBE_REMOTE_WORKBENCH calling run_composio_tool() across many items
Build an agent that searches available Melo operations, composes a multi-step plan, and executes via RUBE_MULTI_EXECUTE_TOOL

FAQ

What if RUBE_MANAGE_CONNECTIONS shows the toolkit is not ACTIVE?

Follow the returned auth link to complete setup, then call RUBE_MANAGE_CONNECTIONS again until the status reports ACTIVE.

How do I handle schema changes between runs?

Always call RUBE_SEARCH_TOOLS at the start of every run to retrieve current tool schemas and recommended execution plans; adapt your arguments to the returned field names and types.