What problem does it solve? Unity Editor automation normally requires the editor to be running and reachable through the UnitySkills REST server, leaving no way to start a closed project, run CI-style headless tests, or execute one-shot batch tasks. This Skill provides advisory guidance for driving the experimental official Unity CLI against a project that has been explicitly bound in the UnitySkills panel. ## Core Features & Use Cases - Cold Start & Liveness: Launch a bound project without Unity Hub using open --args -unityskills-coldstart, triage editor liveness via the UnitySkills registry, and poll REST health until ready. - Headless Tests & Batch Runs: Execute EditMode/PlayMode tests with NUnit XML output and timeouts, or run one-shot -executeMethod batch automation while the editor is closed. - Headless Builds: Build with a required --target and --execute-method, dirty-worktree protection, and structured JSON output for scripting. - Use Case: A CI pipeline needs a full regression run overnight: check cli_config.json is enabled, run unity test --mode EditMode --format json --non-interactive, and parse the NUnit XML report for failures. ## Quick Start Check that Library/UnitySkills/cli_config.json exists with enabled:true, then ask the AI to cold-start the bound Unity project and run its EditMode tests headlessly with JSON output.