Do I need API keys to use this skill?

No API keys are required. Add the Rube MCP endpoint (https://rube.app/mcp) as your MCP server and use RUBE_SEARCH_TOOLS to fetch current tool schemas.

Why must I search tools first?

Tool schemas change over time. Searching first ensures you have the latest tool_slugs and required arguments, reducing errors from hardcoded values.

What should I remember about session and memory?

Reuse session IDs within a workflow for continuity, and always include the memory parameter in RUBE_MULTI_EXECUTE_TOOL calls (even if empty) to preserve context.

booqable-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Booqable Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/booqable

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Booqable operations through Composio's Rube MCP toolkit. This skill emphasizes discovering current tool schemas via RUBE_SEARCH_TOOLS and ensuring an ACTIVE Booqable connection before executing workflows. It provides a reusable pattern to run discovered tools with properly structured arguments.

How This Skill Works

Connect Rube MCP and verify the ACTIVE status, then use RUBE_SEARCH_TOOLS to fetch current Booqable tool schemas. Choose a tool slug from the results and execute it with RUBE_MULTI_EXECUTE_TOOL, supplying exact schema-compliant arguments and memory. Follow the known workflow: discover tools, check connection, then execute the tool.

When to Use It

Automate common Booqable tasks (e.g., create a booking, update a booking, fetch details) by first discovering the relevant tool via RUBE_SEARCH_TOOLS.
When tool schemas change, and you must fetch the latest definitions before building or running automations.
Before running any workflow, confirm the Booqable connection is ACTIVE using RUBE_MANAGE_CONNECTIONS.
When a workflow spans multiple steps and you want to reuse a session ID for continuity.
For bulk or batch operations, using RUBE_REMOTE_WORKBENCH or multiple tool executions within a single workflow.

Quick Start

Step 1: Add the Rube MCP endpoint (https://rube.app/mcp) as an MCP server in your client and verify RUBE_SEARCH_TOOLS responds.
Step 2: Manage the Booqable connection with RUBE_MANAGE_CONNECTIONS and ensure the toolkit is set to booqable; confirm ACTIVE status.
Step 3: Discover the available tools with RUBE_SEARCH_TOOLS, then execute a chosen tool using RUBE_MULTI_EXECUTE_TOOL with memory and a valid session_id.

Best Practices

Always call RUBE_SEARCH_TOOLS before any workflow to get current tool schemas.
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools.
Use exact field names and types from the tool schemas; do not hardcode slugs or arguments.
Always include memory (even if empty, e.g., {}) in RUBE_MULTI_EXECUTE_TOOL calls.
Reuse session IDs within a workflow and generate a new one for new workflows.

Example Use Cases

Discover a Booqable create_booking tool, then execute it with customer and item details to create a new reservation.
Fetch and update a booking's status (e.g., from reserved to confirmed) using the corresponding tool slug.
Retrieve booking details for a given booking_id to display customer info and rental items.
Sync inventory levels after a reservation is created using a bulk operation tool.
Run a multi-step workflow to create a booking and then notify the customer via an automated message.

Frequently Asked Questions

Add this skill to your agents