
Content Audit
Compares planned game content counts in design docs against what's implemented
- Repository
- Donchitos/Claude-Code-Game-Studios
- Stars
- 32,965
- Licence
- MIT
- Files
- 1 file
What it does
This skill makes an AI agent check a game project's design documents (GDDs) for how many enemies, items, levels and similar content are planned, then compare that against what has actually been built. It reads the project's systems index and design files, follows strict rules to report 'NOT ASSESSED - NO DATA' instead of guessing when inputs are missing, and produces a gap summary, optionally saved to a file. It is written for a game-studio workflow that uses other skills such as /map-systems and /design-system.
Great for
- Game developers tracking planned versus built content during production
- Producers or leads who want a quick gap report on a design-documented project
- Teams already using the Claude Code Game Studios template with its design/gdd folder structure
Skip it if
- Projects without a design/gdd/systems-index.md file: the skill is designed to stop and report no data rather than produce a useful report
- Non-game software or projects that do not keep numbered content counts in design documents, since the skill looks for game-specific nouns
- Anyone expecting a verified build check: the SKILL.md only describes reading documents and does not show how implementation is measured
Try asking
- “Run a full content audit across all systems in this game project”
- “Audit only the combat system's planned versus built content”
- “Give me a summary table of content gaps without writing a file”
Install in 3 steps
- 1
Download the skill
The ZIP contains the 1 original files, the MIT licence and an attribution note.
content-audit.zip - 2
Add it to your agent
Claude Code (all projects)
mkdir -p ~/.claude/skills && unzip content-audit.zip -d ~/.claude/skills/Claude Code / Agent SDK (this project only)
mkdir -p .claude/skills && unzip content-audit.zip -d .claude/skills/Claude apps (web/desktop): Settings → Capabilities → Skills → Upload skill, and choose the ZIP.
- 3
Ask for the task
No special command needed — the agent reads the skill's description and loads it when your request matches. Try one of the prompts above.
Get better results
- Run /map-systems and /design-system first so the required design inputs exist; otherwise the audit will report NOT ASSESSED
- Use the --summary argument when you only want the table and do not want a file written
- Keep GDDs with a '## Summary' section, since missing summaries are handled by full reads and slow the audit
What's inside
- SKILL.md
Redistributed unmodified from Donchitos/Claude-Code-Game-Studios under the MIT licence. The assessment was drafted with AI from the skill's files on 2026-10-29. Skills can instruct your agent to run code — read SKILL.md and any scripts before installing.