$ ~/registry/skill/composiohq-composio-skills-botstar-automation

SKILL

botstar-automation

Name: botstar-automation
Author: Composio

Automate Botstar workflows via Rube MCP using current tool schemas first.

Stars

★ 67,763

Source

GitHub

Updated

2026-07-15

// securityCaution

Prompt only, no code
Open source
Community-trusted· 64.7k

Summary

The skill material itself is essentially prompt/documentation-like, open source, and backed by strong community signals, so overall risk is low. The main caution is that it relies on external Rube MCP and Botstar authorization, which means prompts and relevant business data may be sent to third-party services during use.

CredentialsCaution

The material says 'No API keys needed,' but it still requires an ACTIVE `botstar` connection via `RUBE_MANAGE_CONNECTIONS` and completing auth through a returned link. This suggests credentials are likely brokered by Rube/Composio rather than exposed as local environment variables. No direct red flag of local secret harvesting is shown, but third-party account authorization still carries normal misuse and over-authorization concerns.

Network egressCaution

The README explicitly instructs adding `https://rube.app/mcp` as an MCP server and performing actions through the Composio/Botstar toolchain. Therefore, user requests, tool arguments, and some business data may be sent to Rube/Composio and the target Botstar service. The egress appears related to the stated functionality, with no evidence of unrelated or hidden endpoints, but it is still a clear external data flow.

Code executionLow risk

Based on the provided material, this is a prompt-only skill/documentation artifact with no local install script, shell commands, dependency execution, or request for system-level execution privileges. It guides the use of existing MCP tools, but the skill itself does not appear to directly spawn local processes or execute arbitrary code.

Data accessCaution

The material does not show any need to read local files, directories, or system data, but once Botstar authorization is completed it can query and automate actions on Botstar resources through discovered tools, including bulk operations and pagination. The data access scope appears to be mainly within the connected third-party business account, which is a normal functional-access risk.

Supply chainLow risk

The source is an open GitHub repository with strong community adoption signals (64.7k stars), both of which materially reduce risk. Although the license is not stated and maintenance status is unknown, and this appears to be a skill description rather than the full backend implementation, the supply-chain posture of the provided material is closer to low risk than high risk.

Recommendations

Only authorize Rube/Composio when Botstar automation is actually needed, and prefer least-privilege accounts or a test environment.
Before connecting, review the data-handling terms of rube.app/mcp, Composio, and Botstar, and avoid sending highly sensitive customer data in tool arguments.
Inspect the actual schemas returned by `RUBE_SEARCH_TOOLS` before execution to reduce unexpected actions caused by dynamic schema changes.
Add human review or operation limits for bulk, delete, or update actions to reduce the impact of mistakes.

Audited by: gpt-5.4 · 2026-06-17

// install

Copy the install command and let the AI configure it · recommended for beginners

Please install the "botstar-automation" skill from askskill:
1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/botstar-automation/SKILL.md
2. Save it as ~/.claude/skills/botstar-automation/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// docs

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

Automate Autom workflows via Rube MCP while checking current tool schemas first.

ComposioGet→

$ loading_