### Asset Audit
Works with
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
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionasset-auditExecute the skills CLI command in your project's root directory to begin installation:
Fetches asset-audit from Donchitos/Claude-Code-Game-Studios and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate asset-audit. Access via /asset-audit in your agent's command palette.
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 environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
0
total installs
0
this week
10.7K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
10.7K
stars
| 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 |
Read the art bible or asset standards from the relevant design docs and the CLAUDE.md naming conventions.
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 filesNaming conventions:
[category]_[name]_[variant]_[size].[ext][category]_[context]_[name]_[variant].[ext]File standards:
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.
# 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.
/content-audit to cross-check asset counts against GDD-specified requirements.Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ 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.
JuliusBrussee/caveman
JuliusBrussee/caveman
whyashthakker/agent-skills-marketing
JuliusBrussee/caveman
whyashthakker/agent-skills-marketing
vercel-labs/skills
asset-audit reduced setup friction for our internal harness; good balance of opinion and flexibility.
Registry listing for asset-audit matched our evaluation — installs cleanly and behaves as described in the markdown.
asset-audit is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
I recommend asset-audit for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Useful defaults in asset-audit — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
asset-audit reduced setup friction for our internal harness; good balance of opinion and flexibility.
Registry listing for asset-audit matched our evaluation — installs cleanly and behaves as described in the markdown.
I recommend asset-audit for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Useful defaults in asset-audit — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
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