What is required to start automating Piloterr with Rube MCP?

Connect Rube MCP, ensure RUBE_SEARCH_TOOLS responds, and connect the Piloterr toolkit via RUBE_MANAGE_CONNECTIONS. No API keys are needed—just add the MCP endpoint.

Why must I call RUBE_SEARCH_TOOLS first?

Tool schemas can change frequently; RUBE_SEARCH_TOOLS fetches current slugs and input schemas, preventing hardcoded errors.

What should I include in memory and session during execution?

Include a memory object in RUBE_MULTI_EXECUTE_TOOL and reuse a session_id across related tasks to maintain context; follow the core workflow steps and use the exact schemas from the search results.

piloterr-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Piloterr Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/piloterr

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Piloterr operations through Composio's Piloterr toolkit via Rube MCP. This skill enables discovering current tool schemas, validating active connections, and executing Piloterr tasks end-to-end from a single workflow.

How This Skill Works

Connect Rube MCP to Piloterr and use RUBE_SEARCH_TOOLS to fetch current tool slugs and input schemas. Then manage the Piloterr connection with RUBE_MANAGE_CONNECTIONS and ensure the status is ACTIVE. Finally, execute the chosen tool via RUBE_MULTI_EXECUTE_TOOL, supplying the discovered slug, memory, and session_id to maintain state across steps.

When to Use It

When you need to automate Piloterr workflows end-to-end with up-to-date tool schemas.
When tool slugs or input schemas change and you must fetch fresh data before execution.
When establishing or verifying a Piloterr connection via RUBE_MANAGE_CONNECTIONS.
When executing multiple Piloterr tools in bulk using RUBE_MULTI_EXECUTE_TOOL.
When reusing a session_id across related Piloterr tasks to simplify state management.

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server and verify RUBE_SEARCH_TOOLS responds.
Step 2: Call RUBE_MANAGE_CONNECTIONS with toolkit 'piloterr' and complete any auth if prompted; ensure ACTIVE status.
Step 3: Use RUBE_MULTI_EXECUTE_TOOL with a discovered TOOL_SLUG and memory object, supplying the session_id from your workflow.

Best Practices

Always call RUBE_SEARCH_TOOLS before execution to get current slugs and schemas.
Check that RUBE_MANAGE_CONNECTIONS reports ACTIVE before running tools.
Copy exact field names and types from the search results; avoid hardcoding.
Include memory in every RUBE_MULTI_EXECUTE_TOOL call, even if empty.
Reuse session IDs for related workflows and monitor pagination tokens if present.

Example Use Cases

Example 1: Discover Piloterr operations tools using RUBE_SEARCH_TOOLS with use_case: 'Piloterr operations' to identify available tasks and their input schemas.
Example 2: Establish a Piloterr connection with RUBE_MANAGE_CONNECTIONS (toolkit: 'piloterr') and confirm the status is ACTIVE before any run.
Example 3: Execute a discovered Piloterr tool slug via RUBE_MULTI_EXECUTE_TOOL with the required arguments and memory: {}.
Example 4: Run multiple Piloterr actions in a single flow using RUBE_REMOTE_WORKBENCH and run_composio_tool() for bulk execution.
Example 5: Retrieve the full tool schemas with RUBE_GET_TOOL_SCHEMAS to review schemaRef and ensure compatibility before automation.

Frequently Asked Questions

Add this skill to your agents