What prerequisites are required to use botstar-automation?

Rube MCP must be connected, Botstar must be linked via RUBE_MANAGE_CONNECTIONS, and you must always call RUBE_SEARCH_TOOLS to obtain current tool schemas.

Is an API key needed for Botstar automation?

No API keys are required. You add the MCP endpoint, connect Botstar, and use the provided tool schemas.

How should I handle changes in tool schemas?

Always search for tools first with RUBE_SEARCH_TOOLS, avoid hardcoding slugs or fields, ensure exact field names/types, and include memory in multi-execute calls. Reuse sessions where appropriate and fetch new IDs for new workflows.

botstar-automation

npx machina-cli add skill ComposioHQ/awesome-claude-skills/botstar-automation --openclaw

Files (1)

SKILL.md

2.9 KB

Botstar Automation via Rube MCP

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

Toolkit docs: 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.

Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds
Call RUBE_MANAGE_CONNECTIONS with toolkit botstar
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: "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

Source

git clone https://github.com/ComposioHQ/awesome-claude-skills/blob/master/composio-skills/botstar-automation/SKILL.mdView on GitHub

Overview

This skill automates Botstar operations through Composio's Botstar toolkit using Rube MCP. It requires you to always search for current tool schemas with RUBE_SEARCH_TOOLS and ensure the Botstar connection is ACTIVE before executing workflows. This keeps automations aligned with live tool definitions and avoids hard-coded slugs.

How This Skill Works

Set up Rube MCP as an MCP server and verify availability with RUBE_SEARCH_TOOLS. Manage the Botstar connection using RUBE_MANAGE_CONNECTIONS and ensure the status is ACTIVE. Retrieve tool schemas, then execute the chosen Botstar tool via RUBE_MULTI_EXECUTE_TOOL, supplying exact schema fields and including memory and session context.

When to Use It

You need to perform a Botstar task and want the latest tool schemas before execution.
Tool schemas have changed and you’re updating an existing Botstar automation.
You must verify the Botstar connection is ACTIVE before running workflows.
You want to run a sequence of Botstar tools within a single session to reuse IDs.
You’re performing bulk Botstar operations via RUBE_REMOTE_WORKBENCH.

Quick Start

Step 1: Add the MCP endpoint https://rube.app/mcp and verify with RUBE_SEARCH_TOOLS.
Step 2: Manage Botstar connection with RUBE_MANAGE_CONNECTIONS and ensure ACTIVE status.
Step 3: Discover tools, then execute a tool with RUBE_MULTI_EXECUTE_TOOL using memory and a session_id.

Best Practices

Always call RUBE_SEARCH_TOOLS before any execution to get current tool schemas.
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE for the Botstar toolkit before running tools.
Use exact field names and types from the search results; avoid hardcoding slugs.
Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty.
Reuse session IDs within a workflow and generate new IDs only for new workflows.

Example Use Cases

Discover available Botstar tools and create a new project using the returned tool slug and schema.
Connect the Botstar toolkit and fetch a Botstar project status with a single tool execution.
Execute a Botstar tool with arguments derived directly from the live tool schema.
Run multiple Botstar actions within one session to avoid repeated authentications.
Perform a bulk Botstar operation via RUBE_REMOTE_WORKBENCH and run_composio_tool.

Frequently Asked Questions

Add this skill to your agents