home / skills / composiohq / awesome-claude-skills / battlenet-automation

battlenet-automation skill

safe

This skill automates Battlenet tasks via Rube MCP, discovering current tool schemas first for reliable, up-to-date workflows.

npx playbooks add skill composiohq/awesome-claude-skills --skill battlenet-automation

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

2.9 KB

---
name: battlenet-automation
description: "Automate Battlenet tasks via Rube MCP (Composio). Always search tools first for current schemas."
requires:
  mcp: [rube]
---

# Battlenet Automation via Rube MCP

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

**Toolkit docs**: [composio.dev/toolkits/battlenet](https://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.

1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `battlenet`
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: "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](https://composio.dev)*

Overview

This skill automates Battlenet tasks through Composio’s Battlenet toolkit using the Rube MCP orchestration layer. It guides tool discovery, connection management, and safe execution of Battlenet operations while enforcing schema compliance and session handling. Use it to run individual actions or bulk workflows against Battlenet services programmatically.

How this skill works

The skill first calls RUBE_SEARCH_TOOLS to discover current tool slugs and input schemas for Battlenet operations. It then verifies or creates an active Battlenet connection via RUBE_MANAGE_CONNECTIONS. Actual operations run through RUBE_MULTI_EXECUTE_TOOL (or RUBE_REMOTE_WORKBENCH for bulk runs) using schema-compliant arguments, an explicit session_id, and a memory object. It always checks for pagination and connection status before proceeding.

When to use it

Automating routine Battlenet account or game-service tasks
Running bulk or batch operations against Battlenet via Composio tools
Integrating Battlenet actions into larger agent workflows
When reliable schema-aware execution and session management are required
Before calling any Battlenet tool to avoid schema drift or auth failures

Best practices

Always invoke RUBE_SEARCH_TOOLS first — do not hardcode tool slugs or fields
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools
Include a memory object in every RUBE_MULTI_EXECUTE_TOOL call, even if empty ({})
Reuse session_id within a workflow; create a new session for separate flows
Respect exact field names and types from returned schemas and handle pagination tokens

Example use cases

Query available Battlenet services and their current schemas to build dynamic UIs
Execute a series of Battlenet account maintenance tasks as a batched workflow
Trigger game-related operations across multiple accounts using RUBE_REMOTE_WORKBENCH
Automate periodic data pulls from Battlenet APIs while safely handling pagination and sessions
Integrate Battlenet tool calls into a multi-step Claude agent workflow with schema-driven validation

FAQ

Do I need API keys to use Rube MCP?

No API keys are required. Add https://rube.app/mcp as your MCP server and use the exposed RUBE_* tool endpoints.

What if a tool schema changes mid-workflow?

Always call RUBE_SEARCH_TOOLS at the start and re-check schemas before critical steps; do not hardcode fields. If a schema changed, update arguments to match the returned schema and retry.

What happens if the Battlenet connection is not ACTIVE?

RUBE_MANAGE_CONNECTIONS will return an auth link or instructions. Complete the auth flow and confirm the connection shows ACTIVE before running tools.