Do I always need to search for tools before executing?

Yes. Tool schemas change, so always call RUBE_SEARCH_TOOLS to obtain current slugs and inputs.

How do I prevent using stale tool slugs?

RUBE_SEARCH_TOOLS returns current slugs and input schemas. For full schemas, use RUBE_GET_TOOL_SCHEMAS.

How can I perform bulk Apex27 tasks?

Use RUBE_REMOTE_WORKBENCH with run_composio_tool() to execute multiple tools or workflows in bulk.

apex27-automation

Scanned

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

Files (1)

SKILL.md

2.8 KB

Apex27 Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/apex27

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Apex27 operations through Composio's Apex27 toolkit via Rube MCP. Always search tool schemas first to stay aligned with current slugs and inputs. This workflow covers tool discovery, connection checks, execution, and memory/session handling.

How This Skill Works

Connect to Rube MCP and Apex27 using the Apex27 toolkit. First, call RUBE_SEARCH_TOOLS to retrieve current tool slugs and input schemas, then validate the connection with RUBE_MANAGE_CONNECTIONS. Finally, execute the chosen tool via RUBE_MULTI_EXECUTE_TOOL, ensuring memory is supplied and the same session_id is reused across steps.

When to Use It

Automating routine Apex27 tasks with up-to-date tool schemas
Verifying Rube MCP connection and Apex27 linkage before execution
Discovering tools and their required input schemas before crafting tool calls
Reusing a session_id across a multi-step Apex27 workflow for efficiency
Handling bulk Apex27 tasks via multi-tool execution or remote bench

Quick Start

Step 1: Connect Rube MCP to https://rube.app/mcp and verify RUBE_SEARCH_TOOLS responds.
Step 2: Run RUBE_SEARCH_TOOLS for 'Apex27 operations' and note available tool_slugs and input schemas.
Step 3: Choose a tool_slug, check ACTIVE with RUBE_MANAGE_CONNECTIONS, then run RUBE_MULTI_EXECUTE_TOOL with memory and a session_id.

Best Practices

Always call RUBE_SEARCH_TOOLS first to get current tool slugs and input schemas
Check that RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools
Use exact field names and types from the discovered schemas; avoid hardcoding
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty
Reuse session IDs within a workflow; generate new IDs for new workflows; monitor pagination

Example Use Cases

Discover tools for Apex27 operations, select a slug, and execute with appropriate arguments using a single session.
Connect to the apex27 toolkit and confirm ACTIVE status before running a workflow.
Run a multi-step Apex27 task sequence in one session by reusing the same session_id across RUBE_SEARCH_TOOLS, RUBE_MANAGE_CONNECTIONS, and RUBE_MULTI_EXECUTE_TOOL.
Fetch full tool schemas with RUBE_GET_TOOL_SCHEMAS to adapt to changing inputs.
Bulk process Apex27 tasks via RUBE_REMOTE_WORKBENCH run_composio_tool() for efficiency.

Frequently Asked Questions

Add this skill to your agents