What is icypeas-automation?

A Composio-driven pattern to automate Icypeas tasks via Rube MCP, using live tool schemas discovered at runtime.

Do I need keys or credentials?

No API keys are required for the MCP endpoint; you connect through RUBE_SEARCH_TOOLS and RUBE_MANAGE_CONNECTIONS.

What if tool schemas change?

Always call RUBE_SEARCH_TOOLS before executing; hardcoding slugs or arguments is brittle.

icypeas-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Icypeas Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/icypeas

Prerequisites

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

Step 2: Check Connection

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

Overview

Icypeas automation via Composio's Icypeas toolkit lets you run Icypeas operations through Rube MCP. It emphasizes always searching for up-to-date tool schemas before execution to avoid mismatches and ensure workflows stay in sync with live capabilities.

How This Skill Works

The workflow is: discover available Icypeas tools with RUBE_SEARCH_TOOLS, verify and manage the Icypeas connection with RUBE_MANAGE_CONNECTIONS, then execute the chosen tools using RUBE_MULTI_EXECUTE_TOOL (including a memory object). For full schema visibility, you can also fetch schemas with RUBE_GET_TOOL_SCHEMAS. Always ensure the connection is ACTIVE and use the exact field names from the discovered schemas.

When to Use It

When you need to automate Icypeas tasks with the latest tool schemas
When starting a new Icypeas workflow and tooling might have changed since last run
When you must verify a live Icypeas connection before execution
When executing discovered Icypeas tools that require precise input field names
When performing bulk Icypeas operations or reviewing full tool schemas

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server in your client configuration (no API keys required).
Step 2: Run RUBE_SEARCH_TOOLS to fetch current Icypeas tool schemas and then run RUBE_MANAGE_CONNECTIONS with toolkit icypeas to activate the connection.
Step 3: Execute a tool with RUBE_MULTI_EXECUTE_TOOL using a discovered tool_slug and memory: {} in a connected session.

Best Practices

Always run RUBE_SEARCH_TOOLS before executing any Icypeas tool to fetch current schemas
Confirm RUBE_MANAGE_CONNECTIONS shows ACTIVE before running workflows
Use exact field names and types from the discovered tool schemas
Include a non-null memory object in RUBE_MULTI_EXECUTE_TOOL calls (even if empty)
Reuse session IDs within a workflow and generate new IDs for separate runs

Example Use Cases

Discover available Icypeas tools with use_case 'Icypeas operations', connect to icypeas, then execute a tool via RUBE_MULTI_EXECUTE_TOOL
Sequential Icypeas automation in a single session: search, connect, and run multiple tools using discovered schemas
Handle pagination by checking for next tokens in RUBE_SEARCH_TOOLS responses and continuing
Perform bulk operations using RUBE_REMOTE_WORKBENCH and run_composio_tool for Icypeas tasks
Fetch full tool schemas with RUBE_GET_TOOL_SCHEMAS to validate inputs before execution

Frequently Asked Questions

Add this skill to your agents