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

dromo-automation skill

safe

/dromo-automation

This skill automates Dromo tasks via Rube MCP, always discovering current tool schemas before execution to ensure accurate tool usage.

npx playbooks add skill composiohq/awesome-claude-skills --skill dromo-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: dromo-automation
description: "Automate Dromo tasks via Rube MCP (Composio). Always search tools first for current schemas."
requires:
  mcp: [rube]
---

# Dromo Automation via Rube MCP

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

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

1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `dromo`
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: "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](https://composio.dev)*

Overview

This skill automates Dromo tasks through Composio's Dromo toolkit using Rube MCP, providing a repeatable pattern for discovery, connection checks, and tool execution. It enforces searching available tools first so workflows use current schemas and avoids hardcoded tool slugs or arguments. The skill is implemented in Python and targets composable automation workflows for Dromo via Rube MCP.

How this skill works

The skill first calls RUBE_SEARCH_TOOLS to retrieve available tool slugs, input schemas, execution plans, and pagination details. It then verifies or establishes an active Dromo connection with RUBE_MANAGE_CONNECTIONS. Workflows run tools through RUBE_MULTI_EXECUTE_TOOL (or RUBE_REMOTE_WORKBENCH for bulk ops) using schema-compliant arguments and an explicit memory object. Session IDs are created or reused to scope workflows and handle pagination tokens to collect complete results.

When to use it

Automate repetitive Dromo operations that require reliable tool schema discovery
Integrate Dromo actions into larger composable workflows via Rube MCP
Run bulk or parallel Dromo tasks where tool schemas may change frequently
Build Python agents that must validate and execute tool calls dynamically
Orchestrate multi-step flows that depend on active Dromo connections

Best practices

Always call RUBE_SEARCH_TOOLS first; do not hardcode tool slugs or argument shapes
Verify connection status via RUBE_MANAGE_CONNECTIONS and complete any returned auth flows until ACTIVE
Pass an explicit memory object (even {}) to RUBE_MULTI_EXECUTE_TOOL calls
Reuse session_id for a single workflow; generate a new session for distinct workflows
Respect field names and types exactly as returned by the tool schema; follow pagination tokens until complete

Example use cases

Discover and run a Dromo content import tool after retrieving its current input schema
Automate batch updates across Dromo entities using RUBE_REMOTE_WORKBENCH with run_composio_tool()
Create a Python agent that checks connection, fetches tool schema, then executes a deploy workflow
Build an audit workflow that paginates through tool results to gather complete logs
Integrate a Dromo task into a multi-platform pipeline where RUBE_SEARCH_TOOLS ensures compatibility before execution

FAQ

What must I call before executing any Dromo tool?

Always call RUBE_SEARCH_TOOLS to get current tool slugs and input schemas; this prevents runtime errors from schema changes.

Do I need API keys to use Rube MCP?

No API keys are required; add https://rube.app/mcp as an MCP server in your client and use the provided Rube MCP actions.