What is Kaleido automation via Rube MCP?

It automates Kaleido operations through Composio's Kaleido toolkit using Rube MCP and requires you to search tools first for current schemas.

How do I discover and execute a Kaleido tool?

Use RUBE_SEARCH_TOOLS to discover tool_slugs and input schemas, then ensure an active connection with RUBE_MANAGE_CONNECTIONS, and finally run RUBE_MULTI_EXECUTE_TOOL with the chosen tool_slug and proper arguments.

kaleido-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Kaleido Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/kaleido

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Kaleido operations using Composio's Kaleido toolkit through Rube MCP. This skill emphasizes discovering current tool schemas first and ensuring an active Kaleido connection before executing workflows, improving reliability and repeatability.

How This Skill Works

Start by discovering available Kaleido tools with RUBE_SEARCH_TOOLS to fetch slugs and input schemas. Then verify an ACTIVE Kaleido connection via RUBE_MANAGE_CONNECTIONS using the kaleido toolkit. Finally, execute the chosen tool with RUBE_MULTI_EXECUTE_TOOL, supplying exact schema fields, a memory payload, and reusing a session_id for continuity.

When to Use It

When you need to automate Kaleido operations end-to-end using Composio's toolkit
When tool schemas may change and you must fetch updated slugs before running workflows
When you must verify the Kaleido connection is ACTIVE before execution
When performing bulk operations with multiple Kaleido tools or workflows
When you want to reuse sessions across related Kaleido tasks to reduce setup time

Quick Start

Step 1: Discover Available Tools using RUBE_SEARCH_TOOLS with Kaleido use_case
Step 2: Check Connection with RUBE_MANAGE_CONNECTIONS for toolkit kaleido and ensure ACTIVE
Step 3: Execute Tools with RUBE_MULTI_EXECUTE_TOOL using the discovered tool_slug and memory, reusing a session_id

Best Practices

Always call RUBE_SEARCH_TOOLS before every Kaleido workflow to fetch current schemas
Check that RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools
Use exact field names and types from the search results
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty
Reuse session IDs within a workflow; generate new sessions for new workflows

Example Use Cases

Discover a Kaleido data ingestion tool, verify ACTIVE connection, and run the tool with proper arguments in a single session
Establish a Kaleido connection and sequentially execute multiple tools using a shared session via RUBE_MULTI_EXECUTE_TOOL
Bulk run a set of Kaleido tasks using RUBE_REMOTE_WORKBENCH to process a batch workload
Reuse a session ID across iterative Kaleido tasks to minimize startup overhead
When tool schemas change, re-discover with RUBE_SEARCH_TOOLS before executing to avoid schema mismatches

Frequently Asked Questions

Add this skill to your agents