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

SKILL

melo-automation

Name: melo-automation
Author: Composio

Automate Melo workflows 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 appears to be an open-source prompt/instruction set rather than executable code, with no declared local execution, secrets, or direct file access, so overall risk is low. The main consideration is its explicit reliance on remote Rube MCP and an external Melo connection, where data egress and account actions depend on those third-party services.

CredentialsCaution

The material states there are no keys or environment variables for the skill itself, but the README explicitly requires creating a `melo` connection via `RUBE_MANAGE_CONNECTIONS` and completing an auth link. So the skill does not embed static secrets, but it does trigger third-party account authorization and the scope of OAuth/connection tokens should be reviewed.

Network egressCaution

The README instructs users to add `https://rube.app/mcp` as an MCP server and use Composio/Rube to call Melo tools. This means queries, arguments, session IDs, and potentially business data may be sent to declared external services. The egress is consistent with the stated function, but it is still a normal external data flow to note.

Code executionLow risk

The system marks this as `prompt-only`, and the provided content is mainly workflow guidance and tool invocation order. There are no local scripts, binaries, shell commands, or instructions to spawn local processes. For the skill text itself, local code execution exposure appears low.

Data accessCaution

The material does not show direct access to local files or system data, but it does perform Melo 'operations' through an authorized connection and asks for session reuse, `memory`, and tool arguments, so it may access or modify data within the connected Melo account. No signs of excessive local authorization beyond the stated purpose are shown.

Supply chainLow risk

The source is a GitHub open-source repository with strong community adoption (64.7k stars). The provided content is auditable, with no obfuscated installer, closed-source binary, or obvious injection-style disguise. Although the license is unspecified and maintenance status is unknown, that is not enough on current evidence to elevate it to high risk.

Recommendations

Only add `https://rube.app/mcp` in a trusted environment, and verify your organization permits sending relevant business data to Rube/Composio.
Review the OAuth/connection scopes before authorizing the Melo connection, and prefer a least-privilege account.
Validate the actual schema and tool names returned by `RUBE_SEARCH_TOOLS` before execution to avoid mistakes from schema changes.
Do not place unnecessary sensitive information in tool arguments, memory, or session context.

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 "melo-automation" skill from askskill:
1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/melo-automation/SKILL.md
2. Save it as ~/.claude/skills/melo-automation/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// docs

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

Automate Moz SEO tasks via Rube MCP using current tool schemas first.

ComposioGet→

$ loading_