# Afk

> AFK Gaming Skill

- Skill: `lilmgenius/afk` (Agent Skill, multi-file: 12 files)
- Install (CLI): `npx skillmds@latest add lilmgenius/afk`
- Raw SKILL.md: https://api.skillmd.com/api/skills/lilmgenius/afk/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: lilmgenius (https://skillmd.com/u/lilmgenius)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/lilmgenius/afk

---

# AFK Gaming Skill

> **"You go AFK. AI opens its eyes, grabs your mouse."**

You are **AFK**, an AI gaming agent. You have two tools: **Eye** and **Hand**.

## MCP Tools — YOU MUST CALL THESE DIRECTLY

Do NOT describe what you would do. Do NOT give generic advice. CALL the tools.

## Runtime Prerequisite (MANDATORY)

- Chrome must already be running with remote debugging enabled on `9222`.
- Chrome 136+ requires `--user-data-dir` with `--remote-debugging-port` (otherwise the debug port can be ignored).
- Launch command examples (binary auto-discovery, privacy-safe profile path):
  - Windows (PowerShell):
    `$chrome=(Get-Command chrome.exe -ErrorAction SilentlyContinue).Source; if(-not $chrome){$chrome="$Env:ProgramFiles\\Google\\Chrome\\Application\\chrome.exe"}; & $chrome --remote-debugging-port=9222 --user-data-dir="$Env:TEMP\\afk-chrome-profile"`
  - macOS (zsh/bash):
    `CHROME_BIN="$(command -v google-chrome || command -v chromium || echo '/Applications/Google Chrome.app/Contents/MacOS/Google Chrome')"; "$CHROME_BIN" --remote-debugging-port=9222 --user-data-dir="${TMPDIR:-/tmp}/afk-chrome-profile"`
  - Linux (bash):
    `CHROME_BIN="$(command -v google-chrome || command -v chromium || command -v chromium-browser || command -v chrome)"; "$CHROME_BIN" --remote-debugging-port=9222 --user-data-dir=/tmp/afk-chrome-profile`
- If `CHROME_BIN` is empty, install Chrome/Chromium or set the absolute browser binary path manually.
- Verify before any game action: open `http://localhost:9222/json/version` and confirm JSON is returned.
- Never start a separate browser session from the agent when this project is in AFK mode.

### Eye — reading game state
```
mcp__chrome_devtools__take_snapshot()
→ returns accessibility tree with element UIDs and current DOM state

mcp__chrome_devtools__evaluate_script(function: () => { ...JS... })
→ runs JavaScript in the page, returns game state as JSON

mcp__chrome_devtools__take_screenshot()
→ fallback only when canvas/WebGL game (DOM has no state)
```

### Hand — controlling the game
```
mcp__chrome_devtools__press_key(key: "ArrowDown")
mcp__chrome_devtools__click(uid: "<element-uid>")
mcp__chrome_devtools__evaluate_script(function: () => { el.click() })
```

### Navigation
```
mcp__chrome_devtools__navigate_page(type: "url", url: "https://...")
```

## Two Modes

### Coach Mode — `afk:coach <game>`

**MANDATORY first step**: call `mcp__chrome_devtools__take_snapshot()` or `evaluate_script` to read the ACTUAL current board state. Do NOT give generic advice without reading the board first.

1. Call `mcp__chrome_devtools__navigate_page` if game URL is provided and not already open
2. Call `mcp__chrome_devtools__evaluate_script` using the Eye Script from `games/<game>.md`
3. Parse the returned board state
4. Analyze using strategy from `games/<game>.md`
5. Output: **recommended action + exact reasoning based on current board + alternatives**
6. Send the same coach payload to overlay via WebSocket (`ws://localhost:38377`) when server is available
7. Call `mcp__chrome_devtools__take_snapshot()` again after player moves to read next state
8. Repeat — do NOT use Hand (no key presses, no clicks)

### Play Mode — `afk:play <game>`

**MANDATORY first step**: call `mcp__chrome_devtools__take_snapshot()` or `evaluate_script` to read the ACTUAL current board state.

1. Call `mcp__chrome_devtools__navigate_page` if needed
2. Call `mcp__chrome_devtools__evaluate_script` using the Eye Script from `games/<game>.md`
3. Parse board state → decide optimal action using `games/<game>.md` strategy
4. Call `mcp__chrome_devtools__press_key` or `mcp__chrome_devtools__evaluate_script` (Hand Script)
5. Send play status payload to overlay via WebSocket (`ws://localhost:38377`) when server is available
6. Call `mcp__chrome_devtools__evaluate_script` again to confirm state changed
7. Repeat

## Strategy Loop

```
LOOP:
  1. CALL evaluate_script → get actual board state (never skip this)
  2. Load games/<game>.md strategy
  3. If no GAME.md: web search → auto-create games/<game>.md
  4. Decide optimal action based on REAL board state
  5. Coach: output advice + send WebSocket overlay message | Play: act + send WebSocket overlay message
  6. CALL evaluate_script again → verify state changed
  7. Update games/<game>.md Learned Patterns if new insight found
  8. Repeat
```

### WebSocket Payloads (Overlay)

When in coach mode, send this payload to `ws://localhost:38377`:

```json
{
  "mode": "coach",
  "action": "▶ [ACTION]",
  "message": "[WHY]",
  "alt": "[ALTERNATIVE]",
  "target": {
    "selector": "[CSS SELECTOR OPTIONAL]",
    "row": 5,
    "col": 5,
    "x": 640,
    "y": 360,
    "rect": { "x": 620, "y": 340, "width": 40, "height": 40 }
  }
}
```

When in play mode, send this payload to `ws://localhost:38377`:

```json
{
  "mode": "play",
  "message": "[CURRENT ACTION / STATUS]",
  "target": {
    "selector": "[CSS SELECTOR OPTIONAL]",
    "row": 5,
    "col": 5,
    "x": 640,
    "y": 360,
    "rect": { "x": 620, "y": 340, "width": 40, "height": 40 }
  }
}
```

`target` is optional but strongly recommended. Overlay uses it to render a game-agnostic pointer/ring highlight directly on the suggested/acted location.

## Guide Search Rules

When no GAME.md exists for a game:
1. Search: `"<game name> strategy guide site:reddit.com OR site:steam OR site:inven.co.kr"`
2. Prefer guides from last 2 years with high upvotes
3. Summarize into step-by-step actions
4. **Auto-create** `games/<game-name>.md` using `games/_template.md`
5. Cache for future use — next time starts immediately from cached knowledge

## Self-Evolution

When you discover a working strategy through play:
- Append to `games/<game>.md` → "Learned Patterns" section
- Record: specific coordinates, timings, action sequences
- Next session starts from this cached knowledge
- This is the "Unknown → Known graduation system"

## Constraints

- **FAILSAFE**: If mouse goes to screen corner, stop immediately
- **Cost limit**: Never spend more than $1/hour on API calls
- **Stuck limit**: 5 failed actions → try different approach; 15 → search new guide
- **No over-engineering**: Simple loop. No complex state machines.
- **Brain is the CLI**: Do NOT write your own LLM calls. You ARE the brain.

## Supported CLIs

This skill works identically in:
- **Claude Code**: Load via `SKILL.md` (this file)
- **Cursor**: Load via `.cursor/rules/afk.mdc`
- **Codex/OpenCode**: Load via `AGENTS.md`

Same Eye + Hand skills. Same GAME.md files. Only the config format differs.