Do I need an API key?

No API keys are required for this workflow. You add the MCP endpoint (https://rube.app/mcp) and use RUBE_MANAGE_CONNECTIONS with the coinmarketcap toolkit to connect.

How do I ensure you are using current tool schemas?

Always call RUBE_SEARCH_TOOLS before selecting or executing any tool. Tool schemas can change, so rely on live results instead of hardcoded values.

What happens if a tool slug changes?

Re-run RUBE_SEARCH_TOOLS to retrieve updated slugs and adjust your workflow accordingly. Do not hardcode slugs; use the latest discovery results.

coinmarketcap-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Coinmarketcap Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/coinmarketcap

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["coinmarketcap"]
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 Coinmarketcap-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `coinmarketcap`
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/coinmarketcap-automation/SKILL.md

View on GitHub

Overview

Automate CoinMarketCap operations through Composio's Coinmarketcap toolkit via Rube MCP. This skill handles tool discovery, connection management, and execution workflows, ensuring you always use up-to-date tool schemas. Always call RUBE_SEARCH_TOOLS first to fetch current schemas.

How This Skill Works

You first discover available tools with RUBE_SEARCH_TOOLS to retrieve input schemas and execution plans. Next, you verify or establish the CoinMarketCap connection using RUBE_MANAGE_CONNECTIONS, then execute the chosen tool via RUBE_MULTI_EXECUTE_TOOL using the discovered slug and proper arguments. Tool schemas change, so rely on live results and always include memory in multi-execute calls.

When to Use It

When you need to perform a CoinMarketCap operation and you want the latest tool schemas before building a workflow.
When initializing or revalidating a CoinMarketCap connection to ensure ACTIVE status before tasks run.
When your workflow requires discovering multiple tools and selecting slugs at runtime.
When handling large responses, pagination tokens, or iterative data retrieval from CoinMarketCap tools.
When chaining multiple tool calls in a session, reusing session IDs and avoiding hardcoded slugs.

Quick Start

Step 1: RUBE_SEARCH_TOOLS queries: [{use_case: "Coinmarketcap operations", known_fields: ""}]
Step 2: RUBE_MANAGE_CONNECTIONS toolkits: ["coinmarketcap"], session_id: "<your_session_id>"
Step 3: RUBE_MULTI_EXECUTE_TOOL tools: [{tool_slug: "TOOL_SLUG_FROM_SEARCH", arguments: { /* schema fields */ } }], memory: {}, session_id: "<your_session_id>"

Best Practices

Always call RUBE_SEARCH_TOOLS first to fetch current tool schemas.
Check that RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools.
Do not hardcode tool slugs or arguments; rely on live search results.
Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({}).
Reuse session IDs within a workflow and handle pagination tokens if present.

Example Use Cases

Discover tools for CoinMarketCap operations, select a price fetch tool, then run it with the live schema.
Set up a new CoinMarketCap connection, verify ACTIVE status, and execute a batch of historical data tools in sequence.
Use RUBE_SEARCH_TOOLS to obtain pagination-aware results and iterate through all pages of assets.
Create a multi-step workflow that discovers, connects, and executes multiple CoinMarketCap tools in one session.
If tool slugs change, re-run RUBE_SEARCH_TOOLS to obtain fresh slugs and reconfigure your workflow accordingly.

Frequently Asked Questions

Add this skill to your agents