What is Wachete automation via Rube MCP?

It automates Wachete tasks through Composio's Wachete toolkit using the Rube MCP framework.

Do I need to call RUBE_SEARCH_TOOLS before running tools?

Yes, you must fetch current tool schemas to avoid hardcoding tool slugs or arguments.

How do I ensure the Wachete connection is ready?

Check the status with RUBE_MANAGE_CONNECTIONS and require ACTIVE before executing any tools.

wachete-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Wachete Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/wachete

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Wachete operations through Composio's Wachete toolkit via Rube MCP. The workflow discovers available tools, validates the Wachete connection, and executes tool slugs with schema compliant arguments, always relying on current schemas fetched by RUBE_SEARCH_TOOLS.

How This Skill Works

Technically, you first fetch current tool schemas with RUBE_SEARCH_TOOLS, then confirm the Wachete connection via RUBE_MANAGE_CONNECTIONS, and finally execute the chosen tool with RUBE_MULTI_EXECUTE_TOOL using the discovered slug and its required arguments. Always include memory and a session_id to maintain context across steps.

When to Use It

You need to automate repetitive Wachete operations via Composio
You want to ensure tool schemas are current before execution
You are integrating Wachete with Rube MCP backed workflows
You must verify and manage the Wachete connection before running
You are performing batch or multi-tool workflows across targets

Quick Start

Step 1: Discover Available Tools RUBE_SEARCH_TOOLS queries: [{use_case: "your specific Wachete task"}] session: {id: "existing_session_id"}
Step 2: Check Connection RUBE_MANAGE_CONNECTIONS toolkits: ["wachete"] 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"

Best Practices

Always call RUBE_SEARCH_TOOLS before selecting a tool
Verify the Wachete connection is ACTIVE via RUBE_MANAGE_CONNECTIONS
Use exact field names and types from the tool schemas
Include memory in every RUBE_MULTI_EXECUTE_TOOL call
Reuse session IDs where appropriate and handle pagination tokens

Example Use Cases

Schedule daily Wachete page checks across multiple monitors
Automate a batch of Wachete operations after discovering tools
Build a reusable workflow that connects, discovers, and executes tools
Validate tool schema changes by re-discovering tools before running
Run multi-tool workflows with a single session for a project

Frequently Asked Questions

Add this skill to your agents