agentleFS
Sign inStart free
dawn840705dawn840705/claude-code-studios/skills/asset-audit/SKILL.md

asset-audit

Skill1 starsChanged 3 months agoMITView on GitHub

Audits game assets for compliance with naming conventions, file size budgets, format standards, and pipeline requirements. Identifies orphaned assets, missing references, and standard violations.

13 other projects use a version of this, 9 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

6 rules. 1 is common, 4 are distinctive, and 1 is very specific to this project.

  • 1

    Common

    Most of the 11 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read the art bible or asset standards from the relevant design docs and the CLAUDE.md naming conventions.

    line 12
  2. Common:

    All files must be lowercase with underscores

    line 33
  3. Distinctive:

    Orphaned assets: Search code for references to each asset file.

    line 40
  4. Distinctive:

    Missing assets: Search code for asset references and verify the files exist.

    line 42
  5. Distinctive:

    Delete confirmed orphaned assets after manual review.

    line 93
  6. Very specific:

    Run /content-audit to cross-check asset counts against GDD-specified requirements.

    line 94

“Common” is measured: kept by at least 6 in 10 of the 11 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Phase 1: Read Standards

Read the art bible or asset standards from the relevant design docs and the CLAUDE.md naming conventions.

Phase 2: Scan Asset Directories

Scan the target asset directory using Glob:

  • assets/art/**/* for art assets
  • assets/audio/**/* for audio assets
  • assets/vfx/**/* for VFX assets
  • assets/shaders/**/* for shaders
  • assets/data/**/* for data files

Phase 3: Run Compliance Checks

Naming conventions:

  • Art: [category]_[name]_[variant]_[size].[ext]
  • Audio: [category]_[context]_[name]_[variant].[ext]
  • All files must be lowercase with underscores

File standards:

  • Textures: Power-of-two dimensions, correct format (PNG for UI, compressed for 3D), within size budget
  • Audio: Correct sample rate, format (OGG for SFX, OGG/MP3 for music), within duration limits
  • Data: Valid JSON/YAML, schema-compliant

Orphaned assets: Search code for references to each asset file. Flag any with no references.

Missing assets: Search code for asset references and verify the files exist.

Phase 4: Output Audit Report

# Asset Audit Report -- [Category] -- [Date]

## Summary
- **Total assets scanned**: [N]
- **Naming violations**: [N]
- **Size violations**: [N]
- **Format violations**: [N]
- **Orphaned assets**: [N]
- **Missing assets**: [N]
- **Overall health**: [CLEAN / MINOR ISSUES / NEEDS ATTENTION]

## Naming Violations
| File | Expected Pattern | Issue |
|------|-----------------|-------|

## Size Violations
| File | Budget | Actual | Overage |
|------|--------|--------|---------|

## Format Violations
| File | Expected Format | Actual Format |
|------|----------------|---------------|

## Orphaned Assets (no code references found)
| File | Last Modified | Size | Recommendation |
|------|-------------|------|---------------|

## Missing Assets (referenced but not found)
| Reference Location | Expected Path |
|-------------------|---------------|

## Recommendations
[Prioritized list of fixes]

## Verdict: [COMPLIANT / WARNINGS / NON-COMPLIANT]

This skill is read-only — it produces a report but does not write files.

Phase 5: Next Steps

  • Fix naming violations using the patterns defined in CLAUDE.md.
  • Delete confirmed orphaned assets after manual review.
  • Run /content-audit to cross-check asset counts against GDD-specified requirements.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free