What is required to use emelia-automation?

Rube MCP must be connected, an active Emelia connection must be established, and you must always call RUBE_SEARCH_TOOLS first to fetch current tool schemas.

How do I find available Emelia tools?

Use RUBE_SEARCH_TOOLS with a use_case like Emelia operations to retrieve tool slugs, input schemas, and recommended execution plans.

How do I run an Emelia tool?

Ensure the Emelia connection is ACTIVE, then call RUBE_MULTI_EXECUTE_TOOL with the discovered tool_slug, the correct arguments from the schema, a memory object, and a session_id.

emelia-automation

Scanned

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

Files (1)

SKILL.md

2.8 KB

Emelia Automation via Rube MCP

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

Toolkit docs: 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.

Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds
Call RUBE_MANAGE_CONNECTIONS with toolkit emelia
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: "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

Source

git clone https://github.com/ComposioHQ/awesome-claude-skills/blob/master/composio-skills/emelia-automation/SKILL.mdView on GitHub

Overview

Automate Emelia operations through Composio's Emelia toolkit via Rube MCP. Prereqs: connect Rube MCP, ensure Emelia toolkit connection is ACTIVE, and always search for current tool schemas before running workflows.

How This Skill Works

This skill automates Emelia workflows by first discovering available tools with RUBE_SEARCH_TOOLS, then validating the Emelia connection with RUBE_MANAGE_CONNECTIONS, and finally executing the chosen tool via RUBE_MULTI_EXECUTE_TOOL using the required schema fields and a memory payload. It emphasizes using current tool schemas to avoid hardcoding slugs.

When to Use It

Automating a specific Emelia operation after discovering the appropriate tool from current schemas
Verifying that RUBE MCP connection to Emelia is ACTIVE before starting any workflow
Fetching up-to-date input schemas for Emelia tools to avoid outdated arguments
Executing a discovered Emelia tool with a session_id and memory payload
Performing bulk or chained Emelia actions through RUBE_REMOTE_WORKBENCH or multiple tool executions

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server in your client and verify RUBE_SEARCH_TOOLS responds
Step 2: Connect to Emelia with RUBE_MANAGE_CONNECTIONS using toolkits: ["emelia"] and complete any required auth; ensure the status is ACTIVE
Step 3: Discover tools with RUBE_SEARCH_TOOLS for Emelia operations, then execute a tool with RUBE_MULTI_EXECUTE_TOOL using the returned slug and input schema

Best Practices

Always call RUBE_SEARCH_TOOLS first to fetch current tool schemas
Check that RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools
Use exact field names and types from the tool schema when forming arguments
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty
Reuse session IDs for related workflows and avoid hardcoding tool slugs

Example Use Cases

Automate a weekly Emelia report by discovering the tool slug with RUBE_SEARCH_TOOLS and executing it via RUBE_MULTI_EXECUTE_TOOL
Establish and verify an ACTIVE Emelia connection with RUBE_MANAGE_CONNECTIONS before running a sequence
Run a discovered Emelia tool with the exact inputs returned by the schema and a memory payload
Reuse a session ID across multiple Emelia tasks within a workflow
Perform bulk Emelia actions using RUBE_REMOTE_WORKBENCH to run multiple tools

Frequently Asked Questions

Add this skill to your agents