home / skills / composiohq / awesome-claude-skills / botstar-automation

botstar-automation skill

safe

/botstar-automation

This skill automates Botstar tasks through Rube MCP by discovering tool schemas first and ensuring active connections before execution.

npx playbooks add skill composiohq/awesome-claude-skills --skill botstar-automation

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

2.9 KB

---
name: botstar-automation
description: "Automate Botstar tasks via Rube MCP (Composio). Always search tools first for current schemas."
requires:
  mcp: [rube]
---

# Botstar Automation via Rube MCP

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

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

## Prerequisites

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

### Step 2: Check Connection

```
RUBE_MANAGE_CONNECTIONS
toolkits: ["botstar"]
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 Botstar-specific use case |
| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `botstar` |
| 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)*

Overview

This skill automates Botstar tasks using Composio's Botstar toolkit via Rube MCP. It guides discovery of available tools, manages Botstar connections, and runs toolkit actions through RUBE_* RPC calls. Follow the prescribed discovery and connection checks to avoid schema or auth errors.

How this skill works

The skill instructs you to always call RUBE_SEARCH_TOOLS first to retrieve current tool slugs and input schemas. It uses RUBE_MANAGE_CONNECTIONS to ensure the Botstar toolkit connection is ACTIVE, then runs actions with RUBE_MULTI_EXECUTE_TOOL (including an explicit memory object) or bulk operations via RUBE_REMOTE_WORKBENCH. It recommends reusing session IDs within a workflow and handling pagination when listing results.

When to use it

Automate Botstar chatbot creation, updates, or exports.
Run multi-step Botstar workflows that require discovering available toolkit actions first.
Integrate Botstar operations into CI/CD or backend automation pipelines.
Perform bulk operations across multiple bots using the remote workbench.
When you need up-to-date tool schemas before executing actions.

Best practices

Always call RUBE_SEARCH_TOOLS first; tool slugs and schemas change frequently.
Verify connection status with RUBE_MANAGE_CONNECTIONS and complete any returned auth flow until status is ACTIVE.
Provide exact field names and types from the returned schemas; do not guess or hardcode arguments.
Include a memory object (can be empty {}) in RUBE_MULTI_EXECUTE_TOOL calls.
Reuse a session_id for related workflow steps; generate a new session for separate workflows.
Handle pagination for search and list responses to ensure complete data retrieval.

Example use cases

Discover Botstar actions for a specific use case, then provision a new chatbot using the discovered tool schema.
Check and renew the Botstar connection, then run a nightly sync that exports bot configurations.
Bulk-update dialog nodes across several bots using RUBE_REMOTE_WORKBENCH and run_composio_tool().
Integrate Botstar workflows into an automated pipeline that first searches tools, validates schemas, then executes multi-step operations.
Run a diagnostic: search tools, fetch full schemas via RUBE_GET_TOOL_SCHEMAS, and validate local automation against the authoritative schema.

FAQ

Do I need API keys to use Rube MCP?

No API keys are required; add the MCP endpoint (https://rube.app/mcp) to your client configuration and use the RUBE_* calls.

What if a tool schema changes during a workflow?

Always re-run RUBE_SEARCH_TOOLS at the start of a new workflow and validate arguments against the returned schema. Use session reuse only within a stable workflow.