How do I ensure current tool schemas?

Always call RUBE_SEARCH_TOOLS before executing anything to fetch the latest tool slugs and input schemas.

What if the Updown IO connection isn’t ACTIVE?

Follow the auth link returned by RUBE_MANAGE_CONNECTIONS to complete setup and verify that the status shows ACTIVE before proceeding.

Is memory required in tool executions?

Yes. Include the memory parameter in RUBE_MULTI_EXECUTE_TOOL calls, even if it is an empty object {}.

updown-io-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Updown IO Automation via Rube MCP

Automate Updown IO operations through Composio's Updown IO toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/updown_io

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Updown IO operations using Composio's Updown IO toolkit through Rube MCP. This skill emphasizes discovering current tool schemas with RUBE_SEARCH_TOOLS, verifying an active Updown IO connection, and executing chosen tools with properly structured arguments.

How This Skill Works

Start by discovering available Updown IO tools with RUBE_SEARCH_TOOLS to obtain slugs, input schemas, and execution plans. Then check the Updown IO connection with RUBE_MANAGE_CONNECTIONS and confirm the status is ACTIVE. Finally, run the selected tool via RUBE_MULTI_EXECUTE_TOOL, supplying exact schema fields and including a memory object (even if empty) along with the session_id from your workflow.

When to Use It

When you need to automate Updown IO tasks and require the latest tool schemas for accuracy
When establishing or validating a Rube MCP connection to Updown IO and ensuring ACTIVE status
When executing a multi-step Updown IO workflow using discovered tool slugs
When integrating Updown IO operations into scheduled tasks or pipelines and reusing session IDs
When performing bulk operations or audits using bulk tooling workflows

Quick Start

Step 1: Ensure Rube MCP is connected and that RUBE_SEARCH_TOOLS responds to verify tool schemas
Step 2: Use RUBE_SEARCH_TOOLS to discover available Updown IO tools and select a TOOL_SLUG with its required arguments
Step 3: Execute the chosen tool with RUBE_MULTI_EXECUTE_TOOL, including memory and a valid session_id after confirming the connection is ACTIVE

Best Practices

Always call RUBE_SEARCH_TOOLS first to fetch current tool schemas and slugs
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before running any tools
Use exact field names and types from the discovered input schemas
Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty
Reuse session IDs within a workflow and fetch new ones only for separate workflows

Example Use Cases

Auto-toggle a resource state in Updown IO by discovering the appropriate tool and executing it with the correct arguments
Sync Updown IO status to a monitoring dashboard by running a read/status tool and logging the results
Batch update multiple Updown IO resources in a single session using discovered tool slugs
Schedule a recurring workflow to check connectivity, discover tools, and perform a routine operation
Bulk apply configuration updates across several Updown IO tools using bulk execution workflows

Frequently Asked Questions

Add this skill to your agents