Skip to main content
NEW · APP STORE Now on iOS · macOS · iPad Android & Windows soon GET IT
Prompts Emelia Automation via Rube MCP

agent tool_use skill risk: medium

Emelia Automation via Rube MCP

Provides instructions for automating Emelia operations through Composio's Emelia toolkit via Rube MCP, covering prerequisites, setup steps, tool discovery with RUBE_SEARCH_TOOLS, c…

  • External action: high

SKILL 1 file

SKILL.md
---
name: emelia-automation
description: "Automate Emelia tasks via Rube MCP (Composio). Always search tools first for current schemas."
---
# Emelia Automation via Rube MCP

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

**Toolkit docs**: [composio.dev/toolkits/emelia](https://composio.dev/toolkits/emelia)

## Prerequisites

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

### Step 2: Check Connection

```
RUBE_MANAGE_CONNECTIONS
toolkits: ["emelia"]
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 Emelia-specific use case |
| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `emelia` |
| 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)*

REQUIRED CONTEXT

  • Rube MCP connection
  • Emelia toolkit connection via RUBE_MANAGE_CONNECTIONS

TOOLS REQUIRED

  • RUBE_SEARCH_TOOLS
  • RUBE_MANAGE_CONNECTIONS
  • RUBE_MULTI_EXECUTE_TOOL

ROLES & RULES

  1. Always search tools first for current schemas
  2. Always call RUBE_SEARCH_TOOLS first to get current tool schemas
  3. Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds
  4. Call RUBE_MANAGE_CONNECTIONS with toolkit emelia
  5. Confirm connection status shows ACTIVE before running any workflows
  6. Always discover available tools before executing workflows
  7. Always search first
  8. Check connection
  9. Use exact field names and types from the search results
  10. Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty
  11. Reuse session IDs within a workflow
  12. Generate new ones for new workflows
  13. Check responses for pagination tokens and continue fetching until complete

EXPECTED OUTPUT

Format
markdown
Constraints
  • always call RUBE_SEARCH_TOOLS first
  • verify ACTIVE connection before execution
  • use exact schemas from search results

SUCCESS CRITERIA

  • Always search first for current schemas
  • Verify active Emelia connection before executing tools
  • Use schema-compliant arguments from search results
  • Include memory parameter on every MULTI_EXECUTE_TOOL call

FAILURE MODES

  • Hardcoding tool slugs or arguments without calling RUBE_SEARCH_TOOLS
  • Executing tools before connection status is ACTIVE
  • Omitting the memory parameter in MULTI_EXECUTE_TOOL
  • Not reusing session IDs within a workflow

EXAMPLES

Includes multiple example RUBE_* tool calls (SEARCH_TOOLS, MANAGE_CONNECTIONS, MULTI_EXECUTE_TOOL) with sample arguments and a quick-reference table.

CAVEATS

Dependencies
  • Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
  • Active Emelia connection via RUBE_MANAGE_CONNECTIONS
Missing context
  • User's specific Emelia task or use case
Ambiguities
  • Does not specify desired output length or format for workflow results.

QUALITY

OVERALL
0.81
CLARITY
0.82
SPECIFICITY
0.78
REUSABILITY
0.85
COMPLETENESS
0.80

IMPROVEMENT SUGGESTIONS

  • Add a concrete end-to-end example with sample tool slugs and arguments.

USAGE

Copy the prompt above and paste it into your AI of choice — Claude, ChatGPT, Gemini, or anywhere else you're working. Replace any placeholder sections with your own context, then ask for the output.

MORE FOR AGENT