What problem does it solve?
When the Unity Editor is closed, REST-based automation cannot reach the project. This Skill guides AI agents in using the experimental Unity CLI to cold-start the bound Unity project, run headless tests, execute one-shot batch methods, and produce builds without opening the editor manually.
Core Features & Use Cases
- Cold Start & Lifecycle: Launch the bound Unity project with the
-unityskills-coldstart marker so the REST server starts automatically, with liveness triage via registry, lockfile, and CLI process checks.
- 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 structured JSON/NDJSON output and defined exit codes.
- Use Case: In a CI pipeline, cold-start a Unity project, run the full EditMode and PlayMode test suites headlessly, then produce a Windows build — all without human interaction with the editor.
Quick Start
Check the project's Library/UnitySkills/cli_config.json to confirm the Unity CLI is enabled, then use the configured cliPath to cold-start the project and wait for the REST health endpoint to respond.
