What problem does it solve? When the Unity Editor is closed, REST-based automation cannot reach the project, leaving agents unable to start the editor, run tests, execute batch methods, or produce builds. This Skill provides advisory guidance for driving the experimental official Unity CLI against a project that has been explicitly bound in the UnitySkills panel, covering the full editor-closed lifecycle. ## Core Features & Use Cases - Cold start and liveness triage: Launch a bound project with the -unityskills-coldstart marker so the REST server force-starts, and diagnose editor state via the UnitySkills registry before retrying. - Headless tests and 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: Invoke project-defined static build methods with target, output path, versioning, and dirty-worktree guards. - Use Case: A CI-style workflow needs a full regression run overnight: the agent verifies cli_config.json is enabled, confirms the editor version is installed, runs unity test with a timeout and JSON output, and reports failures from exit code 6. ## Quick Start Check that Library/UnitySkills/cli_config.json exists with enabled:true, then ask the agent to cold-start the bound Unity project and run its EditMode tests headlessly with a timeout.