agentleFS
scotidevscotidev/GameDevStudio/.agents/skills/asset-audit/SKILL.md

asset-audit

Skill1 starsChanged 8 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, 10 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use soak-test, team-live-ops and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • lilangMaxSkill

    soak-test

    Generate a soak test protocol for extended play sessions. Defines what to observe, measure, and log during long play sessions to surface slow leaks, fatigue effects, and edge cases that only appear after sustained play. Primarily used in Polish and Release phases.

    Also in 5 projects that use this

  • lilangMaxSkill

    team-live-ops

    Orchestrate the live-ops team for post-launch content planning: coordinates live-ops-designer, economy-designer, analytics-engineer, community-manager, writer, and narrative-director to design and plan a season, event, or live content update.

    Also in 5 projects that use this

  • +10 more from lilangMax

The file

We split this skill into the rules it gives an agent

2 rules. 1 is common, 1 is distinctive, and 0 are very specific to this project.

  • 1

    Common

    Most of the 12 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When this skill is invoked:

    line 9
  2. Common:

    All files must be lowercase with underscores

    line 24

“Common” is measured: kept by at least 6 in 10 of the 12 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

When this skill is invoked:

  1. Read the art bible or asset standards from the relevant design docs and the AGENTS.md naming conventions.
  2. 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
  3. Check naming conventions:
    • Art: [category]_[name]_[variant]_[size].[ext]
    • Audio: [category]_[context]_[name]_[variant].[ext]
    • All files must be lowercase with underscores
  4. Check 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
  5. Check for orphaned assets by searching code for references to each asset file.
  6. Check for missing assets by searching code for asset references and verifying the files exist.
  7. Output the audit:
# 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]

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.