Do I need API keys or credentials to use botsonic-automation?

No API keys are required. Add the MCP server (https://rube.app/mcp) and follow the connection steps to use the toolkit.

What should I do before executing Botsonic tools?

Always search for tools with RUBE_SEARCH_TOOLS and ensure the connection is ACTIVE via RUBE_MANAGE_CONNECTIONS.

How do I handle changes to tool schemas?

RUBE_SEARCH_TOOLS must be used before execution; do not hardcode slugs or argument schemas and always pass a proper memory object with each RUBE_MULTI_EXECUTE_TOOL call.

botsonic-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Botsonic Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/botsonic

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["botsonic"]
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 Botsonic-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `botsonic`
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/botsonic-automation/SKILL.mdView on GitHub

Overview

Automate Botsonic operations through Composio's Botsonic toolkit via Rube MCP. This skill orchestrates discovery of current tool schemas, manages Botsonic connections, and executes tools in a session-aware workflow. Always fetch the latest schemas with RUBE_SEARCH_TOOLS to avoid hard-coded slugs.

How This Skill Works

Technically, you start by validating that Rube MCP is connected and that RUBE_SEARCH_TOOLS is available. Then you discover tools using a Botsonic use case, verify an ACTIVE connection with RUBE_MANAGE_CONNECTIONS, and finally execute the chosen tool via RUBE_MULTI_EXECUTE_TOOL, including a memory object and the current session_id.

When to Use It

When you need to automate routine Botsonic operations end-to-end.
When tool schemas change and you must retrieve current slugs and arguments.
When you require a verified ACTIVE Botsonic connection before execution.
When performing multi-step workflows that reuse a session and memory across tools.
When bulk-running Botsonic tasks or chaining tools through RUBE_REMOTE_WORKBENCH or run_composio_tool.

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server in your client configuration.
Step 2: Run RUBE_SEARCH_TOOLS to ensure Botsonic tool schemas are current.
Step 3: Call RUBE_MANAGE_CONNECTIONS with toolkit 'botsonic'; when ACTIVE, execute a tool via RUBE_MULTI_EXECUTE_TOOL with memory and session_id.

Best Practices

Always call RUBE_SEARCH_TOOLS before executing tools.
Check that RUBE_MANAGE_CONNECTIONS reports ACTIVE before running tools.
Use exact field names and types from the search results.
Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty.
Reuse session IDs within a workflow and fetch pagination tokens if necessary.

Example Use Cases

Automate a Botsonic data extraction by discovering the appropriate tool slug and running it with the required arguments.
Create a multi-tool Botsonic workflow that searches tools, validates connection, then executes two tools in sequence within the same session.
Run a diagnostic workflow to verify connectivity and tool availability before operations.
Update a Botsonic automation after a schema change by re-running RUBE_SEARCH_TOOLS and adjusting tool slugs.
Batch process Botsonic tasks using RUBE_MULTI_EXECUTE_TOOL in a bulk workflow via RUBE_REMOTE_WORKBENCH.

Frequently Asked Questions

Add this skill to your agents