Skip to main content
NEW · APP STORE Now on iOS · macOS · iPad Android & Windows soon GET IT
Prompts Chatbotkit Rube MCP Automation Guide

agent tool_use skill risk: low

Chatbotkit Rube MCP Automation Guide

Instructs the model to automate Chatbotkit operations through Composio's Rube MCP by first calling RUBE_SEARCH_TOOLS, managing connections with RUBE_MANAGE_CONNECTIONS, and executi…

  • External action: medium

SKILL 1 file

SKILL.md
---
name: chatbotkit-automation
description: "Automate Chatbotkit tasks via Rube MCP (Composio). Always search tools first for current schemas."
---
# Chatbotkit Automation via Rube MCP

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

**Toolkit docs**: [composio.dev/toolkits/chatbotkit](https://composio.dev/toolkits/chatbotkit)

## Prerequisites

- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Chatbotkit connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `chatbotkit`
- 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.

1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `chatbotkit`
3. If connection is not ACTIVE, follow the returned auth link to complete setup
4. 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_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 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](https://composio.dev)*

REQUIRED CONTEXT

  • RUBE_SEARCH_TOOLS availability
  • active chatbotkit connection via RUBE_MANAGE_CONNECTIONS

OPTIONAL CONTEXT

  • existing session_id

TOOLS REQUIRED

  • RUBE_SEARCH_TOOLS
  • RUBE_MANAGE_CONNECTIONS
  • RUBE_MULTI_EXECUTE_TOOL
  • RUBE_REMOTE_WORKBENCH
  • RUBE_GET_TOOL_SCHEMAS

ROLES & RULES

  1. Always search tools first for current schemas.
  2. Always call RUBE_SEARCH_TOOLS first to get current tool schemas
  3. Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds
  4. If connection is not ACTIVE, follow the returned auth link to complete setup
  5. Confirm connection status shows ACTIVE before running any workflows
  6. Always discover available tools before executing workflows
  7. Never hardcode tool slugs or arguments without calling RUBE_SEARCH_TOOLS
  8. Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing tools
  9. Use exact field names and types from the search results
  10. Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty
  11. Reuse session IDs within a workflow
  12. Generate new session IDs for new workflows
  13. Check responses for pagination tokens and continue fetching until complete

EXPECTED OUTPUT

Format
markdown
Constraints
  • always search tools first
  • check connection status before execution
  • use exact schemas from search results
  • include memory parameter

SUCCESS CRITERIA

  • Always search first
  • Check connection status
  • Use schema-compliant arguments
  • Include memory parameter

FAILURE MODES

  • Hardcode tool slugs or arguments
  • Skip connection verification
  • Omit memory parameter
  • Ignore pagination tokens

EXAMPLES

Includes multiple example tool call blocks for RUBE_SEARCH_TOOLS, RUBE_MANAGE_CONNECTIONS, and RUBE_MULTI_EXECUTE_TOOL.

CAVEATS

Dependencies
  • Rube MCP connection
  • Active Chatbotkit connection via RUBE_MANAGE_CONNECTIONS
Missing context
  • Concrete examples of Chatbotkit tasks to execute
  • Expected final output format or success criteria for workflows
Ambiguities
  • Placeholder text 'your specific Chatbotkit task' left in the example without guidance on substitution.

QUALITY

OVERALL
0.76
CLARITY
0.88
SPECIFICITY
0.90
REUSABILITY
0.55
COMPLETENESS
0.78

IMPROVEMENT SUGGESTIONS

  • Replace the literal placeholder 'your specific Chatbotkit task' with a variable or a set of example use cases.
  • Add a short 'Success Criteria' section that defines when a workflow is considered complete.

USAGE

Copy the prompt above and paste it into your AI of choice — Claude, ChatGPT, Gemini, or anywhere else you're working. Replace any placeholder sections with your own context, then ask for the output.

MORE FOR AGENT