Menu
Explain maps, variants, and curriculum ordering used by a training command or recipe. Use when asked to audit a recipe configuration.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when designing or repairing a CoGames-style game and the main risk is that the rules, map, roles, or play loop do not yet match the real game or prompt closely enough.
Use when creating a new mettagrid game from scratch and you need the design-first workflow that writes the rules contract, checks engine fit, and hands a clean build plan to `cg.game.build-game`.
Use when a CoGames-style game already works visually and mechanically and now needs to be split into a composable variant registry, dependency tree, and optional curriculum tree without regressing the default game.
Use when implementing or overhauling a CoGames-style game once the target contract is known, including scaffold, registration, mechanics, assets, and variant factoring.
Use when designing or repairing a CoGames-style game and the main risk is that the rules, map, roles, or play loop do not yet match the real game or prompt closely enough.
Use when a CoGames-style game is mechanically working but still has missing, placeholder, wrongly themed, or non-namespaced art, terrain, or atlas entries.
| name | recipe-curriculum-audit |
| description | Explain maps, variants, and curriculum ordering used by a training command or recipe. Use when asked to audit a recipe configuration. |
./tools/run.py command.