Run any Skill in Manus with one click

unity-tooling

Stars4

Forks0

UpdatedMay 26, 2026 at 10:17

Use when about to write or install a custom Editor script, add a [MenuItem], build a custom Editor window, or create a one-off Editor helper — to check whether a ready-to-paste template already exists in tooling/<domain>/ before reaching for Unity_CreateScript.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

batihandev

batihandev/unity-mcp-skills

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	unity-tooling
description	Use when about to write or install a custom Editor script, add a [MenuItem], build a custom Editor window, or create a one-off Editor helper — to check whether a ready-to-paste template already exists in tooling/<domain>/ before reaching for Unity_CreateScript.

Tooling Index

Install-once Editor script templates live under ../../tooling/<domain>/. Check here before writing a new Editor script from scratch.

When to Use

Reach for tooling/ when the task needs a persistent Editor-side helper rather than a one-shot Unity_RunCommand body. Signals:

About to paste a [MenuItem("Tools/...")] script via Unity_CreateScript.
Need a tool the user re-runs from the Editor menu later (screenshots, exporters, custom build steps, batch operations).
A recipe in recipes/<domain>/ carries a "Prerequisite: install Editor script" note pointing at tooling/<domain>/.

Do NOT use for one-shot operations — those belong in recipes/<domain>/ and run through Unity_RunCommand.

Routing

Open ../../tooling/<domain>/README.md for the domain that matches the task (e.g. tooling/ui/).
If a matching tool exists, install via Unity_CreateScript at the path the tool file specifies.
Wait for Unity to recompile — poll EditorApplication.isCompiling (see UI Authoring Loop Phase 1 in ../ui/SKILL.md).
Call the installed menu items via EditorApplication.ExecuteMenuItem.

If no tool covers the case, write one — but check first.

Available domains

Domain	Folder	Tools
ui	`../../tooling/ui/`	`ui_screenshot_tool`

Common Mistakes

Pasting a tooling/ C# block into Unity_RunCommand. These are install-once Editor scripts, not IRunCommand bodies — they will not compile in the RunCommand context. Always install via Unity_CreateScript at the path the tool file specifies.
Calling EditorApplication.ExecuteMenuItem immediately after install. Unity needs to recompile the new script before the menu items register. Poll isCompiling first.
Treating tooling/ files as compile/run-gated like recipes/. They have no validation gate — install into a scratch project once before trusting at scale.

More from this repository

same repository

unity-mcp-skills

batihandev/unity-mcp-skills

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.

2026-07-034

unity-test

batihandev/unity-mcp-skills

Use when users want to run Unity tests or read test results.

2026-05-294

unity-editor

batihandev/unity-mcp-skills

Use when users want to enter play mode, select objects, undo/redo, or execute menu commands.

2026-05-264

unity-script

batihandev/unity-mcp-skills

Use when creating, reading, editing, searching, validating, or deleting C# scripts in a Unity project.

2026-05-264

unity-ui

batihandev/unity-mcp-skills

Use when users want to create Canvas, Button, Text, Image, or other UI elements.

2026-05-264

unity-cleaner

batihandev/unity-mcp-skills

Use when users want to find unused assets, duplicate files, or clean up the project.

2026-05-114

name	unity-tooling
description	Use when about to write or install a custom Editor script, add a [MenuItem], build a custom Editor window, or create a one-off Editor helper — to check whether a ready-to-paste template already exists in tooling/<domain>/ before reaching for Unity_CreateScript.

Tooling Index

Install-once Editor script templates live under ../../tooling/<domain>/. Check here before writing a new Editor script from scratch.

When to Use

Reach for tooling/ when the task needs a persistent Editor-side helper rather than a one-shot Unity_RunCommand body. Signals:

About to paste a [MenuItem("Tools/...")] script via Unity_CreateScript.
Need a tool the user re-runs from the Editor menu later (screenshots, exporters, custom build steps, batch operations).
A recipe in recipes/<domain>/ carries a "Prerequisite: install Editor script" note pointing at tooling/<domain>/.

Do NOT use for one-shot operations — those belong in recipes/<domain>/ and run through Unity_RunCommand.

Routing

Open ../../tooling/<domain>/README.md for the domain that matches the task (e.g. tooling/ui/).
If a matching tool exists, install via Unity_CreateScript at the path the tool file specifies.
Wait for Unity to recompile — poll EditorApplication.isCompiling (see UI Authoring Loop Phase 1 in ../ui/SKILL.md).
Call the installed menu items via EditorApplication.ExecuteMenuItem.

If no tool covers the case, write one — but check first.

Available domains

Domain	Folder	Tools
ui	`../../tooling/ui/`	`ui_screenshot_tool`

Common Mistakes

Pasting a tooling/ C# block into Unity_RunCommand. These are install-once Editor scripts, not IRunCommand bodies — they will not compile in the RunCommand context. Always install via Unity_CreateScript at the path the tool file specifies.
Calling EditorApplication.ExecuteMenuItem immediately after install. Unity needs to recompile the new script before the menu items register. Poll isCompiling first.
Treating tooling/ files as compile/run-gated like recipes/. They have no validation gate — install into a scratch project once before trusting at scale.