asset-audit▌
Donchitos/Claude-Code-Game-Studios · updated Apr 16, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
### Asset Audit
- ›description: "Audits game assets for compliance with naming conventions, file size budgets, format standards, and pipeline requirements. Identifies orphaned assets, missing references, and standard vi
- ›argument-hint: "[category|all]"
- ›allowed-tools: Read, Glob, Grep
| name | asset-audit |
| description | "Audits game assets for compliance with naming conventions, file size budgets, format standards, and pipeline requirements. Identifies orphaned assets, missing references, and standard violations." |
| argument-hint | "[category|all]" |
| user-invocable | true |
| allowed-tools | Read, Glob, Grep # Read-only diagnostic skill — no specialist agent delegation needed |
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 assetsassets/audio/**/*for audio assetsassets/vfx/**/*for VFX assetsassets/shaders/**/*for shadersassets/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-auditto cross-check asset counts against GDD-specified requirements.
How to use asset-audit on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add asset-audit
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches asset-audit from GitHub repository Donchitos/Claude-Code-Game-Studios and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate asset-audit. Access the skill through slash commands (e.g., /asset-audit) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
Task Automation & Efficiency
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Knowledge Enhancement
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Quality Improvement
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client with skill support
- ›Clear understanding of task or problem to solve
- ›Willingness to iterate and refine outputs
Time Estimate
15-45 minutes depending on use case complexity
Installation Steps
- 1.Install skill using provided installation command
- 2.Test with simple use case relevant to your work
- 3.Evaluate output quality and relevance
- 4.Iterate on prompts to improve results
- 5.Integrate into regular workflow if valuable
Common Pitfalls
- ⚠Expecting perfect results without iteration
- ⚠Not providing enough context in prompts
- ⚠Using skill for tasks outside its intended scope
- ⚠Accepting outputs without review and validation
Best Practices▌
✓ Do
- +Start with clear, specific prompts
- +Provide relevant context and constraints
- +Review and refine all outputs before using
- +Iterate to improve output quality
- +Document successful prompt patterns
✗ Don't
- −Don't use without understanding skill limitations
- −Don't skip validation of outputs
- −Don't share sensitive information in prompts
- −Don't expect skill to replace human judgment
💡 Pro Tips
- ★Be specific about desired format and style
- ★Ask for multiple options to choose from
- ★Request explanations to understand reasoning
- ★Combine AI efficiency with human expertise
When to Use This▌
✓ Use When
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid When
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
Learning Path▌
- 1Familiarize yourself with skill capabilities and limitations
- 2Start with low-risk, non-critical tasks
- 3Progress to more complex and valuable use cases
- 4Build expertise through regular use and experimentation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.6★★★★★69 reviews- ★★★★★Dhruvi Jain· Dec 20, 2024
asset-audit reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Arjun Johnson· Dec 20, 2024
Registry listing for asset-audit matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Mia Nasser· Dec 20, 2024
asset-audit is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Liam Martin· Dec 8, 2024
I recommend asset-audit for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Naina Chen· Dec 8, 2024
Useful defaults in asset-audit — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Lucas Martin· Nov 27, 2024
asset-audit reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Yuki Gupta· Nov 27, 2024
Registry listing for asset-audit matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Oshnikdeep· Nov 11, 2024
I recommend asset-audit for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Arya Thomas· Nov 11, 2024
Useful defaults in asset-audit — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Henry Agarwal· Nov 11, 2024
Solid pick for teams standardizing on skills: asset-audit is focused, and the summary matches what you get after install.
showing 1-10 of 69