epic-games-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/epic-games-automation --openclawEpic Games Automation via Rube MCP
Automate Epic Games operations through Composio's Epic Games toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/epic_games
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Epic Games connection via
RUBE_MANAGE_CONNECTIONSwith toolkitepic_games - Always call
RUBE_SEARCH_TOOLSfirst 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_TOOLSresponds - Call
RUBE_MANAGE_CONNECTIONSwith toolkitepic_games - 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: "Epic Games 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 Epic Games task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["epic_games"]
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_CONNECTIONSshows ACTIVE status before executing tools - Schema compliance: Use exact field names and types from the search results
- Memory parameter: Always include
memoryinRUBE_MULTI_EXECUTE_TOOLcalls, 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 Epic Games-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit epic_games |
| 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/epic-games-automation/SKILL.mdView on GitHub Overview
Automate Epic Games operations through Composio's Epic Games toolkit via Rube MCP. It requires an active Rube MCP connection and mandates always calling RUBE_SEARCH_TOOLS first to fetch current tool schemas. Follow the core workflow to discover tools, verify connections, and execute with the exact parameter schemas.
How This Skill Works
You discover available Epic Games tools with RUBE_SEARCH_TOOLS to obtain tool slugs and input schemas. Then you verify the connection with RUBE_MANAGE_CONNECTIONS and ensure it is ACTIVE before running workflows. Finally, execute tools using RUBE_MULTI_EXECUTE_TOOL with the discovered slug and arguments, including a memory payload and session_id.
When to Use It
- You need to automate routine Epic Games operations with repeatable, auditable workflows.
- Tool schemas change frequently, so you must fetch current slugs and argument schemas via RUBE_SEARCH_TOOLS.
- You want to ensure an ACTIVE Epic Games connection before executing any tools.
- You are orchestrating multiple tools in one workflow within a single session using RUBE_MULTI_EXECUTE_TOOL.
- You plan bulk Epic Games operations and want to scale with RUBE_REMOTE_WORKBENCH and run_composio_tool.
Quick Start
- Step 1: Add https://rube.app/mcp as an MCP server (no API keys needed) and verify connectivity.
- Step 2: Call RUBE_SEARCH_TOOLS with toolkit epic_games to fetch current tool slugs and input schemas; ensure status is available.
- Step 3: Call RUBE_MANAGE_CONNECTIONS for toolkit epic_games and, once ACTIVE, execute a tool with RUBE_MULTI_EXECUTE_TOOL including memory and a session_id.
Best Practices
- Always call RUBE_SEARCH_TOOLS before selecting or executing a tool slug.
- Check that RUBE_MANAGE_CONNECTIONS shows an ACTIVE status prior to execution.
- Use exact field names and types from the search results when constructing arguments.
- Include memory in every RUBE_MULTI_EXECUTE_TOOL call, even if empty ({}).
- Reuse session IDs within a workflow and paginate responses when necessary.
Example Use Cases
- Example 1: Discover tools for Epic Games operations, select a slug from the results, and execute it in a single session.
- Example 2: Establish an Epic Games connection via RUBE_MANAGE_CONNECTIONS, verify ACTIVE, then run a routine task tool.
- Example 3: Create a multi-tool workflow that runs two Epic Games tools in sequence within one session using RUBE_MULTI_EXECUTE_TOOL.
- Example 4: Use RUBE_GET_TOOL_SCHEMAS to compare current tool schemas before performing a migration or upgrade.
- Example 5: Perform bulk Epic Games operations with RUBE_REMOTE_WORKBENCH and run_composio_tool for scalable automation.
