unity-mcp-skills
Skill7 starsChanged 7 months agoMITView on GitHub
Use when working with a Unity project via MCP — creating or editing scenes, GameObjects, components, prefabs, materials, UI, lighting, navmesh, animations, terrain, C# scripts, or any other Unity Editor task.
In this repository34 other files it gives its agents.
- 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-validationSkill
- unity-xrSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
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 14
If during a task you find a referenced file is missing or a path does not resolve (e.g.
- Distinctive: line 23
Do not attempt to work around missing files by fabricating recipe content.
- Distinctive: line 86
All paths above are relative to the library root (this file's directory).
≈ “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 MCP Skills Library
Overview
The single entry point for Unity work via MCP. Domain skills under skills/<domain>/SKILL.md are loaded on demand from this router — read this file first, then navigate to the domain file that matches the task.
Integrity Check
If during a task you find a referenced file is missing or a path does not resolve
(e.g. ../../recipes/scene/scene_create.md not found, a recipes/_shared/ helper
missing, ../../mcp-tools.md missing, or a references/<topic>.md fallback missing),
stop and tell the user:
The Unity skills library appears to be incomplete or out of date. Please reinstall or update the
unity-mcp-skillsfolder in your agent's skills directory to the latest version from https://github.com/batihandev/unity-mcp-skills, then retry.
Do not attempt to work around missing files by fabricating recipe content.
Routing Order
- Native MCP tool — see
mcp-tools.md(library root) for the routing matrix. - Topic skill + exact recipe — load the matching domain skill below, then its recipe in
recipes/<domain>/. - Install-once Editor tool — if the task needs a persistent Editor script, check
tooling/<domain>/viaskills/tooling/SKILL.md. - Closest recipe — adapt the nearest recipe if no exact match exists.
references/index.md— lists all available topics; consultreferences/<topic>.mdas a tertiary fallback.- Fresh
Unity_RunCommand— last resort; allowed only under the RunCommand Contract below.
RunCommand Contract
Before the first Unity_RunCommand in a domain, read that domain's skills/<domain>/SKILL.md and the recipe it routes to. Every Unity_RunCommand body either adapts a named recipe (recipes/<domain>/<command>.md — name it) or states that no recipe covers the case. Do not send a fresh body without saying which of the two applies.
Execution trees
Two trees, route by execution model first:
recipes/<domain>/—Unity_RunCommandone-shot bodies, compile/run-gated.tooling/<domain>/—Unity_CreateScriptinstall-once Editor scripts, no gate. Seetooling/README.md.
The Domain Skill Map below indexes recipes/. For install-once tools, open tooling/<domain>/README.md under the same domain name.
Domain Skill Map
| Domain | What it covers | Skill file | Tool route |
| gameobject | Object create/move/parent | skills/gameobject/SKILL.md | Unity_RunCommand |
| component | Component add/remove/configure | skills/component/SKILL.md | Unity_RunCommand |
| material | Material property edits | skills/material/SKILL.md | Unity_RunCommand |
| light | Light create/configure | skills/light/SKILL.md | Unity_RunCommand |
| prefab | Prefab create/apply/spawn | skills/prefab/SKILL.md | Unity_RunCommand |
| asset | Asset refresh/find/info | skills/asset/SKILL.md | Unity_RunCommand |
| ui | UGUI Canvas/UI creation | skills/ui/SKILL.md | Unity_RunCommand |
| uitoolkit | UXML/USS/UIDocument | skills/uitoolkit/SKILL.md | Unity_RunCommand |
| script | Script edit/validate/SHA | skills/script/SKILL.md | Native MCP only (Unity_CreateScript / Unity_ScriptApplyEdits / Unity_ValidateScript / …) — no recipes |
| tooling | Install-once Editor script templates | skills/tooling/SKILL.md | Unity_CreateScript (templates under tooling/<domain>/) |
| scene | Scene load/save/query | skills/scene/SKILL.md | Unity_RunCommand |
| editor | Play/select/undo/redo | skills/editor/SKILL.md | Unity_RunCommand |
| animator | Animator controllers | skills/animator/SKILL.md | Unity_RunCommand |
| shader | Shader create/list | skills/shader/SKILL.md | Unity_RunCommand |
| console | Log capture/debug | skills/console/SKILL.md | Unity_ReadConsole |
| validation | Broken reference checks | skills/validation/SKILL.md | Unity_RunCommand |
| importer | Texture/audio/model import | skills/importer/SKILL.md | Unity_RunCommand |
| cinemachine | VCam operations | skills/cinemachine/SKILL.md | Unity_RunCommand |
| probuilder | ProBuilder mesh edits | skills/probuilder/SKILL.md | Unity_RunCommand |
| xr | XRI setup | skills/xr/SKILL.md | Unity_RunCommand |
| terrain | Terrain create/paint | skills/terrain/SKILL.md | Unity_RunCommand |
| physics | Raycast/overlap/gravity | skills/physics/SKILL.md | Unity_RunCommand |
| navmesh | NavMesh bake/query | skills/navmesh/SKILL.md | Unity_RunCommand |
| timeline | Timeline tracks/clips | skills/timeline/SKILL.md | Unity_RunCommand |
| cleaner | Unused/duplicate assets | skills/cleaner/SKILL.md | Unity_RunCommand |
| smart | Query/layout/auto-bind | skills/smart/SKILL.md | Unity_RunCommand |
| perception | Scene/project analysis | skills/perception/SKILL.md | Unity_RunCommand |
| camera | Scene View camera | skills/camera/SKILL.md | Unity_Camera_Capture (Scene View / in-memory); game-camera PNG at a path/resolution → camera_screenshot recipe — do not hand-roll a RenderTexture |
| event | UnityEvent wiring | skills/event/SKILL.md | Unity_RunCommand |
| package | UPM install/query | skills/package/SKILL.md | Native MCP only (Unity_PackageManager_ExecuteAction / Unity_PackageManager_GetData) |
| project | Project info/settings | skills/project/SKILL.md | Unity_GetProjectData |
| optimization | Asset optimization | skills/optimization/SKILL.md | Unity_RunCommand |
| test | Unity Test Runner | skills/test/SKILL.md | Unity_CreateScript once (tooling/test/test_runner_tool), then Unity_RunCommand to call it — never register a result callback from a RunCommand body |
| scriptableobject | ScriptableObject assets | skills/scriptableobject/SKILL.md | Unity_RunCommand |
All paths above are relative to the library root (this file's directory).
Other root files
mcp-tools.md— full routing matrix for native MCP tools vsUnity_RunCommand.recipes/README.md— recipes intro and conventions.tooling/README.md— install-once Editor script templates (not subject to RunCommand validation); domain subfolders mirrorrecipes/.recipes/_shared/README.md— cross-domain C# helpers embedded by many recipes:execution_result,validate,workflow_manager,gameobject_finder,skills_common,component_type_finder,value_converter,project_skills,perception_helpers.references/index.md— catalog of allreferences/<topic>.mdfallback docs.
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.