What is required to use unione-automation?

Rube MCP must be connected and an active Unione connection established; always call RUBE_SEARCH_TOOLS before executing.

Why must I search tools first?

Tool schemas change; you must fetch current tool slugs and input schemas before running any tool.

How do I execute a discovered tool?

Use RUBE_MULTI_EXECUTE_TOOL with the discovered tool_slug, supply schema-compliant arguments, include memory: {} and the current session_id from discovery.

unione-automation

Scanned

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

Files (1)

SKILL.md

2.8 KB

Unione Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/unione

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Unione operations through Composio's Unione toolkit using Rube MCP. The workflow emphasizes discovering available tool schemas with RUBE_SEARCH_TOOLS before execution, ensuring inputs are current. It includes establishing an active Unione connection and executing discovered tools in sequence.

How This Skill Works

Technically, you first run RUBE_SEARCH_TOOLS to obtain tool slugs and input schemas for your Unione task. Then you verify the Unione connection via RUBE_MANAGE_CONNECTIONS, and once ACTIVE, execute the chosen tool with RUBE_MULTI_EXECUTE_TOOL, supplying the discovered slug, proper arguments, a memory object, and a session_id from prior steps.

When to Use It

Automating recurring Unione tasks while keeping tool schemas current
Avoiding hardcoded tool slugs by discovering tools at runtime
Ensuring the Unione connection is ACTIVE before workflow execution
Orchestrating multiple Unione tools in a single workflow (multi-step)
Handling dynamic schemas or pagination by re-discovering tools as needed

Quick Start

Step 1: Configure Rube MCP by adding the MCP endpoint (https://rube.app/mcp) and verify RUBE_SEARCH_TOOLS responds
Step 2: Establish an Unione connection with RUBE_MANAGE_CONNECTIONS and ensure the status is ACTIVE
Step 3: Discover tools with RUBE_SEARCH_TOOLS for your use case, then run the chosen tool with RUBE_MULTI_EXECUTE_TOOL using the discovered slug, proper arguments, memory, and a session_id

Best Practices

Always call RUBE_SEARCH_TOOLS before executing any workflow
Check that RUBE_MANAGE_CONNECTIONS reports ACTIVE before running tools
Use exact field names and types from the search results; avoid hardcoding
Include memory in every RUBE_MULTI_EXECUTE_TOOL call, even if empty
Reuse session IDs within a workflow and manage new sessions when starting new tasks

Example Use Cases

Automate a daily Unione data sync by discovering tools, ensuring an ACTIVE connection, and executing the sync tool with a shared session
Run a multi-step Unione operation in a single session by discovering required tools and then executing them in sequence
Update automation after a tool schema change by re-running discovery to fetch new slugs and inputs before execution
Execute bulk Unione tasks via RUBE_REMOTE_WORKBENCH using run_composio_tool() for batch processing
Recover from an outage by rechecking ACTIVE status and resuming workflow with the same session_id to reuse context

Frequently Asked Questions

Add this skill to your agents