What is Rube MCP and the Dromo toolkit?

Rube MCP is an MCP server you connect to from your client. The Dromo toolkit enables performing Dromo operations via this MCP, with tool schemas fetched dynamically.

Is an API key required to use this skill?

No API keys are needed — you simply configure the MCP endpoint (e.g., https://rube.app/mcp) and proceed.

What should I do if tool schemas change after discovery?

Always re-run RUBE_SEARCH_TOOLS to fetch the latest tool slugs and input schemas before executing any tool to ensure compatibility.

dromo-automation

Scanned

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

Files (1)

SKILL.md

2.8 KB

Dromo Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/dromo

Prerequisites

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

Step 2: Check Connection

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

Overview

This skill automates Dromo operations through Composio's Dromo toolkit via Rube MCP. It emphasizes discovering current tool schemas with RUBE_SEARCH_TOOLS before running workflows to adapt to changes. A proper setup requires a connected Rube MCP and an active Dromo integration.

How This Skill Works

Connect to Rube MCP and verify tool schemas with RUBE_SEARCH_TOOLS. Then establish a Dromo connection using RUBE_MANAGE_CONNECTIONS and ensure the session is ACTIVE. Finally, execute discovered tools with RUBE_MULTI_EXECUTE_TOOL, providing exact schema fields and including memory data, while reusing sessions when appropriate.

When to Use It

Starting a new Dromo automation workflow that relies on Composio's Dromo toolkit.
When tool schemas may have changed and you must fetch the latest slugs and input schemas with RUBE_SEARCH_TOOLS.
Before running any workflow to verify the Dromo connection is ACTIVE via RUBE_MANAGE_CONNECTIONS.
Executing multiple tools in sequence within a single workflow using RUBE_MULTI_EXECUTE_TOOL.
Reusing a session ID across a workflow to improve efficiency and continuity.

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server in your client config and verify RUBE_SEARCH_TOOLS is accessible.
Step 2: Call RUBE_MANAGE_CONNECTIONS with toolkits: ["dromo"] and ensure the session_id is active.
Step 3: Use RUBE_SEARCH_TOOLS to discover tools, then run RUBE_MULTI_EXECUTE_TOOL with the chosen tool_slug and the required arguments, including memory.

Best Practices

Always call RUBE_SEARCH_TOOLS before executing any workflow to get current tool slugs and schemas.
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before running tools.
Use exact field names and types from the tool schemas returned by the search.
Include memory in every RUBE_MULTI_EXECUTE_TOOL call, even if empty ({}).
Reuse session IDs within a workflow when appropriate and generate new ones for new workflows.

Example Use Cases

Discover available Dromo tools with RUBE_SEARCH_TOOLS and execute a chosen tool slug with the required inputs.
Set up the Dromo connection via RUBE_MANAGE_CONNECTIONS and confirm ACTIVE before automating tasks.
Run a multi-tool Dromo workflow by selecting slugs from discovered tools and supplying memory state.
Sequence three Dromo actions in one workflow while reusing the same session_id for efficiency.
If tool schemas change, re-fetch schemas with RUBE_SEARCH_TOOLS before re-running the workflow.

Frequently Asked Questions

Add this skill to your agents