What problem does it solve? Working with the Unity Editor through MCP (Model Context Protocol) involves dozens of tools, resources, and version-specific conventions that are easy to misuse, causing compilation errors, stale edits, and failed operations. This Skill provides the operational knowledge to drive Unity Editor automation correctly and efficiently. ## Core Features & Use Cases - Resource-First Workflow: Read editor state, scene, and project info resources before invoking tools to prevent errors and detect installed packages (uGUI, TextMeshPro, Input System, UI Toolkit). - Tool Orchestration: Covers scene management, GameObject creation/modification, C# script creation and structured editing, prefabs, materials, UI (UI Toolkit and uGUI), cameras with Cinemachine, graphics, packages, ProBuilder, and test execution. - Best Practices: Batch operations with batch_execute, compilation-aware script workflows, screenshot-based visual verification, pagination handling, multi-instance routing, and error recovery patterns. - Use Case: Ask the AI to build a game scene in Unity — it creates a fresh scene, batches GameObject creation, writes and compiles C# scripts, wires component references, runs EditMode tests, and verifies the result with screenshots. ## Quick Start Use the unity-mcp-orchestrator skill to create a new Unity scene with a player character, a follow camera, and a movement script, then verify it with a screenshot.