kaleido-automation

Automate Kaleido platform operations through Rube MCP tool discovery and execution workflows.

74.2k|8.5k|Updated Oct 17, 2025
One-click install
npx skills add https://github.com/ComposioHQ/awesome-claude-skills --skill kaleido-automation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kaleido-automation
Source: https://github.com/ComposioHQ/awesome-claude-skills/tree/main/composio-skills/kaleido-automation
Command: npx skills add https://github.com/ComposioHQ/awesome-claude-skills --skill kaleido-automation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the complexity of manually navigating Kaleido platform interfaces by providing a standardized, agent-driven approach to executing tasks and managing connections.

Core Features & Use Cases

  • Dynamic Tool Discovery: Automatically fetches current schemas and tool definitions via Rube MCP to ensure compatibility.
  • Connection Management: Handles authentication and status verification for Kaleido toolkits within the Rube ecosystem.
  • Multi-Tool Execution: Supports complex workflows by chaining multiple tool calls and managing session memory.

Quick Start

Use the kaleido-automation skill to discover available tools and execute a specific task for your current session.

Frequently Asked Questions about kaleido-automation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I discover available Kaleido tools?

Call the RUBE_SEARCH_TOOLS function with a query related to your specific Kaleido task. This returns the current tool slugs, input schemas, and execution requirements needed for your workflow.

How do I verify my Kaleido connection status?

Use the RUBE_MANAGE_CONNECTIONS tool with the 'kaleido' toolkit parameter. This will return the current connection status and provide an authentication link if the connection is not active.

Can I reuse session IDs for multiple tasks?

Yes, you should reuse session IDs within a single workflow to maintain context. However, generate new session IDs for distinct, unrelated workflows to prevent state contamination.

Why must I call RUBE_SEARCH_TOOLS before executing?

Tool schemas and slugs on the Kaleido platform change frequently. Searching first ensures you are using the most current arguments and field requirements, preventing execution errors.

What should I do if a tool execution fails?

Verify that your connection status is ACTIVE via RUBE_MANAGE_CONNECTIONS and ensure your arguments strictly match the schema returned by the most recent RUBE_SEARCH_TOOLS call.