What is borneo-automation?

A workflow pattern to automate Borneo operations through Composio's Rube MCP toolkit, with emphasis on live tool discovery and reliable execution.

Why should I always search for current schemas before running?

Tool schemas can change, so hardcoding slugs and arguments leads to failures. RUBE_SEARCH_TOOLS returns slugs, input schemas, recommended plans, and pitfalls to guide execution.

Which commands are used to discover, connect, and execute?

Discovery: RUBE_SEARCH_TOOLS; Connection: RUBE_MANAGE_CONNECTIONS; Execution: RUBE_MULTI_EXECUTE_TOOL (with memory and session_id).

borneo-automation

Scanned

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

Files (1)

SKILL.md

2.8 KB

Borneo Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/borneo

Prerequisites

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

Step 2: Check Connection

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

Overview

borneo-automation enables automating Borneo operations through Composio's Rube MCP toolkit. It emphasizes discovering current tool schemas first to avoid hardcoding slugs and arguments, ensuring reliable workflows through discovery, connection management, and execution steps.

How This Skill Works

The workflow begins by discovering available Borneo tools with RUBE_SEARCH_TOOLS, then verifies and manages the borneo connection using RUBE_MANAGE_CONNECTIONS, and finally executes the chosen tools via RUBE_MULTI_EXECUTE_TOOL with a memory payload and a session ID.

When to Use It

When you need to automate Borneo operations and want tool choices to adapt to current schemas.
When tool schemas may change and you must avoid hardcoding slugs or arguments.
When you need to ensure an ACTIVE connection before running Borneo workflows.
When you want to orchestrate multiple tools in a single run using RUBE_MULTI_EXECUTE_TOOL.
When performing bulk or batch Borneo tasks via RUBE_REMOTE_WORKBENCH.

Quick Start

Step 1: Add the Rube MCP endpoint and verify availability with RUBE_SEARCH_TOOLS.
Step 2: Manage the borneo connection using RUBE_MANAGE_CONNECTIONS and complete auth if prompted.
Step 3: Discover tools with RUBE_SEARCH_TOOLS and execute a chosen tool via RUBE_MULTI_EXECUTE_TOOL, including memory and a session_id.

Best Practices

Always search first: tool schemas change, so avoid hardcoding slugs or arguments.
Check connection: verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before execution.
Schema compliance: use exact field names and types from the search results.
Memory parameter: include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty.
Session reuse: reuse session IDs within a workflow and generate new ones for new workflows.

Example Use Cases

Nightly Borneo task sync: discover available tools with RUBE_SEARCH_TOOLS and then execute the appropriate tool slug with RUBE_MULTI_EXECUTE_TOOL.
On-demand Borneo operation: look up current tool schemas first, then run the chosen tool without hardcoding slugs.
Batch Borneo tasks: use RUBE_REMOTE_WORKBENCH to run multiple Composio tools in a single batch.
Session-based workflow: reuse a session ID across a sequence of Borneo tasks for continuity.
Failure-safe automation: verify ACTIVE connection before execution and gracefully handle tool schema changes.

Frequently Asked Questions

Add this skill to your agents