Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Play Pokemon Red autonomously via PyBoy emulator. The OpenClaw agent IS the player — starts the emulator server, sees screenshots, reads game state from RAM, and makes decisions via HTTP API. Use when an agent wants to play Pokemon Red, battle, explore, grind levels, or compete with other agents. Requires Python 3.10+, pyboy, and a legally obtained Pokemon Red ROM.
Play Pokemon Red autonomously via PyBoy emulator. The OpenClaw agent IS the player — starts the emulator server, sees screenshots, reads game state from RAM, and makes decisions via HTTP API. Use when an agent wants to play Pokemon Red, battle, explore, grind levels, or compete with other agents. Requires Python 3.10+, pyboy, and a legally obtained Pokemon Red ROM.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
You play Pokemon Red directly. No middleman script. You start the emulator server, hit its HTTP API for screenshots and state, look at the screen, decide what to do, and send commands back.
Clone the repo and install dependencies: git clone https://github.com/drbarq/Pokemon-OpenClaw.git cd Pokemon-OpenClaw pip install pyboy pillow numpy fastapi uvicorn requests # Place your legally obtained ROM at ./PokemonRed.gb Set POKEMON_DIR to wherever you cloned the repo (default: ~/Code/pokemon-openclaw).
# Start emulator server (background process) cd $POKEMON_DIR && python scripts/emulator_server.py --save ready --port 3456
Every turn, do these in order:
curl -s http://localhost:3456/api/state curl -s http://localhost:3456/api/screenshot -o /tmp/pokemon_current.png Then use the image tool to look at the screenshot. Always look before acting.
Use navigate for travel — it BLOCKS until you arrive, hit a battle, or get stuck: curl -s -X POST http://localhost:3456/api/navigate \ -H 'Content-Type: application/json' \ -d '{"destination": "Viridian City"}' Navigate returns one of: "status": "arrived" — you're there! Continue quest. "status": "battle" — wild encounter interrupted. Fight it, then navigate again. "status": "stuck" — couldn't reach destination. Try manual buttons or different route. "status": "error" — unknown destination or no path. Check destinations list. The response always includes full game state, so you know exactly where you are. Important: Navigate blocks — set a long timeout (60-120s) on the curl call. Check available destinations first: curl -s http://localhost:3456/api/destinations Check which maps have pathfinding data: curl -s http://localhost:3456/api/maps Fall back to manual buttons only when: Navigate returns "stuck" or "error" You're inside a building doing specific interactions You're in dialogue or a menu
# Move / interact curl -s -X POST http://localhost:3456/api/press \ -H 'Content-Type: application/json' \ -d '{"buttons": ["up","up","a"], "reasoning": "Walking to door"}' Valid buttons: up, down, left, right, a, b, start, select. Send 1-5 per turn.
Fight: Press a to open fight menu, a again for FIGHT, navigate to move, a to confirm, then mash a through animations Run: Press a, then down, right, a to select RUN, mash a through text Check state after — if still in_battle, go again
curl -s http://localhost:3456/api/quest # Current objective curl -s -X POST http://localhost:3456/api/quest/complete \ -H 'Content-Type: application/json' \ -d '{"lesson": "Door is at x=12"}' # Advance step + save lesson
curl -s -X POST http://localhost:3456/api/command \ -H 'Content-Type: application/json' \ -d '{"command": "save", "name": "checkpoint_viridian"}'
EndpointMethodPurpose/api/stateGETGame state from RAM (position, party, badges, battle)/api/screenshotGETPNG screenshot of game screen/api/navigatePOSTPathfind to named destination/api/destinationsGETList all navigation destinations/api/mapsGETWhich maps have pathfinding data/api/pressPOSTSend button presses/api/questGETCurrent quest and step/api/quest/completePOSTMark step done, optionally save a lesson/api/knowledgeGETAll lessons learned/api/knowledge/lessonPOSTAdd a new lesson/api/commandPOSTSave/load/speed commands
Navigate first. For any travel, use /api/navigate. It blocks until arrival or battle — no polling needed. Handle battles immediately. If navigate returns "status": "battle", fight (mash A), then navigate again to the same destination. Check quest. Always know your current objective. Don't wander. HP management. Below 30% → consider healing. Below 15% → definitely heal. Navigate to nearest pokecenter. Ignore text_active. The text detection flag is broken (always true). Don't spam B to dismiss phantom text. Save often. Every 10 turns or after any milestone.
A sub-agent session should: Start emulator server (if not already running) Check quest status and destinations Play 20-50 turns (navigate + manual as needed) Save state before exiting Report progress (location, level, quest step, any highlights) Keep notes in /tmp/pokemon_notepad.txt for continuity within a session.
See references/game_instructions.md for Pokemon Red basics: movement, buildings, doors, battles, type matchups, healing, and the quest system.
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.