bookingmood-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/bookingmood-automation --openclawBookingmood Automation via Rube MCP
Automate Bookingmood operations through Composio's Bookingmood toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/bookingmood
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Bookingmood connection via
RUBE_MANAGE_CONNECTIONSwith toolkitbookingmood - Always call
RUBE_SEARCH_TOOLSfirst 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_TOOLSresponds - Call
RUBE_MANAGE_CONNECTIONSwith toolkitbookingmood - 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: "Bookingmood 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 Bookingmood task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["bookingmood"]
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_CONNECTIONSshows ACTIVE status before executing tools - Schema compliance: Use exact field names and types from the search results
- Memory parameter: Always include
memoryinRUBE_MULTI_EXECUTE_TOOLcalls, 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 Bookingmood-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit bookingmood |
| 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/bookingmood-automation/SKILL.mdView on GitHub Overview
Automate Bookingmood operations through Composio's Bookingmood toolkit via Rube MCP. The approach emphasizes always discovering current tool schemas before execution to avoid stale slugs. This enables end-to-end automation from discovery to execution with managed connections and session memory.
How This Skill Works
First, fetch available Bookingmood tool slugs and input schemas using RUBE_SEARCH_TOOLS. Then verify the Bookingmood connection is ACTIVE with RUBE_MANAGE_CONNECTIONS, and finally execute the chosen tool with RUBE_MULTI_EXECUTE_TOOL, supplying memory and a session_id. This workflow relies on live schemas and strict schema adherence, updating slugs as tool schemas evolve.
When to Use It
- Automate a Bookingmood task end-to-end by discovering the appropriate tool slug and executing it.
- When tool schemas or slugs may change, fetch current tooling via RUBE_SEARCH_TOOLS before running.
- Before running, ensure the Bookingmood connection is ACTIVE with RUBE_MANAGE_CONNECTIONS.
- Run multi-step booking workflows in a single session with memory between tools.
- Handle large result sets or pagination by continuing to fetch tokens and reusing discovery.
Quick Start
- Step 1: Add https://rube.app/mcp as an MCP server in your client and verify RUBE_SEARCH_TOOLS responds.
- Step 2: Run RUBE_SEARCH_TOOLS with use_case: "Bookingmood operations" to discover tool slugs and schemas; start a session if needed.
- Step 3: Run RUBE_MULTI_EXECUTE_TOOL with the discovered tool_slug and proper arguments, including memory and a session_id.
Best Practices
- Always call RUBE_SEARCH_TOOLS first to get current tool schemas.
- Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools.
- Use exact field names and types from the search results; do not hardcode slugs.
- Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({}).
- Reuse session IDs within a workflow and manage pagination tokens when present.
Example Use Cases
- Auto-create a booking by discovering the latest tool slug via RUBE_SEARCH_TOOLS and executing it.
- Update a booking status after confirming an ACTIVE Bookingmood connection and using the correct tool slug.
- Cancel a batch of bookings by running multiple tools in one session with memory management.
- Execute a multi-step Bookingmood workflow that reuses the same session_id across tools.
- If tool schemas change, re-fetch tools at the start of the workflow to avoid hard-coded slugs.
