What problem does it solve? Unity Editor automation normally requires the editor to be running and reachable through the UnitySkills REST server, which makes cold starts, CI-style headless test runs, and unattended builds impossible. This Skill governs safe use of the experimental Unity CLI so those lifecycle operations work while the editor is closed. ## Core Features & Use Cases - Cold Start & Lifecycle: Launch the bound Unity project with the -unityskills-coldstart marker, verify the installed editor version, and triage liveness via the registry, lockfile, and CLI process list before starting anything. - Headless Tests & Batch Runs: Run EditMode/PlayMode tests with NUnit XML output and timeouts, or execute one-shot -executeMethod batch automation while the editor is closed. - Headless Builds: Build via Unity 6 Build Profiles, built-in desktop targets, or custom C# build methods, with dirty-worktree guards and structured exit codes. - Use Case: In a CI pipeline, run unity test against a bound project with --format json --non-interactive and a timeout to produce an NUnit XML report without ever opening the editor interactively. ## Quick Start Read the project's Library/UnitySkills/cli_config.json to confirm the CLI is enabled, then ask the assistant to cold-start the bound Unity project and wait for the REST health endpoint.
