# Asset Audit

Audit assets against naming conventions, file size budgets, format standards.

- Repository: https://github.com/Donchitos/Claude-Code-Game-Studios (32144 stars)
- Category: Engineering
- License: MIT
- Last updated: 2026-10-19
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add Donchitos/Claude-Code-Game-Studios --skill asset-audit -g -a claude-code -y`
Codex: `npx skills add Donchitos/Claude-Code-Game-Studios --skill asset-audit -g -a codex -y`
Cursor: `npx skills add Donchitos/Claude-Code-Game-Studios --skill asset-audit -g -a cursor -y`
Gemini CLI: `npx skills add Donchitos/Claude-Code-Game-Studios --skill asset-audit -g -a gemini-cli -y`

## Description

Audit assets against naming conventions, file size budgets, format standards. Finds orphaned assets, missing references.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Asset Audit

## Measuring file sizes and formats requires Bash

This skill's report asks for **file sizes against budgets**, **texture dimensions**
(power-of-two), **audio sample rates**, and **last-modified times** for orphan
detection. None of those are obtainable from `Read`/`Glob`/`Grep`, they need
`stat` or a binary header read, so the read-only measuring commands (`stat`,
`file`, `od`, `wc`, `du`) are pre-approved above; list files with Glob. Anything
else asks first.

**If you cannot take a measurement, the cell is `NOT ASSESSED`, never an
estimate.** A size budget table filled from guesses is worse than an empty one:
it looks like evidence. This is a live fabrication vector even on a project full
of real assets: if the template demands tables of numbers the tool allowlist
cannot produce, the only way to complete it is to invent them.

---

## Insufficient input, check this before producing any report

**If the inputs this skill needs do not exist, the answer is "could not run", not a filled-in report.** Check first, and stop if the check fails.

1. List the inputs this skill reads (data files, prior reports, profiler output,
   test results, registries, source code).
2. For each, record `FOUND` or `ABSENT`, not "assumed present".
3. If any input required for a section is ABSENT, that section is
   **`NOT ASSESSED, NO DATA`**. Do not estimate it, do not infer it from an
   adjacent artifact, and do not leave a mandated cell to be filled by whoever
   reads the template next.
4. If **every** required input is ABSENT, stop and report
   **`NOT ASSESSED, NO DATA`** as the whole verdict, naming what was missing and
   which skill produces it.

The rest: https://github.com/Donchitos/Claude-Code-Game-Studios/blob/HEAD/.claude/skills/asset-audit/SKILL.md