$ ~/registry/skill/composiohq-composio-skills-exist-automation

SKILL

exist-automation

Automate Exist tasks through Rube MCP using current discovered tool schemas.

Stars

★ 73,665

Source

GitHub

Updated

2026-08-28

// securityLow risk

Prompt only, no code
Open source
Community-trusted· 73.7k

Running security audit…

Credentials
Network egress
Code execution
Data access
Supply chain

// install

Copy the install command and let the AI configure it · recommended for beginners

Please install the "exist-automation" skill from askskill:
1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/exist-automation/SKILL.md
2. Save it as ~/.claude/skills/exist-automation/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// use cases

Discover tools dynamically before automation

Before calling any Exist capability, a developer can use RUBE_SEARCH_TOOLS to retrieve the current tools and parameter schemas, avoiding failures caused by hardcoded assumptions. This fits automation workflows that must adapt to changing schemas.

Connect and verify the Exist integration

During first-time setup or after a connection issue, users can check whether the exist toolkit is ACTIVE with RUBE_MANAGE_CONNECTIONS. If it is not active, they can complete authorization through the returned auth link.

Run an Exist workflow with a shared session

Reusing a session ID across a workflow helps keep discovery, connection checks, and execution aligned. During execution, arguments must strictly follow the discovered schema and include the memory field.

// docs

AI summary

The document explains how to automate Exist operations through Composio's Exist toolkit via Rube MCP. It covers prerequisites, connection and authorization steps, tool discovery, and the recommended workflow: first use `RUBE_SEARCH_TOOLS` to get current schemas, then verify the connection with `RUBE_MANAGE_CONNECTIONS`, and finally execute with `RUBE_MULTI_EXECUTE_TOOL`. It also highlights session reuse, including the `memory` field, and handling pagination.

Show full docs ▾

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

// FAQ

What does this skill do?

It automates Exist-related operations through Rube MCP using Composio's Exist toolkit. The docs specifically stress searching for tools first and executing against the latest schema.

What prerequisites are required before use?

You need Rube MCP connected and `RUBE_SEARCH_TOOLS` available. You also need an active connection for the `exist` toolkit through `RUBE_MANAGE_CONNECTIONS`.

Why must I search tools first?

Because tool schemas may change, and the docs explicitly say not to hardcode tool slugs or arguments. Searching first gives you the current input structure, execution guidance, and known pitfalls.

Automate Livesession workflows via Rube MCP using current tool schemas first.

ComposioGet→

$ loading_