agentleFS
batihandevbatihandev/unity-mcp-skills/skills/validation/SKILL.md

unity-validation

Skill7 starsChanged 7 months agoMITView on GitHub

Use when users want to find missing scripts, validate references, or check project health.

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
  1. Distinctive:

    Remove missing script components.

    line 66
  2. Distinctive:

    Remove empty folders from project.

    line 75
  3. Distinctive:

    Check for oversized textures.

    line 95
  4. Distinctive:

    Run validation before major builds

    line 156
  5. Distinctive:

    Keep texture sizes appropriate for target platform

    line 158

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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, not validation_*
  • validation_run / validation_check do not exist → use specific skills such as validate_scene, validate_project_structure, validate_missing_references
  • validation_fix does not exist → validation skills report issues; use other modules to fix them
  • validation_clean does not exist → use cleaner module for cleanup operations

Routing:

  • For unused/duplicate asset cleanup → use cleaner module
  • For missing script fix → cleaner_fix_missing_scripts (cleaner module)
  • For compile errors → script_get_compile_feedback (script module)

Skills Overview

SkillDescription
validate_sceneComprehensive scene validation
validate_find_missing_scriptsFind objects with missing scripts
validate_fix_missing_scriptsRemove missing script components
validate_cleanup_empty_foldersRemove empty folders
validate_find_unused_assetsFind potentially unused assets
validate_texture_sizesCheck texture sizes
validate_project_structureGet project overview
validate_missing_referencesFind null/missing object references on components
validate_mesh_collider_convexFind non-convex MeshColliders
validate_shader_errorsFind shaders with compilation errors

Skills

validate_scene

Comprehensive scene validation.

ParameterTypeRequiredDefaultDescription
checkMissingScriptsboolNotrueCheck for missing scripts
checkMissingPrefabsboolNotrueCheck for missing prefabs
checkDuplicateNamesboolNofalseCheck duplicate names

Returns: {success, sceneName, totalIssues, missingScripts, missingPrefabs, duplicateNames}

validate_find_missing_scripts

Find objects with missing script references.

ParameterTypeRequiredDefaultDescription
searchInPrefabsboolNofalseAlso check prefab assets

Returns: {success, count, objectsWithMissingScripts: [{name, path, missingCount}]}

validate_fix_missing_scripts

Remove missing script components.

ParameterTypeRequiredDefaultDescription
dryRunboolNotruePreview only, don't remove

Returns: {success, totalFixed, fixedObjects}

validate_cleanup_empty_folders

Remove empty folders from project.

ParameterTypeRequiredDefaultDescription
rootPathstringNo"Assets"Starting folder
dryRunboolNotruePreview only, don't delete

Returns: {success, count, foldersToDelete: [path]}

validate_find_unused_assets

Find potentially unused assets.

ParameterTypeRequiredDefaultDescription
assetTypestringNonullFilter: Texture/Material/Prefab/etc
limitintNo100Max results

Returns: {success, count, unusedAssets: [path]}

validate_texture_sizes

Check for oversized textures.

ParameterTypeRequiredDefaultDescription
maxRecommendedSizeintNo2048Warn if larger
limitintNo50Max results

Returns: {success, totalChecked, oversizedCount, oversizedTextures: [{path, width, height, recommendation}]}

validate_project_structure

Get project folder structure overview.

ParameterTypeRequiredDefaultDescription
rootPathstringNo"Assets"Starting folder
maxDepthintNo3Max folder depth

Returns: {success, structure, summary: {totalFolders, totalAssets}}

validate_missing_references

Find null/missing object references on components in the scene.

ParameterTypeRequiredDefaultDescription
limitintNo50Max results

Returns: { success, count, issues: [{ gameObject, path, component, property }] }

validate_mesh_collider_convex

Find non-convex MeshColliders (potential performance issue).

ParameterTypeRequiredDefaultDescription
limitintNo50Max results

Returns: { success, count, nonConvexColliders: [{ gameObject, path, vertexCount }] }

validate_shader_errors

Find shaders with compilation errors.

ParameterTypeRequiredDefaultDescription
limitintNo50Max 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

  1. Always use dryRun=True first to preview changes
  2. Run validation before major builds
  3. Review unused assets manually before deletion
  4. Keep texture sizes appropriate for target platform
  5. Fix missing scripts before they cause runtime errors
  6. Regular cleanup prevents project bloat

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.