Why should I always search tools first?

Tool schemas change; fetching current slugs and input definitions with RUBE_SEARCH_TOOLS prevents mismatches.

What should I do if the API Bible connection isn't ACTIVE?

Follow the auth link returned by RUBE_MANAGE_CONNECTIONS to complete setup, then re-check until ACTIVE.

Do I need to include memory in every multi-execute call?

Yes. Include memory (even if empty {}) in RUBE_MULTI_EXECUTE_TOOL calls to preserve state and context.

api-bible-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

API Bible Automation via Rube MCP

Automate API Bible operations through Composio's API Bible toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/api_bible

Prerequisites

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

Step 2: Check Connection

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

Overview

api-bible-automation lets you automate API Bible operations through Composio's Rube MCP toolkit. It emphasizes discovering current tool schemas via RUBE_SEARCH_TOOLS before any workflow to ensure correct slugs and inputs. The flow guides you from connecting the Rube MCP, validating the API Bible connection, to executing tools with discovered schemas.

How This Skill Works

Set up a Rube MCP endpoint, verify availability with RUBE_SEARCH_TOOLS, and then manage the api_bible connection with RUBE_MANAGE_CONNECTIONS. When ACTIVE, run tools using RUBE_MULTI_EXECUTE_TOOL with the discovered tool_slug and schema-aligned arguments, always including memory and a session_id.

When to Use It

When you need up-to-date API Bible tool schemas before building a workflow
When you must establish or verify an ACTIVE API Bible connection via RUBE_MANAGE_CONNECTIONS
When executing a workflow that relies on discovered tool slugs and inputs
When tool schemas change and hardcoding slugs would break automation
When performing batch operations with multiple tools in a single session

Quick Start

Step 1: Set up Rube MCP and verify RUBE_SEARCH_TOOLS responds.
Step 2: Connect api_bible with RUBE_MANAGE_CONNECTIONS and ensure the status is ACTIVE.
Step 3: Discover tools with RUBE_SEARCH_TOOLS for your API Bible task, then run RUBE_MULTI_EXECUTE_TOOL with the discovered slug and a memory object, providing a session_id.

Best Practices

Always call RUBE_SEARCH_TOOLS first to fetch current schemas
Verify the RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools
Use exact field names and types from search results
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({})
Reuse session IDs within a workflow and generate new ones for new workflows

Example Use Cases

Discover tools and run a single API Bible operation using a discovered slug
Run a multi-step API Bible workflow by discovering tools, ensuring ACTIVE connection, then executing tools in sequence
Audit API Bible tool schemas by periodically running RUBE_SEARCH_TOOLS and adjusting automation
Perform a bulk batch of API Bible tasks with RUBE_MULTI_EXECUTE_TOOL in a single session
Troubleshoot failures by checking tool slugs and input schemas against the latest tool schemas

Frequently Asked Questions

Add this skill to your agents