What is the first action to perform?

Add the Rube MCP endpoint, then verify RUBE_SEARCH_TOOLS is available.

Why must I call RUBE_SEARCH_TOOLS before selecting a tool?

Tool schemas change; this ensures you use current slugs and input fields.

How do I ensure the workflow runs safely?

Check that the Re Amaze connection is ACTIVE with RUBE_MANAGE_CONNECTIONS before executing, and include memory in calls.

re-amaze-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Re Amaze Automation via Rube MCP

Automate Re Amaze operations through Composio's Re Amaze toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/re_amaze

Prerequisites

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

Step 2: Check Connection

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

Overview

This skill automates Re Amaze operations by interfacing with Composio's Re Amaze toolkit via Rube MCP. It emphasizes discovering current tool schemas with RUBE_SEARCH_TOOLS before execution and requires an ACTIVE Re Amaze connection, ensuring workflows run against up-to-date inputs and slugs.

How This Skill Works

1) Discover available tools using RUBE_SEARCH_TOOLS with a Re Amaze use_case to fetch current slugs and schemas. 2) Verify the connection is ACTIVE via RUBE_MANAGE_CONNECTIONS for the re_amaze toolkit. 3) Execute the chosen tool with RUBE_MULTI_EXECUTE_TOOL, including memory and session_id, based on the live schemas.

When to Use It

When setting up a new Re Amaze automation and you need current tool schemas before proceeding
When executing a workflow that relies on up-to-date tool slugs and input schemas
When validating or reusing an existing session across multiple Re Amaze tasks
When performing batch or bulk operations with RUBE_MULTI_EXECUTE_TOOL
When handling dynamic tool outputs and potential pagination in tool discovery

Quick Start

Step 1: Add the MCP endpoint (https://rube.app/mcp) and verify RUBE_SEARCH_TOOLS
Step 2: Establish and confirm an ACTIVE re_amaze connection with RUBE_MANAGE_CONNECTIONS
Step 3: Discover tools, then execute a tool with RUBE_MULTI_EXECUTE_TOOL using the live schema

Best Practices

Always run RUBE_SEARCH_TOOLS first to fetch current schemas
Check that RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty
Reuse session_id within a workflow to maintain continuity
Avoid hardcoding tool slugs; rely on live results from RUBE_SEARCH_TOOLS and RUBE_GET_TOOL_SCHEMAS

Example Use Cases

Automating a repetitive Re Amaze task by discovering tools, connecting, then executing
Running several Re Amaze operations in a single session with dynamic tool slugs
Updating an existing automation to always reference current schemas before run
Diagnosing a failure by inspecting RUBE_SEARCH_TOOLS outputs and connection status
Batch processing multiple Re Amaze tasks via RUBE_MULTI_EXECUTE_TOOL

Frequently Asked Questions

Add this skill to your agents