unity-validation
Skill7 starsChanged 7 months agoMITView on GitHub
Use when users want to find missing scripts, validate references, or check project health.
In this repository34 other files it gives its agents.
- unity-mcp-skillsSkill
- unity-animatorSkill
- unity-assetSkill
- unity-cameraSkill
- unity-cinemachineSkill
- unity-cleanerSkill
- unity-componentSkill
- unity-consoleSkill
- unity-editorSkill
- unity-eventSkill
- unity-gameobjectSkill
- unity-importerSkill
- unity-lightSkill
- unity-materialSkill
- unity-navmeshSkill
- unity-optimizationSkill
- unity-packageSkill
- unity-perceptionSkill
- unity-physicsSkill
- unity-prefabSkill
- unity-probuilderSkill
- unity-projectSkill
- unity-sceneSkill
- unity-scriptableobjectSkill
- unity-scriptSkill
- unity-shaderSkill
- unity-smartSkill
- unity-terrainSkill
- unity-testSkill
- unity-timelineSkill
- unity-toolingSkill
- unity-uiSkill
- unity-uitoolkitSkill
- unity-xrSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
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
- Distinctive: line 66
Remove missing script components.
- Distinctive: line 75
Remove empty folders from project.
- Distinctive: line 95
Check for oversized textures.
- Distinctive: line 156
Run validation before major builds
- Distinctive: line 158
Keep texture sizes appropriate for target platform
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Unity Validation Skills
Overview
Maintain project health - find problems, clean up, and validate your Unity project.
Common Mistakes
DO NOT (common hallucinations):
- Validation skill routes use the
validate_*prefix, notvalidation_* validation_run/validation_checkdo not exist → use specific skills such asvalidate_scene,validate_project_structure,validate_missing_referencesvalidation_fixdoes not exist → validation skills report issues; use other modules to fix themvalidation_cleandoes not exist → usecleanermodule for cleanup operations
Routing:
- For unused/duplicate asset cleanup → use
cleanermodule - For missing script fix →
cleaner_fix_missing_scripts(cleaner module) - For compile errors →
script_get_compile_feedback(script module)
Skills Overview
| Skill | Description |
validate_scene | Comprehensive scene validation |
validate_find_missing_scripts | Find objects with missing scripts |
validate_fix_missing_scripts | Remove missing script components |
validate_cleanup_empty_folders | Remove empty folders |
validate_find_unused_assets | Find potentially unused assets |
validate_texture_sizes | Check texture sizes |
validate_project_structure | Get project overview |
validate_missing_references | Find null/missing object references on components |
validate_mesh_collider_convex | Find non-convex MeshColliders |
validate_shader_errors | Find shaders with compilation errors |
Skills
validate_scene
Comprehensive scene validation.
| Parameter | Type | Required | Default | Description |
checkMissingScripts | bool | No | true | Check for missing scripts |
checkMissingPrefabs | bool | No | true | Check for missing prefabs |
checkDuplicateNames | bool | No | false | Check duplicate names |
Returns: {success, sceneName, totalIssues, missingScripts, missingPrefabs, duplicateNames}
validate_find_missing_scripts
Find objects with missing script references.
| Parameter | Type | Required | Default | Description |
searchInPrefabs | bool | No | false | Also check prefab assets |
Returns: {success, count, objectsWithMissingScripts: [{name, path, missingCount}]}
validate_fix_missing_scripts
Remove missing script components.
| Parameter | Type | Required | Default | Description |
dryRun | bool | No | true | Preview only, don't remove |
Returns: {success, totalFixed, fixedObjects}
validate_cleanup_empty_folders
Remove empty folders from project.
| Parameter | Type | Required | Default | Description |
rootPath | string | No | "Assets" | Starting folder |
dryRun | bool | No | true | Preview only, don't delete |
Returns: {success, count, foldersToDelete: [path]}
validate_find_unused_assets
Find potentially unused assets.
| Parameter | Type | Required | Default | Description |
assetType | string | No | null | Filter: Texture/Material/Prefab/etc |
limit | int | No | 100 | Max results |
Returns: {success, count, unusedAssets: [path]}
validate_texture_sizes
Check for oversized textures.
| Parameter | Type | Required | Default | Description |
maxRecommendedSize | int | No | 2048 | Warn if larger |
limit | int | No | 50 | Max results |
Returns: {success, totalChecked, oversizedCount, oversizedTextures: [{path, width, height, recommendation}]}
validate_project_structure
Get project folder structure overview.
| Parameter | Type | Required | Default | Description |
rootPath | string | No | "Assets" | Starting folder |
maxDepth | int | No | 3 | Max folder depth |
Returns: {success, structure, summary: {totalFolders, totalAssets}}
validate_missing_references
Find null/missing object references on components in the scene.
| Parameter | Type | Required | Default | Description |
limit | int | No | 50 | Max results |
Returns: { success, count, issues: [{ gameObject, path, component, property }] }
validate_mesh_collider_convex
Find non-convex MeshColliders (potential performance issue).
| Parameter | Type | Required | Default | Description |
limit | int | No | 50 | Max results |
Returns: { success, count, nonConvexColliders: [{ gameObject, path, vertexCount }] }
validate_shader_errors
Find shaders with compilation errors.
| Parameter | Type | Required | Default | Description |
limit | int | No | 50 | Max results |
Returns: { success, count, shaders: [{ name, path, errorCount }] }
Common Workflows
Recipe path rule: ../../recipes/validation/<command>.md
Pre-Build Check
See ../../recipes/validation/<command>.md for C# templates.
Project Cleanup
See ../../recipes/validation/<command>.md for C# templates.
Best Practices
- Always use
dryRun=Truefirst to preview changes - Run validation before major builds
- Review unused assets manually before deletion
- Keep texture sizes appropriate for target platform
- Fix missing scripts before they cause runtime errors
- Regular cleanup prevents project bloat
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
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.

