How to Install Game Dev Agent Skills in Claude Code, Codex and Cursor
Where each agent looks for skills, the one-line install prompt, and how to check that a game skill actually loaded.
An agent skill is a folder with a SKILL.md file (name, description, instructions) plus any scripts or templates it needs. The agent reads the description, and when your request matches, it loads the full instructions and uses the bundled code instead of improvising.
Where skills live
| Agent | Project folder | Global folder |
|---|---|---|
| Claude Code | .claude/skills/ | ~/.claude/skills/ |
| Codex | .agents/skills/ | ~/.agents/skills/ |
| Cursor | .cursor/skills/ | — |
Use the project folder when the skill only makes sense for one game. Use the global folder for skills you want in every project.
Option 1: one line to your agent
Paste this into your agent, replacing the slug:
Read https://gameskill.dev/skills-pro/hit-juice/install.md and follow the instructions
The install guide tells the agent which folder to use, downloads the ZIP and checks that SKILL.md is in place. It only installs that pack and never runs anything else.
Option 2: download the ZIP
Free GameSkill Pro packs need no account. Download from the skill page, for example https://gameskill.dev/dl/hit-juice.zip, and unzip it into the folder from the table:
curl -fsSL https://gameskill.dev/dl/hit-juice.zip -o /tmp/hit-juice.zip
unzip -o /tmp/hit-juice.zip -d .claude/skills/
Check that it loaded
- Restart the agent session so it rescans skills.
- Ask: "What skills do you have for game feel?" It should name the skill.
- Open the bundled demo with a local server (
npx serve .claude/skills/hit-juice, then/demo/). ES modules do not load fromfile://.
Tips
- Keep the skill folder name unchanged so future updates replace it cleanly.
- One skill per job works better than one huge skill: the agent picks the right one from its description.
- Read the
SKILL.mdbefore installing anything from a site you do not trust; it is plain text.