What is Battlenet automation via Rube MCP?

A workflow to automate Battlenet tasks by discovering tool schemas with RUBE_SEARCH_TOOLS and executing them through RUBE_MULTI_EXECUTE_TOOL, all coordinated via Rube MCP.

Do I need API keys for this skill?

No API keys are required. You connect to MCP (rube.app) and rely on RUBE_SEARCH_TOOLS and RUBE_MANAGE_CONNECTIONS to access Battlenet tools.

What if tool schemas change?

Always search tools first with RUBE_SEARCH_TOOLS before executing; do not hardcode slugs or field names to avoid failures.

battlenet-automation

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

Files (1)

SKILL.md

2.9 KB

Battlenet Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/battlenet

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Battlenet operations through Composio's Battlenet toolkit using Rube MCP. This approach emphasizes discovering current tool schemas before execution to keep workflows resilient.

How This Skill Works

The skill uses RUBE_SEARCH_TOOLS to fetch available Battlenet tools and their schemas, then validates connectivity with RUBE_MANAGE_CONNECTIONS. Finally, it executes the chosen tool via RUBE_MULTI_EXECUTE_TOOL, including a memory payload and an active session, ensuring you always reference up-to-date schemas.

When to Use It

When you need to automate routine Battlenet tasks without manual clicks.
When tool schemas may have changed and you must fetch them first.
When performing batch Battlenet operations within a single workflow session.
When verifying an ACTIVE Battlenet connection before running tools.
When reusing a session for related Battlenet workflows.

Quick Start

Step 1: Add the MCP server (https://rube.app/mcp) to your client and verify RUBE_SEARCH_TOOLS responses.
Step 2: Call RUBE_MANAGE_CONNECTIONS with toolkit battlenet and confirm ACTIVE status.
Step 3: Discover tools with RUBE_SEARCH_TOOLS and execute a chosen tool via RUBE_MULTI_EXECUTE_TOOL, including memory and session_id.

Best Practices

Always call RUBE_SEARCH_TOOLS first to get current tool schemas.
Check RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools.
Use exact field names and types from the search results (no guessing).
Always include memory in RUBE_MULTI_EXECUTE_TOOL calls (even if empty).
Reuse session IDs within a workflow or generate new ones for separate workflows.

Example Use Cases

Discover the Battlenet toolset and run a tool to fetch player stats using the discovered TOOL_SLUG_FROM_SEARCH.
Establish a Battlenet connection and execute a bulk update of settings for multiple accounts in one session.
Validate that the Battlenet connection is ACTIVE, then run a sequence of tools for account reconciliation.
Fetch all tool schemas via RUBE_GET_TOOL_SCHEMAS, then execute a matching tool with the correct schema fields.
Use RUBE_REMOTE_WORKBENCH and run_composio_tool to perform a batch of Battlenet operations in parallel.

Frequently Asked Questions

Add this skill to your agents