dungeon-fighter-online-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/dungeon-fighter-online-automation --openclawDungeon Fighter Online Automation via Rube MCP
Automate Dungeon Fighter Online operations through Composio's Dungeon Fighter Online toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/dungeon_fighter_online
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Dungeon Fighter Online connection via
RUBE_MANAGE_CONNECTIONSwith toolkitdungeon_fighter_online - 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 toolkitdungeon_fighter_online - 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: "Dungeon Fighter Online 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 Dungeon Fighter Online task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["dungeon_fighter_online"]
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 Dungeon Fighter Online-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit dungeon_fighter_online |
| 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/dungeon-fighter-online-automation/SKILL.mdView on GitHub Overview
Automate Dungeon Fighter Online tasks using Composio's dungeon_fighter_online toolkit through Rube MCP. The workflow emphasizes discovering current tool schemas with RUBE_SEARCH_TOOLS before running automation and ensuring an ACTIVE connection with RUBE_MANAGE_CONNECTIONS. This approach keeps automations resilient to schema changes.
How This Skill Works
It starts by querying available tools with RUBE_SEARCH_TOOLS using a Dungeon Fighter Online use_case. It then validates the toolkit connection with RUBE_MANAGE_CONNECTIONS to ensure status ACTIVE. Finally, it executes the chosen tool via RUBE_MULTI_EXECUTE_TOOL, including a memory payload and the session_id for continuity.
When to Use It
- Automating a recurring Dungeon Fighter Online task and needing to adapt to new tool schemas by always discovering tools first
- Sequencing multiple DFO actions in a single workflow after establishing a connection
- Running bulk actions or batched operations using multi tool execution
- Troubleshooting tool integration by validating schemas and fields before execution
- Reusing a session across related DFO tasks to maintain context
Quick Start
- Step 1: Add the MCP server https://rube.app/mcp to your client and verify RUBE_SEARCH_TOOLS responds
- Step 2: Run RUBE_SEARCH_TOOLS with use_case Dungeon Fighter Online operations and pick a tool slug from results
- Step 3: Run RUBE_MANAGE_CONNECTIONS to activate the dungeon_fighter_online toolkit, then RUBE_MULTI_EXECUTE_TOOL with memory and a session_id
Best Practices
- Always call RUBE_SEARCH_TOOLS before any execution to fetch current schemas
- Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before running tools
- Use exact field names and types from search results; avoid hardcoding slugs or args
- Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty
- Reuse session IDs within a workflow and generate new ones for new workflows
Example Use Cases
- Automate a daily dungeon run by discovering the appropriate tool slug with RUBE_SEARCH_TOOLS and executing it with empty memory and a session_id
- Chain two tools such as collect_rewards and inventory_update in a single workflow, reusing the same session_id
- Run a batch of tools returned by RUBE_SEARCH_TOOLS for dungeon_fighter_online in one go using RUBE_MULTI_EXECUTE_TOOL
- Troubleshoot integration by fetching tool schemas with RUBE_GET_TOOL_SCHEMAS and validating fields before execution
- Handle pagination in tool listings by iterating through pages until all tools are retrieved
