chatbotkit-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/chatbotkit-automation --openclawChatbotkit Automation via Rube MCP
Automate Chatbotkit operations through Composio's Chatbotkit toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/chatbotkit
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Chatbotkit connection via
RUBE_MANAGE_CONNECTIONSwith toolkitchatbotkit - 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 toolkitchatbotkit - 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: "Chatbotkit 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 Chatbotkit task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["chatbotkit"]
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 Chatbotkit-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit chatbotkit |
| 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/chatbotkit-automation/SKILL.mdView on GitHub Overview
This skill automates Chatbotkit operations using Composio's toolkit through Rube MCP. It emphasizes discovering current tool schemas before execution and managing connections to ensure tools run against the latest definitions.
How This Skill Works
First discover available tools with RUBE_SEARCH_TOOLS for your use case. Then verify an ACTIVE connection using RUBE_MANAGE_CONNECTIONS and finally execute the chosen tool with RUBE_MULTI_EXECUTE_TOOL, supplying memory and exact schema fields from the discovered tool.
When to Use It
- When you need current Chatbotkit tool schemas before building an automation workflow
- When establishing or rechecking the ACTIVE status of a Rube MCP connection to chatbotkit
- When selecting a discovered tool slug and running it with the correct, schema-aligned arguments
- When performing bulk tool executions via RUBE_REMOTE_WORKBENCH and run_composio_tool()
- When integrating multi-step workflows and reusing session IDs to maintain context
Quick Start
- Step 1: Add https://rube.app/mcp as an MCP server in your client configuration
- Step 2: Run RUBE_SEARCH_TOOLS with use_case like 'Chatbotkit operations' to discover tools and schemas
- Step 3: Run RUBE_MANAGE_CONNECTIONS for toolkit 'chatbotkit' and then execute a tool with RUBE_MULTI_EXECUTE_TOOL, including memory
Best Practices
- Always call RUBE_SEARCH_TOOLS first to get current tool schemas
- Check that RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools
- Use exact field names and types from the search results (no hardcoding)
- Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty
- Reuse session IDs within a workflow to maintain context; generate new ones for separate runs
Example Use Cases
- Discover tools for a Chatbotkit use case and inspect input schemas to determine required fields
- Establish and verify an ACTIVE chatbotkit connection via RUBE_MANAGE_CONNECTIONS before running tools
- Execute a discovered tool slug with arguments pulled from the latest tool schema
- Perform bulk tool operations using RUBE_REMOTE_WORKBENCH to run multiple tools in one workflow
- Fetch full tool schemas with RUBE_GET_TOOL_SCHEMAS to review schemaRef and field definitions