agent tool_use skill risk: high
Botsonic Automation via Rube MCP
Provides instructions for automating Botsonic operations through Composio's Rube MCP toolkit, including prerequisites, tool discovery with RUBE_SEARCH_TOOLS, connection management,…
- Policy sensitive
- Human review
- External action: high
SKILL 1 file
SKILL.md
---
name: botsonic-automation
description: "Automate Botsonic tasks via Rube MCP (Composio). Always search tools first for current schemas."
---
# Botsonic Automation via Rube MCP
Automate Botsonic operations through Composio's Botsonic toolkit via Rube MCP.
**Toolkit docs**: [composio.dev/toolkits/botsonic](https://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.
1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `botsonic`
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: "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](https://composio.dev)*
REQUIRED CONTEXT
- Rube MCP connection
- Botsonic toolkit connection
OPTIONAL CONTEXT
- specific Botsonic use case
- existing session_id
TOOLS REQUIRED
- RUBE_SEARCH_TOOLS
- RUBE_MANAGE_CONNECTIONS
- RUBE_MULTI_EXECUTE_TOOL
- RUBE_REMOTE_WORKBENCH
- RUBE_GET_TOOL_SCHEMAS
ROLES & RULES
- Always search tools first for current schemas.
- Always call RUBE_SEARCH_TOOLS first to get current tool schemas.
- Always discover available tools before executing workflows.
- Never hardcode tool slugs or arguments without calling RUBE_SEARCH_TOOLS.
- Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing 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.
- Generate new session IDs for new workflows.
- Check responses for pagination tokens and continue fetching until complete.
EXPECTED OUTPUT
- Format
- markdown
- Constraints
- always call RUBE_SEARCH_TOOLS first
- verify ACTIVE connection before execution
- reuse session IDs within workflow
SUCCESS CRITERIA
- Verify Rube MCP availability first
- Confirm Botsonic connection is ACTIVE
- Use only schema-compliant arguments from search results
FAILURE MODES
- Hardcoding tool slugs or arguments without searching first
- Executing tools before confirming ACTIVE connection
- Omitting the memory parameter in execute calls
- Failing to reuse or manage session IDs correctly
EXAMPLES
Includes multiple example RUBE_* tool calls showing discovery, connection check, and execution patterns.
CAVEATS
- Dependencies
- Rube MCP must be connected
- Active Botsonic connection via RUBE_MANAGE_CONNECTIONS
- Missing context
- Target MCP client or environment where this prompt will be used
- Concrete example of a full end-to-end task execution
- Ambiguities
- Placeholder text "your specific Botsonic task" left in example without clarification on how to fill it.
- Session management syntax (generate_id vs existing id) is shown inconsistently across examples.
QUALITY
- OVERALL
- 0.77
- CLARITY
- 0.82
- SPECIFICITY
- 0.78
- REUSABILITY
- 0.71
- COMPLETENESS
- 0.80
IMPROVEMENT SUGGESTIONS
- Replace the literal placeholder "your specific Botsonic task" with a brief instruction such as "[describe the exact Botsonic operation]".
- Add one complete worked example showing a full sequence of RUBE_* calls for a common operation such as listing bots.
USAGE
Copy the prompt above and paste it into your AI of choice — Claude, ChatGPT, Gemini, or anywhere else you're working. Replace any placeholder sections with your own context, then ask for the output.
MORE FOR AGENT
- Xcode MCP Usage Guidelines for Agentsagenttool_use
- Xcode MCP Usage Guidelinesagenttool_use
- Xquik X/Twitter API Integration Skillagenttool_use
- Filesystem Agent Context Engineeringagenttool_use
- Agent Tool Design Principlesagenttool_use
- Conventional Git Commit Creatoragenttool_use
- GitHub Trending Dashboard Generatoragenttool_use
- Hosted Background Agent Infrastructureagenttool_use
- AudioCraft Text-to-Music Generation Guideagenttool_use
- Trello Boards Lists Cards Integratoragenttool_use
- Git Commit Push PR Automatoragenttool_use
- GitHub Starred Projects Fetcher via Agent Browseragenttool_use
- 2chat Rube MCP Automation Guideagenttool_use
- Rube MCP Autom Task Automationagenttool_use
- Botbaba Automation via Rube MCPagenttool_use
- Aero Workflow Rube MCP Automationagenttool_use
- Boldsign Automation via Rube MCPagenttool_use
- API Sports Rube MCP Automation Guideagenttool_use
- Bolt IoT Rube MCP Automation Guideagenttool_use
- Booqable Automation via Rube MCPagenttool_use
- Coassemble Automation via Rube MCPagenttool_use
- D2L Brightspace Rube MCP Automation Guideagenttool_use
- Codacy Automation via Rube MCPagenttool_use
- Conversion Tools Rube MCP Automationagenttool_use
- Codereadr Automation via Rube MCPagenttool_use