How to use the Game Development Matrix agent skill

What the Game Development Matrix skill makes the agent do

The skill gives the agent a map of game development tools grouped by capability: game engines (Godot, pygame, Arcade, Panda3D and Ursina), 2D and 3D art tools, sound and music tools, AI image and audio generators, agent-driven play testing, building game packages, and uploading builds to stores such as Steam and itch.io.

It checks which of these tools are installed or which API keys are set, then recommends options based on your requirements, output quality, offline needs, credential state, cost and provider notes. For paid or metered services it asks you before using them. The skill organises the choice of tools for the agent; it does not create a game by itself.

• Covers engine, 2D and 3D assets, audio, notation, AI-generated assets, playtesting, packaging, store publishing and telemetry.
• Runs a preflight availability report before recommending providers.
• Does not cover Unity or Unreal projects, according to the skill file.

Install the skill and its cli-hub dependency

The skill requires cli-hub, which provides the matrix install and preflight commands. Python is also needed for the preflight script and for Python-based providers. Once cli-hub is available, install the matrix with the command below.

To add the skill to your agent, download the skill ZIP from this page and unzip it into one of two places. For a personal setup, use ~/.claude/skills/. For a single project, use the .claude/skills/ folder inside that project. You can also upload the ZIP in the Claude apps under Settings, then Capabilities, then Skills.

• Personal install: unzip into ~/.claude/skills/
• Project install: unzip into .claude/skills/ inside your project
• Claude apps: Settings, then Capabilities, then Skills, then upload the ZIP

Run the preflight check

Preflight tells the agent which tools and credentials are available on your machine. Run it before starting work so the agent knows what it can use without asking. The skill's own guidance is to treat the preflight output as an availability report, not as a choice of provider.

The preflight checks for optional tools including godot, blender, aseprite, butler, steamcmd, ffmpeg and pyinstaller. It also checks for environment variables such as STEAM_USERNAME, ITCH_API_KEY, OPENAI_API_KEY, REPLICATE_API_TOKEN and SENTRY_DSN, reporting only whether each is set or unset. A missing tool is not an error; the agent will work with what is present.

• Use --json for machine-readable output.
• Use the info command to read the matrix details for this skill.
• If you run an older cli-hub version, the skill file includes a manual preflight block instead.

Trigger the skill with natural requests

You do not need a special command to use the skill. Describe your game task in plain language and mention the stage you are at, such as choosing an engine, making sprites, exporting a build or publishing. The agent should load the skill when the request matches its scope.

Be specific about your constraints. Saying whether you need offline tools, whether you have a budget, and whether you already have store accounts helps the agent choose between free local tools and paid services. If you want the agent to check your setup first, ask for a preflight.

• Which engine suits a small 2D jam game with an offline workflow, and which tools do I already have installed?
• Run a preflight for my game tools and tell me what is missing for a Steam release.
• Suggest free tools for sprites and sound effects, and don't use any paid API without asking me.
• Package my pygame project for Windows and tell me what export tool is available.

Ask the agent for example workflows

The skill describes several recipes that combine capabilities. A game jam workflow typically uses an engine, 2D art, audio, packaging and optionally store publishing. An AI-assisted short adds generated art to a simple engine loop. A release workflow adds store upload and crash reporting. Ask for the recipe by describing your goal, and the agent will pick the relevant capabilities.

• Game jam: engine, 2D art, audio, then build packaging, with store upload optional
• AI-generated art with a simple engine loop
• Steam release with crash reporting through telemetry tools
• Agent playtesting of an existing game with telemetry

Safety notes: scripts, network and credentials

This skill runs scripts and uses the network. The preflight step runs commands and reads environment variables, and the providers it routes to may call online services. Review what the agent is about to run before you approve it, especially any command that touches your store account.

Store uploads need account logins and, in the case of Steam, a fee. The skill file's example cites a one-time $100 Steamworks fee and recommends a dedicated build account to limit credential risk. The skill asks you before using paid or metered services, so keep that confirmation step in place.

• Use a dedicated build account for store uploads where possible.
• Only set API keys you are prepared to let the agent use.
• Metered services may charge per use, so check your provider account before large jobs.