FreePublished on GitHubEnglish overview

botstar-automation

Run Botstar tasks through Rube MCP, a connection for agent tools. The skill discovers available operations, retrieves their current input requirements, verifies an active service connection, and executes actions through Composio.

OriginalShow the original description

Automate Botstar tasks via Rube MCP (Composio). Always search tools first for current schemas.

ComposioHQ/awesome-claude-skills

Run score Not tested

See how to install

Good for

Discovering available Botstar operations
Checking authentication and connection status
Automating repeated Botstar tasks
Running bulk actions with discovered tools

Overview

What it does

This skill lets you delegate Botstar tasks to an AI agent through Rube MCP. It searches Composio's tools for operations that match your goal and checks the required input fields and formats. It defines a workflow that verifies the connection before executing the task with the discovered tools.

When it helps

Use it to delegate recurring Botstar tasks or check the operations currently available before proceeding. It also explains bulk execution for handling multiple operations together. Within a single workflow, it reuses the session ID that links the operations.

Example requests

“Find the Botstar operations currently available and their input fields.”
“Check authentication and connection status, then carry out the specified task.”
“Use the tools found in the search to execute the specified operations in a batch.”

Notes

You need Rube MCP and an authenticated Botstar connection with ACTIVE status. Adding Rube MCP itself is described as requiring no API key. Tool specifications can change, so a search is required before execution. The source does not list individual Botstar operations; search to confirm which specific tasks are supported.

This overview was written by AI (OpenAI Codex) from the public SKILL.md. Check the original below for the exact behavior.

Document check

AI checked the SKILL.md for operations that need care and for setup requirements. The score comes only from actually running the skill (hands-on test).

SafetyAre sending data, deleting files, and running commands disclosed?: BPartly lackingIt executes external tools, but does not document the scope of their effects or approval steps before execution.
Easy setupDoes it need few tools or API keys, and are they documented?: AGoodInstructions explain how to add Rube MCP and configure the service connection through an authentication link.

Not counted in the score. Rated by AI (OpenAI Codex) as of Oct 21, 2026. Treat it as a guide and read the original before installing.

Disagree? Request a re-evaluation

Files included (1)

SKILL.md2.9 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

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

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

More skills from this repository

-21risk-automation

FreeSummary

Automate 21risk operations through Rube MCP, a connection for agent tools. The skill discovers available actions, checks the service connection, and uses current input requirements to carry out requested tasks.

Find available 21risk actions
Run tasks after checking the service connection
Process multiple operations in bulk