The Other Half of Game Development Scores 9.0 and Gets One Download

When people say "game development" in an agent-skills context, they mean code generation. But four skills in our directory cover the other half of the job — levels, characters, engine loops, builds — and they score as well as the programming half while installing a tenth as often.

Four skills, four non-code problems

level-design — 9.0 — covers the blockout-to-playable workflow: turning a whitebox into a level that teaches mechanics, pacing difficulty, and reading player metrics to find where people actually quit. roblox-characters — 9.0 — builds respawn-safe character systems around the Roblox APIs every experienced Roblox developer knows bite newcomers: CharacterAdded, CharacterRemoving, and the duplication issues around respawning. love2d-core — 9.0 — structures and debugs LÖVE games in Lua: the love.load/update/draw loop, delta-time correctness, and state management. unity-build-pipeline — 9.0 — handles the shipping side: Unity 6.3 LTS build settings, player and quality settings, and scene configuration.

Only one of those is really about writing code. Level design is spatial reasoning and pacing. Roblox characters is API semantics and failure modes. The LÖVE skill is architecture. The Unity skill is build configuration — the classic "works on my machine" graveyard. These are exactly the kinds of knowledge that senior game developers carry and juniors lack, and exactly the kinds that compress well into a skill: procedural, checkable, with a right answer more often than not.

The scores: content is the differentiator

The dimension lines are unusually even. Content scores run 9.5 for the level, Roblox, and LÖVE skills — the highest content marks in our games category — reflecting reference material that is specific enough to act on: actual pacing curves, actual respawn-safe patterns, actual delta-time bugs. Security is 10.0 for level-design and love2d-core, 9.5 for the other two. Engineering sits at 8.0 to 8.5, workflow at 8.5 to 8.8 — good, not exceptional, because these skills teach more than they execute.

Compare that to the code-generation side of game tooling, which we have covered before: the pattern there is high workflow, thinner content. Design knowledge is the scarce resource in this set, and the scores correctly identify where it lives.

One download each

Here is the uncomfortable number: 1, 1, 2, and 1 installs. The best-written game-design reference in the directory moves less than a median marketing skill moves in a day.

The likely explanation is a mismatch between who writes skills and who needs this one. Skill authors skew toward backend, tooling, and marketing — people who automate their own work. Game designers are a smaller population, less embedded in the agent-tooling ecosystem, and historically underserved by it. Roblox alone has millions of creators, but almost none of them are browsing skill directories yet. The demand is real; the channel does not exist.

There is also a discovery problem inside the skill ecosystem itself: someone asking an agent for "help with my Roblox game" usually wants a script, not a character-system architecture review. The trigger descriptions do their job — they name the phrasings — but the mental model of the asker has to expand before the routing gets tested at scale.

The bet

The scores say these four skills are among the highest-quality material in the games category. The install counts say nobody knows. That combination is usually an early signal, not a dead end: quality-first, adoption-later is the shape every vertical took right before it became crowded. If game-design skills ever get distribution — a Roblox creator community, a game-jam scene, a studio onboarding flow — these are the artifacts it will grow around. The code-generation half of game development is already a commodity. The half that scores 9.5 on content is still sitting there with one download.