Asset Audit
INTEGRATED SYSTEM: this skill belongs to the complete "Claude Code Game Studios" template (49 agents, 74 skills, templates and a studio CLAUDE.md); it assumes that template and its conventions.
- What
- INTEGRATED SYSTEM: this skill belongs to the complete "Claude Code Game Studios" template (49 agents, 74 skills, templates and a studio CLAUDE.md); it assumes that template and its conventions.
- Cost
- Free
- Needs
- Before you start: read this whole install prompt, tell me in a few lines what this skill does and what installing it involves, and wait for my go-ahead before you do anything else.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — INTEGRATED SYSTEM: this skill belongs to the complete "Claude Code Game Studios" template (49 agents, 74 skills, templates and a studio CLAUDE.md); it assumes that template and its conventions. This listing installs only this skill's folder, without the rest of the system, and the skill may reference template agents or files that are absent outside the full template. It audits a game project's assets against the naming conventions, file-size budgets and format standards set in the art bible: it measures real files (sizes, texture dimensions, audio sample rates, modified times) with read-only shell commands, and finds orphaned assets and missing references. Its hard rule: a measurement it cannot take is NOT ASSESSED, never an estimate — and if the inputs a section needs are absent, that section reports NOT ASSESSED — NO DATA instead of a fabricated pass. By @Donchitos, listed here with credit to its creator. MIT licensed. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Copy the install package below, then paste it into Muse📌 Pinned version: commit 05ad7c8Before you start: read this whole install prompt, tell me in a few lines what this skill does and what installing it involves, and wait for my go-ahead before you do anything else. Prerequisites — INTEGRATED SYSTEM FIRST: this skill is one piece of the complete "Claude Code Game Studios" template (49 agents, 74 skills, studio templates and a studio CLAUDE.md, per the repository README). Each skill assumes that template is installed, with its conventions, its project.yaml / project.local.yaml configuration, its .claude/docs/ mode documents, its hooks (for example hooks/yaml-helper.sh, outside this skill's folder) and its .claude/scripts/ helpers. Installing this listing alone copies only this skill's folder, without the rest of the system: the skill may reference template agents, files, hooks or scripts that are absent outside the full template, and it may not run as designed on its own. No account, no key and no payment are needed to copy the files, and nothing is run during installation. Install "Asset Audit" for me. It is the Game Studios read-only diagnostic for a project's assets: it reads the Asset Standards section of design/art/art-bible.md (size budgets, formats, naming convention — without an art bible, the size section is NOT ASSESSED and the report names /art-bible as the skill that sets them), scans the asset directories, measures files with the read-only commands its frontmatter pre-approves (stat, file, od, wc, du, plus Glob/Grep/Read), and checks naming conventions, size budgets, format standards (such as power-of-two texture dimensions and audio sample rates), orphaned assets and missing references. The file is built around an anti-fabrication rule: insufficient input is checked before any report, absent inputs make a section NOT ASSESSED — NO DATA, and a cell that cannot be measured is never filled with an estimate. Repository: https://github.com/Donchitos/Claude-Code-Game-Studios (the skill is the whole .claude/skills/asset-audit/ folder at the pinned commit: 1 files in total) Pinned version: install the code at commit 05ad7c8a5b8aa2aa86bbd3439ae7cf7295cac418 exactly. Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Clone https://github.com/Donchitos/Claude-Code-Game-Studios into a temporary folder, check out commit 05ad7c8a5b8aa2aa86bbd3439ae7cf7295cac418, and copy the .claude/skills/asset-audit/ folder from that checkout. Then compare every file in the folder with the fingerprints recorded for this listing on 2026-10-22: [FINGERPRINTS] - SKILL.md: SHA-256 9aaa056c533cd0d61af1da5332fd26065fbfa6937db4bd117ac0692f8c65a3f4 If a file does not match, it changed since the listing was prepared: do not install it yet, tell me what you found and let me decide. 2. Read SKILL.md in full, and tell me in plain words: what the skill does when used, what it connects to, whether it reads or sends any personal information or credentials, and anything that seems unusual. Stop on any red flag and tell me before going further. Confirm these points from the files: - The skill folder holds 1 file only: SKILL.md (8175 characters of instructions in a single file; there are no companion files in its folder). Nothing in the folder is run during installation; companion files are instructions/references the skill reads at use time, copied as-is. - Nothing is sent anywhere during installation itself; the only download at install time is the skill folder from GitHub at the pinned commit, and no project of mine is read or modified. - At use time this is a read-only diagnostic inside my project: it lists asset files with Glob and measures them only with the pre-approved read-only commands named in its frontmatter (stat, file, od, wc, du), reads the art bible's Asset Standards for the budgets and formats to check against, and writes nothing. It does not use the template's yaml-helper hook, but it does depend on template/project artifacts — above all design/art/art-bible.md (produced by the /art-bible skill of the same template) — and outside the template's conventions its standards source is absent. - No account, key, payment or third-party service is named in the files I read; any file it writes at use time is in my own project and follows the template's ask-before-writing collaborative conventions described in the skill. - Do not run any template hook or script, do not spawn any template agent, and do not use the skill in any way during this install: using it is a separate step that only starts when I ask for it later. 3. When I say "yes, install", install it as a skill: copy the whole asset-audit folder into the agent's skills directory, in a folder named exactly "asset-audit", keeping its 1 files in their original relative layout (SKILL.md at its root). 4. Verify with no network calls: frontmatter valid (name: asset-audit), the 1 files in place with matching fingerprints. Do not run anything from the folder and do not use the skill to verify. 5. Report what was installed, where, and what I still need to do myself (for example: that it belongs to the full Claude Code Game Studios template (its standards come from the template's art bible) and that it is a read-only diagnostic: it measures my project's assets with stat/file/od/wc/du and reports NOT ASSESSED rather than guessing when data is missing). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.