Do I need API keys to use imgbb-automation?

No. You set up the Rube MCP endpoint, add the MCP server, and ensure the Imgbb connection is ACTIVE; API keys are not required for the workflow described.

How do I keep tool schemas current?

Always run RUBE_SEARCH_TOOLS before execution. It returns tool slugs, input schemas, recommended execution plans, and known pitfalls.

What about memory and session handling?

Include a memory object in every RUBE_MULTI_EXECUTE_TOOL call (even if empty) and reuse session IDs within a workflow; generate new IDs for new workflows.

imgbb-automation

Scanned

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

Files (1)

SKILL.md

2.8 KB

Imgbb Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/imgbb

Prerequisites

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

Step 2: Check Connection

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

Overview

Automates Imgbb operations using Composio's Rube MCP toolkit. It emphasizes discovering current tool schemas with RUBE_SEARCH_TOOLS, establishing an ACTIVE Imgbb connection, and executing tools via RUBE_MULTI_EXECUTE_TOOL. This approach avoids hardcoding slugs and adapts to schema updates.

How This Skill Works

First, fetch available Imgbb tool slugs and input schemas using RUBE_SEARCH_TOOLS. Then verify the Imgbb connection is ACTIVE with RUBE_MANAGE_CONNECTIONS. Finally, execute the chosen tool with RUBE_MULTI_EXECUTE_TOOL, providing the discovered arguments and a memory object, and reuse sessions when appropriate.

When to Use It

Automating a single Imgbb task (upload, delete, or edit) by discovering the correct tool slug and running it.
Keeping tool schemas up-to-date by always running RUBE_SEARCH_TOOLS before execution.
Coordinating multiple Imgbb tasks in a single workflow while reusing a session_id.
Ensuring the Imgbb connection is ACTIVE before executing any tool.
Performing bulk Imgbb operations via RUBE_REMOTE_WORKBENCH run_composio_tool.

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed.
Step 2: Verify RUBE_SEARCH_TOOLS responds; call RUBE_MANAGE_CONNECTIONS with toolkit 'imgbb' and ensure ACTIVE status.
Step 3: Discover tools for your Imgbb task using RUBE_SEARCH_TOOLS, then execute the chosen tool via RUBE_MULTI_EXECUTE_TOOL with memory: {} and a session_id.

Best Practices

Always search first; tool schemas change and slugs can be updated. Do not hardcode tool slugs or arguments.
Verify the Imgbb connection shows ACTIVE with RUBE_MANAGE_CONNECTIONS before executing tools.
Follow exact field names and types from the search results to ensure schema compliance.
Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty (memory: {}).
Reuse session IDs within a workflow and generate new IDs for new workflows; watch for pagination tokens in responses.

Example Use Cases

Example 1: Upload a single image by discovering the appropriate Imgbb tool slug, verifying the connection, and executing with the image path and memory object.
Example 2: Update image metadata after discovering the relevant tool and passing metadata fields as arguments.
Example 3: Schedule recurring uploads within a single session to maintain context and reduce setup overhead.
Example 4: Execute multiple Imgbb operations in bulk using RUBE_REMOTE_WORKBENCH with run_composio_tool for efficiency.
Example 5: When tool schemas change, re-run RUBE_SEARCH_TOOLS and adjust the arguments to match the new schema.

Frequently Asked Questions

Add this skill to your agents