What problem does it solve? AI agents working with Unity projects need to observe and drive the Unity Editor without parsing raw scene YAML files. This Skill exposes structured operations for reading editor state, tracking persistent scene and file changes, driving Play Mode, and executing menu commands. ## Core Features & Use Cases - Editor State Observation: Query play/pause/compile state, selection, full editor context, tags, and layers through structured responses. - Play Mode Control: Enter, pause, step frame-by-frame, capture runtime errors and screenshots, and inspect live GameObject state during Play Mode. - Change Tracking: Read a persistent change journal via cursor-based polling to detect scene and asset modifications across domain reloads. - Use Case: After a user edits the Unity project externally, call editor_get_changes with the saved cursor to see what changed, then use editor_playmode_inspect to verify a GameObject's runtime transform during Play Mode. ## Quick Start Ask the AI to check the Unity Editor state and list any scene changes since the last session before entering Play Mode.