asset-audit

Audit game assets for naming, size, format, orphaned files, and missing references.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/polsegu/Claude-Code-Game-Dev --skill asset-audit-polsegu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: asset-audit
Source: https://github.com/polsegu/Claude-Code-Game-Dev/tree/main/.claude/skills/asset-audit
Command: npx skills add https://github.com/polsegu/Claude-Code-Game-Dev --skill asset-audit-polsegu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Inconsistent asset naming, incorrect formats, oversize files, orphaned or missing assets, and pipeline violations cause build failures, wasted storage, and artist/developer rework; this Skill centralizes detection so teams can fix issues before they impact production.

Core Features & Use Cases

  • Compliance scanning: Validates naming conventions, lowercase/underscore rules, and expected filename patterns across art, audio, VFX, shaders, and data.
  • Standards & size checks: Verifies texture dimensions and formats, audio sample rates and durations, and data file schema/validity against project budgets.
  • Reference analysis: Finds orphaned files with no code references and flags missing assets referenced by code, producing a prioritized markdown audit for asset managers and engineers.
  • Use case: Run before a build or content freeze to ensure assets meet engine and pipeline requirements and to produce a remediation plan for artists and engineers.

Quick Start

Run the asset-audit skill on assets/art, assets/audio, and assets/vfx to generate a markdown audit report summarizing naming, size, format, orphaned, and missing asset issues.

Frequently Asked Questions about asset-audit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check game assets for naming convention compliance and pipeline violations?

Asset naming compliance is enforced by scanning art, audio, VFX, shaders, and data directories to validate lowercase/underscore rules and expected filename patterns. This detects pipeline violations before builds, preventing rework and build failures caused by inconsistent naming conventions.

How do I find orphaned files and missing asset references in my game project?

Orphaned files and missing references are found by cross-referencing filesystem globs with code content greps. This identifies assets with no code references and flags missing assets referenced by code, producing a prioritized remediation plan for artists and engineers.

Can I validate texture dimensions, audio sample rates, and data schemas against production budgets?

Texture dimensions, audio sample rates, durations, and data file schemas are validated against project production budgets. This checks file sizes and formats to ensure assets comply with engine constraints and storage limits before content freezes.

What's the best way to audit game assets before a content freeze or build?

The best way to audit assets before a build is running a comprehensive scan across art, audio, VFX, shaders, and data directories. This generates a markdown audit report with issue counts and prioritized recommendations for quick remediation.

Does asset auditing work without external dependencies or specific engine tools?

Asset auditing works standalone without external dependencies, using filesystem globbing, file inspection, content grep, and schema validation. It operates directly on project directories to produce compliance reports independent of specific engine tooling.