Skip to main content
NEW · APP STORE Now on iOS · macOS · iPad Android & Windows soon GET IT
Prompts Epic Games Automation via Rube MCP

agent tool_use skill risk: medium

Epic Games Automation via Rube MCP

The prompt provides instructions for automating Epic Games operations through Composio's Epic Games toolkit via Rube MCP, including prerequisites, setup steps, tool discovery with…

  • Human review
  • External action: high

SKILL 1 file

SKILL.md
---
name: epic-games-automation
description: "Automate Epic Games tasks via Rube MCP (Composio). Always search tools first for current schemas."
---
# Epic 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](https://composio.dev/toolkits/epic_games)

## Prerequisites

- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Epic Games connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `epic_games`
- 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 `epic_games`
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: "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_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 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](https://composio.dev)*

REQUIRED CONTEXT

  • Rube MCP connection
  • Epic Games toolkit connection status

OPTIONAL CONTEXT

  • session_id
  • specific use_case for tool search

TOOLS REQUIRED

  • RUBE_SEARCH_TOOLS
  • RUBE_MANAGE_CONNECTIONS
  • RUBE_MULTI_EXECUTE_TOOL

ROLES & RULES

  1. Always search tools first for current schemas
  2. Always call RUBE_SEARCH_TOOLS first to get current tool schemas
  3. Always discover available tools before executing workflows
  4. Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds
  5. Call RUBE_MANAGE_CONNECTIONS with toolkit epic_games
  6. Confirm connection status shows ACTIVE before running any workflows
  7. Never hardcode tool slugs or arguments without calling RUBE_SEARCH_TOOLS
  8. Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing tools
  9. Use exact field names and types from the search results
  10. Always include memory in RUBE_MULTI_EXECUTE_TOOL calls even if empty
  11. Reuse session IDs within a workflow
  12. Generate new session IDs for new workflows
  13. 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
  • use exact schemas from search results

SUCCESS CRITERIA

  • Always search first
  • Check connection status is ACTIVE
  • Follow schema compliance
  • Include memory parameter
  • Reuse sessions appropriately

FAILURE MODES

  • Hardcoding tool slugs without searching first
  • Executing before confirming ACTIVE connection
  • Using incorrect field names from outdated schemas
  • Omitting the memory parameter
  • Not handling pagination

EXAMPLES

Includes multiple example RUBE tool calls (SEARCH_TOOLS, MANAGE_CONNECTIONS, MULTI_EXECUTE_TOOL) with sample arguments and session handling.

CAVEATS

Dependencies
  • Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
  • Active Epic Games connection via RUBE_MANAGE_CONNECTIONS
  • Session ID from prior RUBE_SEARCH_TOOLS call
Missing context
  • Target MCP client or environment
  • Example concrete Epic Games tasks with expected outputs
  • Error handling or retry strategy details
Ambiguities
  • Placeholder text "your specific Epic Games task" left unresolved in workflow example
  • Does not define what constitutes a complete or successful workflow outcome

QUALITY

OVERALL
0.79
CLARITY
0.85
SPECIFICITY
0.78
REUSABILITY
0.72
COMPLETENESS
0.80

IMPROVEMENT SUGGESTIONS

  • Replace the generic use-case placeholder with 2-3 concrete task examples (e.g., "claim free game", "check library")
  • Add a minimal end-to-end example call sequence with realistic argument values

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