What problem does it solve? Setting up Unity editor automation requires choosing between competing MCP adapters, verifying versions, and avoiding risky unreviewed installs. This Skill inspects your Unity project and proposes exactly one compatible, pinned MCP adapter with full transparency before anything changes. ## Core Features & Use Cases - Project Inspection: Confirms ProjectSettings/ProjectVersion.txt, Unity/Hub availability, OS/architecture, Python or Node requirements, existing MCP servers, and uncommitted files. - Adapter Selection: Defaults to CoplayDev/unity-mcp at an immutable commit, switching to IvanMurzak/Unity-MCP only with documented evidence it meets a requirement the default cannot. - Gated Installation: Generates a plan via pack plan unity, requires the user to repeat a displayed digest verbatim, then applies with pack apply and verifies with pack doctor plus a read-only health check. - Use Case: A developer wants AI-driven Unity editor automation but needs licenses, permissions, backups, and rollback steps reviewed before any server is installed or replaced. ## Quick Start Use the setup-unity skill to inspect this Unity project and propose one compatible pinned MCP adapter with rollback steps, waiting for my confirmation before installing anything.