// the take
A collection of 77 SKILL.md files that teach AI coding agents how to work in specific game engines and genres — Godot, Unity, Unreal, Bevy, pygame, LÖVE, Phaser, three.js, Roblox and more — plus a router skill that loads only the ones relevant to your current project and request. It's aimed at developers who already use an agent like Claude Code or Cursor for game dev and want it to stop hallucinating APIs from the wrong engine version.
The router's engine-detection (project.godot, *.uproject, etc.) plus exclusive-engine/additive-discipline composition is a real solution to context bloat — you don't load all 77 skills, just the 2-4 that match. Each skill is pinned to one specific engine version (Godot 4.7, Unity 6.3 LTS, UE 5.8, Ebitengine v2.10.5), which matters because generic LLM game-dev advice is usually stale by two major versions. The Agent Skills format is genuinely portable — the same SKILL.md loads natively in Claude Code, Cursor, Codex, Gemini CLI, etc., with no per-tool conversion step, and there's a validator script enforcing a format rubric before merge.
It's one maintainer covering 12 engines with meaningfully different APIs and idioms — nobody has production depth in Godot, Unity, Unreal, Bevy and Roblox simultaneously, so skill quality and currency will vary a lot even though the format is consistent. Version pinning is a maintenance liability, not just a strength: Godot and Unity ship frequently, and keeping 77 skills accurate against moving targets is the kind of thing that quietly rots without someone actively tracking every engine's release notes. The validator checks skill format and rubric compliance, not whether the embedded code actually compiles or runs against the pinned engine version — there's no CI that builds a Godot project headless or runs Unity batch mode to catch a skill teaching broken API usage. Routing correctness also isn't actually tested; it depends on the host LLM correctly interpreting the routing table, which is unverifiable from outside and can misfire in early-stage or mixed-engine projects with no project file yet.
We read the README, the directory tree and a key source file in November 2026. Nobody pays to be listed. How we judge →