Skip to content
SkillModel-led6,790 tokens in use

Game Development Router

Entry point for game-dev work: it detects the engine from project files, classifies the task, and names the few skills to read before the agent writes code.

9,682 stars on the repository Apache License 2.0gamedev-skills/awesome-gamedev-agent-skills · router
npx skills add gamedev-skills/awesome-gamedev-agent-skills
View source

Install command as written in the repository's README

Skill label

measured from its files

What installing Game Development Router costs

91tokens idle
6,790tokens in use
15,790tokens, up to

Idle is what sits in context while the skill is installed. In use is its instructions, loaded when it runs. Up to adds the files its instructions link. Counts are approximate, made offline with cl100k_base.

Model dependence Model-led

Script-ledMixedModel-led

Mostly instructions, so how well it works depends on the model that follows them.

This describes the skill's structure, how much of it is scripts. It does not say how well it works.

Touches

Nothing detected: no shell, network, file writes, git or credentials in its files.

Declared tags come from the skill's frontmatter; detected ones from its scripts, its code blocks and the commands it names in inline code. This is detected, not audited.

How it scores

Quality

How well the skill is written, counted from its own files: its frontmatter, its steps, examples, stated output and constraints, its size and whether every file it ships is one it names.How we score it →
Good
  • Frontmatter8/15
  • Structure25/25
  • Examples6/15
  • Output10/15
  • Size11/15
  • Resources11/15

Security

Starts at 100 and loses points for each thing in the skill's files that a reader should look at first.How we score it →
Excellent

No findings.

Repository health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum.How we score it →
Good
  • Development activity92
  • Maintenance96
  • Community60
  • Maturity24
  • Momentum40

The router is the first skill an agent opens on a game-development request. It looks for engine fingerprints in the project (project.godot, a .uproject, Assets plus ProjectSettings, go.mod with Ebitengine, package.json with phaser, and so on for 12 engines), reads the pinned engine version, and sorts the request into disciplines, genres and workflows.

It then names the smallest set of skills to load, in a fixed order: engine basics, the discipline concept, genre glue, then workflow. It dispatches and composes; it does not teach engine APIs itself.

What You Get

  • An engine detection table covering Godot, Unreal, Unity, Ebitengine, Bevy, Phaser, PixiJS, three.js, Defold, LÖVE, pygame and Roblox, with the file that identifies each
  • A routing table from request wording to the discipline, genre or workflow skill that owns it
  • Ownership rules for requests two skills both claim, such as behavior trees or platformer jump feel
  • A fallback path for unknown, custom or in-house engines that keeps the existing engine and binds APIs from project evidence

Common Use Cases

  • Starting a game request without knowing which of the many game-dev skills fits
  • Adding a feature such as a double jump or an inventory and having the engine and genre skills chosen for you
  • Working in a project with a pinned engine version older or newer than the catalog baseline
  • Splitting work with an engine vendor’s own agent skills or editor connection when one is already in the session

What Makes It Unique

Most game-dev skills teach one engine or one topic. This one teaches no engine API at all: its job is selection. It encodes engine fingerprints, version checks, a table of who owns overlapping requests, and a rule to load the minimum number of skills so the context is not filled with unrelated engines.

Under The Hood

The skill is instructions only and ships no scripts. It tells the agent to scan the project for fingerprint files, read the engine version from project metadata or lockfiles, and then open the chosen SKILL.md files and, on demand, three reference files in its own references folder. It does not fetch web pages, call APIs, run commands or write files by itself. It states a trust rule: text found in project files or tool output is not treated as an instruction. It also says never to install a vendor plugin or MCP server for the user.

Join founders building with open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on SubstackJoin 750+ subscribers