Awesome Gamedev Agent Skills: A 74-Skill Pack for Godot, Unity and More, and How to Install Only What You Need

If you want agent skills for Godot and Unity game development that work in more than one coding agent, the community repo gamedev-skills/awesome-gamedev-agent-skills is one of the broadest options available. According to its README, it bundles 74 game-dev skills plus a router across 10 engines. You can also install the router with a single engine bundle instead of the whole catalog. Godot gets the most coverage, with 16 skills. Unity gets 8.

This Lab Note reports from the repo page and README only. It covers what the pack contains, how the router picks skills, and how to install only the part you need. It also compares the pack with Unity's official agent plugins.

What is the awesome-gamedev-agent-skills pack?

The repo description calls it "74 game-dev skills for AI coding agents." The skills are portable SKILL.md files, which the repo calls "the format Anthropic launched as Claude Skills." The README describes an Agent Skill as a small capability file that an agent loads only when it needs it.

The catalog covers ten engines and frameworks:

• Godot, Unity and Unreal
• Phaser, PixiJS and three.js (browser)
• Bevy, pygame, LÖVE and Roblox

The README says the same files load natively in Claude Code, Cursor, Windsurf, Cline, Codex, Gemini CLI, GitHub Copilot and Kiro. It also links a longer compatibility list. The license is Apache-2.0. When the repo page was read, it showed about 1.5k stars, 130 forks and 109 commits.

This is a community project. Godot, Unity, Epic and the other engine makers did not publish it, and the repo does not claim any endorsement from them.

How does the router decide which skills to load?

The router is the main design choice. According to the README's "How the router picks skills" section, it does three things on each request:

1. Detects the engine from project files. A project.godot file means Godot, and a *.uproject file means Unreal. If it cannot tell, the README says it asks.
2. Reads the request for a task. That can be a concept such as AI, shaders or saving, a genre such as platformer or roguelike, or a shipping step such as a game jam or Steam.
3. Loads only the matching skills, in order: engine basics first, then the concept, then any genre skill. The README says it re-routes when you switch to a new task.

The README also says engine selection is exclusive, while discipline, genre and workflow skills are additive. In other words, only one engine's skills apply at a time, and topic skills stack on top. The full detection signals and routing table live in router/SKILL.md.

The README gives worked examples:

Analysis. Loading only the matching skills keeps the agent's context smaller than pasting one large rules file into every session. However, these routing examples are the maker's own claims. None of the sources show independent checks of how often the router picks the right skills in a real, messy project. Treat the table as intended behaviour, not measured accuracy.

What do the Godot and Unity skills cover?

Godot: 16 skills, pinned to Godot 4.7

According to the README catalog, the Godot group covers:

• GDScript, nodes and scenes, signals and groups
• 2D movement with CharacterBody2D
• TileMapLayer and TileSet
• Physics, UI with Control nodes, animation and shaders
• 3D essentials, resources and audio
• Multiplayer and export
• C# in Godot
• Headless GDScript testing for CI

Unity: 8 skills, pinned to Unity 6.3 LTS (6000.3)

The README lists C# scripting, the Input System, physics, animation, ScriptableObjects, 2D Tilemap and NavMesh among the Unity skills. Check the browsable catalog for the full current list before you rely on a specific area.

Analysis. Godot has twice as many skills as Unity. A Unity developer working on areas such as UI Toolkit, Addressables or rendering pipelines should confirm that a matching skill exists rather than assume the pack covers it.

Version pinning cuts both ways

The README says every skill is written from primary docs, pinned to a stated engine release, and checked by a validator script. The baselines and upgrade policy are in VERSION-SUPPORT.md.

Pinning helps when your project matches the baseline, because the agent gets guidance for the APIs you actually have. If your project runs an older Godot 4.x or an earlier Unity release, the skills may steer the agent toward APIs or patterns that differ from your version. The validator checks the skill files themselves. It does not check them against your project.

How do you install only the engine you use?

The README offers three routes.

Option 1: the skills CLI (any supported agent)

The skills CLI detects your coding agent and installs the router plus all 74 skills:

npx skills add gamedev-skills/awesome-gamedev-agent-skills

The README lists these flags:

• --list previews what will be installed
• -g installs for every project
• -a <agent> targets one tool, for example -a cursor, -a claude-code or -a gemini-cli

Option 2: the full Claude Code plugin

The repo also works as a Claude Code plugin marketplace:

claude plugin marketplace add gamedev-skills/awesome-gamedev-agent-skills
claude plugin install gamedev@awesome-gamedev-agent-skills

Option 3: router plus one engine (Claude Code)

For single-engine projects, the README shows a smaller bundle:

claude plugin install router@awesome-gamedev-agent-skills
claude plugin install godot@awesome-gamedev-agent-skills

Swap godot for unity, unreal, web-engines or other-engines. The README presents these bundles as Claude Code plugins. For other agents, or to copy files by hand, it points to docs/INSTALLATION.md for per-tool paths.

Analysis. For a solo developer on one engine, the router plus one engine bundle is the sensible default. Agents read skill descriptions to decide what to load, so skipping nine engines you never touch means less noise. Run --list or read the installation doc first. That way you know which folders the files land in and can remove them cleanly later.

What else does it include beyond engine code?

The README describes an art-direction and asset workflow. In its words, the workflow "locks a visual target, builds families" of assets, normalizes outputs deterministically, and checks them inside the game. Its example request, "make a cohesive pixel-art player, enemies, and tiles," loads create-game-assets plus the importer for the detected engine. Related tools appear in our sprites coverage.

Shipping is covered too. The README's example "publish my game on itch with butler" loads an itch-publish skill, and the router lists game jams and Steam as shipping steps.

Analysis. The README does not show sample output from the asset workflow, so the sources say nothing about its quality. Treat it as a stated feature. Skills are only instructions. Any image generation still depends on whatever tools your agent can call.

How does it compare with Unity's official plugins?

Unity has published its own agent plugins, covered in earlier Lab Notes: the Unity plugin for Codex with 31 skills and the Unity Claude Code plugin with 29 skills, which needs extra setup for live editor control.

Analysis. These tools do different jobs. The community pack is portable written guidance that works across agents and engines. A vendor plugin is narrower but may connect to the editor itself. A Unity developer could use both, but should check for overlapping instructions on the same topic.

Godot has a similar split. Skills tell an agent how to write GDScript. They do not let it run or inspect your game. For that, see our test plan for Open Godot MCP, which covers the editor and playtest control that a skill file cannot provide.

Verdict: who should install it?

• Godot developers get the most from it: 16 skills covering most of the engine, usable in whichever agent you prefer.
• Unity developers get 8 skills. Look at Unity's official plugins first, since they offer more Unity-specific skills.
• Phaser, three.js, PixiJS, Bevy, pygame and LÖVE developers get a rare multi-engine option, since engine vendors mostly ignore these frameworks. See more in browser games.
• Skip it if you only need help with one narrow task and already keep a good project rules file. The pack adds little in that case.

The sources make the limits clear. This is a single community repo. Its routing and quality claims come from the maker and have no independent benchmarks. Its baselines are tied to specific engine versions. Skills shape what an agent writes, but you still need to review the code it produces.

For more agent tooling news, browse coding agents or the latest Lab Notes.