bonsai-automation
npx machina-cli add skill ComposioHQ/awesome-claude-skills/bonsai-automation --openclawBonsai Automation via Rube MCP
Automate Bonsai operations through Composio's Bonsai toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/bonsai
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Bonsai connection via
RUBE_MANAGE_CONNECTIONSwith toolkitbonsai - 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 toolkitbonsai - 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: "Bonsai 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 Bonsai task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["bonsai"]
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 Bonsai-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit bonsai |
| 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/bonsai-automation/SKILL.mdView on GitHub Overview
Bonsai Automation via Rube MCP automates Bonsai operations through Composio's Bonsai toolkit using the Rube MCP integration. It emphasizes discovering current tool schemas first and ensuring an active Bonsai connection before running workflows.
How This Skill Works
It starts by discovering available tools with RUBE_SEARCH_TOOLS and the Bonsai use_case to fetch slugs and schemas. Then you verify the Bonsai connection via RUBE_MANAGE_CONNECTIONS. Finally, you execute tooling through RUBE_MULTI_EXECUTE_TOOL, passing the discovered tool_slug, the schema-compliant arguments, a memory payload, and the session_id.
When to Use It
- When you need to automate Bonsai operations and want up-to-date tool schemas.
- When ensuring an active Bonsai connection before running workflows.
- When discovering and selecting the exact Bonsai tool slug from current tools.
- When reusing the same session across multiple steps in a Bonsai workflow.
- When tool discovery returns large results requiring pagination handling.
Quick Start
- Step 1: RUBE_SEARCH_TOOLS with queries: [{use_case: "Bonsai operations"}] to fetch available tool slugs and schemas.
- Step 2: RUBE_MANAGE_CONNECTIONS with toolkits: ["bonsai"] and verify the session shows ACTIVE.
- Step 3: RUBE_MULTI_EXECUTE_TOOL with tool_slug from search results, proper arguments, memory: {}, and the session_id.
Best Practices
- Always call RUBE_SEARCH_TOOLS first to fetch current tool schemas.
- Check that RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools.
- Use exact field names and types from the search results.
- Always include memory in RUBE_MULTI_EXECUTE_TOOL calls (empty {} is allowed).
- Reuse session IDs within a workflow, but generate new ones for new workflows.
Example Use Cases
- Discover available Bonsai operations with RUBE_SEARCH_TOOLS using use_case: Bonsai operations to obtain tool slugs and schemas.
- Connect to Bonsai by calling RUBE_MANAGE_CONNECTIONS with toolkit: bonsai and verify the ACTIVE status.
- Execute a discovered Bonsai tool via RUBE_MULTI_EXECUTE_TOOL using the returned tool_slug and proper arguments.
- Bulk operations with RUBE_REMOTE_WORKBENCH to run composio tool tasks across multiple tools.
- Retrieve full tool schemas with RUBE_GET_TOOL_SCHEMAS for tools that include a schemaRef.
