Do I always need to call RUBE_SEARCH_TOOLS before executing an Imgix task?

Yes. RUBE_SEARCH_TOOLS fetches current tool schemas and is required to avoid hardcoding slugs or arguments.

How do I verify Imgix is ready to use?

Ensure RUBE_MANAGE_CONNECTIONS returns ACTIVE for the Imgix toolkit before executing any tools.

What about memory when executing tools?

Always include a memory object in RUBE_MULTI_EXECUTE_TOOL calls, even if empty, to preserve state and context.

imgix-automation

Scanned

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

Files (1)

SKILL.md

2.8 KB

Imgix Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/imgix

Prerequisites

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

Step 2: Check Connection

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

Overview

Automates Imgix operations by orchestrating Composio's Imgix toolkit through Rube MCP. It requires discovering current tool schemas with RUBE_SEARCH_TOOLS before any execution and validating an active Imgix connection with RUBE_MANAGE_CONNECTIONS. This enables repeatable, schema-aware workflows for Imgix tasks.

How This Skill Works

First, it uses RUBE_SEARCH_TOOLS to fetch current Imgix tool schemas. Next, it validates the Imgix connection with RUBE_MANAGE_CONNECTIONS and ensures the status is ACTIVE. Finally, it runs the discovered tool with RUBE_MULTI_EXECUTE_TOOL, supplying memory and a session_id.

When to Use It

You need up-to-date Imgix tool schemas before starting any workflow.
You're integrating a new Imgix task and must confirm available tool options.
You must verify the Imgix connection is ACTIVE before execution.
You want to run multiple Imgix tools in a single session or in bulk.
You need to fetch full tool schemas or compare against schemaRef before execution.

Quick Start

Step 1: Add the Rube MCP endpoint (https://rube.app/mcp) to your MCP servers and confirm RUBE_SEARCH_TOOLS responds.
Step 2: Call RUBE_MANAGE_CONNECTIONS with toolkits: ["imgix"] and verify the connection status is ACTIVE.
Step 3: Use RUBE_SEARCH_TOOLS to discover tools, then run a chosen tool with RUBE_MULTI_EXECUTE_TOOL, including memory: {} and a session_id.

Best Practices

Always call RUBE_SEARCH_TOOLS first to fetch current tool schemas.
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools.
Use exact field names and types from search results; do not hardcode slugs.
Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({})
Reuse session IDs within a workflow and fetch new ones for new workflows; watch for pagination tokens.

Example Use Cases

Discover Imgix tools for a resize operation, then execute with width/height parameters.
Connect to the Imgix toolkit and verify ACTIVE before starting a batch optimization.
Execute a sequence of Imgix tools in one session using RUBE_MULTI_EXECUTE_TOOL with memory.
Perform bulk Imgix tasks via RUBE_REMOTE_WORKBENCH and run_composio_tool().
Fetch full tool schemas with RUBE_GET_TOOL_SCHEMAS to inspect schemaRef and plan changes.

Frequently Asked Questions

Add this skill to your agents