deep-analysis
Investigate a game from raw logs, trace bugs to source code, and file detailed issues. Use for deeper debugging than export-only analysis.
npx skills add majiayu000/claude-skill-registry --skill deep-analysis-gregorstocks-mage-bench --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Deep Analysis Deep analysis of game logs — reads all raw log files, traces bugs to source code, and files detailed issues. For quick triage, use `/fast-analysis` instead. ## Workflow ### Step 1: Select the game Determine which game to analyze: - If the user specified a game ID (e.g. `game_20260211_080409`), use that. - If the user said "most recent" or similar, find the latest: ```bash uv run python scripts/list_recent_games.py ``` - If the user mentioned a config name (e.g. "round-robin-commander", "jumpstart-dumb", "modern-staller"), use the corresponding symlink: ```bash uv run python scripts/list_recent_games.py --config {config} ``` where `{config}` might be `round-robin-commander`, `jumpstart-dumb`, `modern-staller`, etc. Check what symlinks exist with `--symlinks`. - **If no game specified at all**, find the most recent unanalyzed game: ```bash uv run python scripts/analysis/find_unanalyzed.py --type deep --count 1 ``` Set `GAME_DIR=~/.mage-bench/logs/{game_id}`. If the full log directory doesn't exist but the game export exists in `website/public/games/` (`.json` or `.json.gz`), tell the user the full logs aren't available and offer to run a fast analysis from the export
- Workflow
- Step 1: Select the game
- Step 2: Bootstrap from gz (if available)
- Step 3: Read game metadata
- Step 4: Check existing issues
- Step 5: Analyze log files in parallel
- Step 6: Cross-reference findings
- Step 7: Distinguish code bugs from model issues
- Step 8: Trace bugs to source code
- Step 9: Create issue files
- Step 10: Focus on a single game
- Step 11: Present summary
- Step 12: Create reusable analysis scripts
- Step 13: Document investigation tricks
uv run python scripts/list_recent_games.py
uv run python scripts/list_recent_games.py --config {config}
uv run python scripts/analysis/find_unanalyzed.py --type deep --count 1
uv run python scripts/game_gz_bootstrap.py ${GAME_ID}
uv run python scripts/query_issues.py
git log --oneline --since="YYYY-MM-DD" origin/master # date of the gameWhat does the deep-analysis skill do?
Investigate a game from raw logs, trace bugs to source code, and file detailed issues. Use for deeper debugging than export-only analysis.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill deep-analysis-gregorstocks-mage-bench --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.
