What problem does it solve? Unity 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 batch builds impossible when the Editor is closed. This Skill governs safe use of the experimental Unity CLI so those operations work on a bound project without the Editor open. ## Core Features & Use Cases - Cold start and lifecycle control: Launch a closed Unity Editor with the -unityskills-coldstart marker, verify liveness via the registry, PID checks, and Library/UnityLockfile, then wait for REST health. - Headless tests and batch runs: Execute EditMode/PlayMode tests with NUnit XML output and run one-shot -executeMethod batch jobs with timeouts and structured exit codes. - Headless builds: Build via Unity 6 Build Profiles, built-in desktop targets, or custom C# build methods, with dirty-worktree guards and signal-aware crash diagnostics. - Use Case: In a CI pipeline, run unity test against a bound project with --format json --non-interactive and a timeout, then parse the NUnit XML report for results while the Editor stays closed. ## Quick Start Check the project's Library/UnitySkills/cli_config.json to confirm the CLI is enabled, then ask the agent to run the project's EditMode tests headlessly with JSON output and a timeout.
