Do I need to install anything to use this skill?

Yes. Configure an MCP at https://rube.app/mcp and ensure the imagekit_io toolkit is connected; RUBE_SEARCH_TOOLS must respond before running tools.

How do I ensure tool schemas are current?

Always call RUBE_SEARCH_TOOLS to fetch up-to-date schemas before executing any tool; never hardcode slugs or arguments.

What about the memory parameter in executions?

Include memory in each RUBE_MULTI_EXECUTE_TOOL call, even if it is an empty object.

imagekit-io-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Imagekit IO Automation via Rube MCP

Automate Imagekit IO operations through Composio's Imagekit IO toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/imagekit_io

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["imagekit_io"]
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 Imagekit IO-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `imagekit_io`
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/imagekit-io-automation/SKILL.md

View on GitHub

Overview

Automate Imagekit IO operations through Composio's Imagekit IO toolkit via Rube MCP. It orchestrates tool discovery, connection management, and execution using current schemas fetched with RUBE_SEARCH_TOOLS.

How This Skill Works

First, discover available tools for Imagekit IO using RUBE_SEARCH_TOOLS to obtain current input schemas. Then verify the imagekit_io connection with RUBE_MANAGE_CONNECTIONS and ensure it is ACTIVE. Finally, run the tool via RUBE_MULTI_EXECUTE_TOOL, including memory and the exact schema fields from the search results.

When to Use It

When you need to perform a specific Imagekit IO operation and want up-to-date tool schemas.
When you must verify or refresh the imagekit_io connection before workflows.
When orchestrating a multi-step workflow that relies on session IDs.
When you need to handle paginated responses from tool discovery.
When performing a bulk or batch operation via RUBE_REMOTE_WORKBENCH with run_composio_tool.

Quick Start

Step 1: Ensure Rube MCP is configured by adding the MCP server at https://rube.app/mcp and verify RUBE_SEARCH_TOOLS is available.
Step 2: Discover tools with RUBE_SEARCH_TOOLS for Imagekit IO operations to obtain current input schemas.
Step 3: Manage the Imagekit IO connection with RUBE_MANAGE_CONNECTIONS, then execute a tool with RUBE_MULTI_EXECUTE_TOOL using memory and the exact schema fields.

Best Practices

Always call RUBE_SEARCH_TOOLS first; don't hardcode tool slugs or args.
Verify the connection is ACTIVE via RUBE_MANAGE_CONNECTIONS before execution.
Use exact field names and types from the search results for tool calls.
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty.
Reuse session IDs within a workflow; generate new session IDs for new workflows.

Example Use Cases

Discover available Imagekit IO operations and execute a resize_image tool using the current schema.
Connect to the Imagekit IO toolkit with RUBE_MANAGE_CONNECTIONS and complete authentication before running workflows.
Run a multi-step Imagekit IO workflow that shares a session_id and memory across tools.
Handle pagination while listing tools from RUBE_SEARCH_TOOLS and continue until all results are fetched.
Perform a bulk image processing batch via RUBE_REMOTE_WORKBENCH using run_composio_tool.

Frequently Asked Questions

Add this skill to your agents