Kaleido Automation

What This Skill Does

• This skill automates Kaleido operations using Composio's Kaleido toolkit through Rube MCP.
• It is designed for users who need to streamline their Kaleido workflows.
• The skill ensures proper setup, tool discovery, and execution while avoiding common pitfalls.

When to Use

• Automate Kaleido tasks.
• Manage Kaleido API connections.
• Discover available Kaleido tools.
• Check Kaleido connection status.
• Execute Kaleido tools with schema compliance.
• Generate Kaleido reports.

Key Features

• Automates Kaleido operations via Rube MCP.
• Uses Composio's Kaleido toolkit.
• Requires active Kaleido connection.
• Discovers tools using RUBE_SEARCH_TOOLS.
• Checks connection status with RUBE_MANAGE_CONNECTIONS.
• Executes tools with RUBE_MULTI_EXECUTE_TOOL.

Manual Installation

• Manual installation.
• View Full Skill Content.
• The complete markdown content that gets installed.
• 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

Powered by Composio. 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

Powered by Composio