What are the prerequisites to use exist-automation?

Rube MCP must be connected, RUBE_SEARCH_TOOLS must respond, and you must have an active Exist connection via RUBE_MANAGE_CONNECTIONS with the exist toolkit. Always start by searching tools.

Do I need to hardcode tool slugs?

No. Always fetch current tool schemas with RUBE_SEARCH_TOOLS before executing any tool to avoid stale slugs or mismatched arguments.

How do I actually run an Exist tool after discovery?

After confirming the connection, call RUBE_MULTI_EXECUTE_TOOL with the discovered tool_slug and its required arguments, include a memory payload, and attach the session_id from the discovery step.

exist-automation

Scanned

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

Files (1)

SKILL.md

2.8 KB

Exist Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/exist

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Exist operations using the Composio Exist toolkit through the Rube MCP. It ensures you always fetch current tool schemas before running workflows. Follow prerequisites and the core workflow pattern to reliably discover, connect, and execute Exist tools.

How This Skill Works

Verify the RUBE_SEARCH_TOOLS endpoint is responsive, then establish a connection to the Exist toolkit with RUBE_MANAGE_CONNECTIONS. Discover available tools using RUBE_SEARCH_TOOLS, then execute the chosen tool with RUBE_MULTI_EXECUTE_TOOL, including a memory payload and the session_id. This approach emphasizes dynamic schema discovery, active connections, and session reuse across steps.

When to Use It

Need to perform Exist operations and require up to date tool schemas before execution
Want to reuse a session across a sequence of Exist tasks
Wiring automated Exist workflows into a larger Composio pipeline
Must verify the Exist connection is ACTIVE before running tools
Avoid hardcoding tool slugs by discovering them at runtime

Quick Start

Step 1: Add the Rube MCP endpoint (https://rube.app/mcp) as an MCP server in your client configuration
Step 2: Verify RUBE_SEARCH_TOOLS responds and discover Exist tools for your task
Step 3: Execute a discovered tool with RUBE_MULTI_EXECUTE_TOOL, providing memory and a session_id

Best Practices

Always search first to get current tool schemas
Verify that RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools
Use exact field names and types from tool schemas
Include memory in every RUBE_MULTI_EXECUTE_TOOL call, even if empty
Reuse session IDs within a workflow and generate a new one only for new workflows

Example Use Cases

Discover Exist tools with RUBE_SEARCH_TOOLS and execute a create operation using RUBE_MULTI_EXECUTE_TOOL
Check the connection status with RUBE_MANAGE_CONNECTIONS and run an update task on an Exist resource
Perform bulk Exist operations via RUBE_REMOTE_WORKBENCH using run_composio_tool
Fetch paginated results from Exist by handling pagination tokens returned by RUBE_SEARCH_TOOLS
Reuse an existing session to execute a dependent sequence of Exist tasks

Frequently Asked Questions

Add this skill to your agents