UnityOps Remote Control for Unity Editor

Problem

When a Unity project is open or needs to be driven by automation, manually clicking menus, waiting for compilation, saving scenes, and capturing screenshots makes batch workflows hard to reason about. Unity_Ops turns editor operations into a JSON protocol over a TCP Socket, so external scripts can query project paths, refresh assets, load scenes, create primitives, place FBX/Prefab assets, and capture fixed-angle screenshots. It fits cases where editor actions need to enter scripted workflows without repeated manual menu steps.

How It Works

The skill first checks the Unity process and project root, then synchronizes UnityOpsListener.cs and CoreOperations.cs. If files differ, it asks whether to keep the Skill version or the project version; after overwriting, it calls RefreshAssets. It then checks port 8888: if it is listening, work continues; if Unity is open but the service is not running, it asks for a manual start; if Unity is closed, it locates the Unity executable, starts it with -startServer, and polls until the port is ready.

Main commands include:
- Scene: SaveScene, NewScene, LoadScene
- Model: CreateModel, DeleteObject, PlaceAsset
- Screenshot: CaptureScreenshot with iso, top, or front
- Utilities: RefreshAssets, Manual, GetAssetPath

Limits

Extension commands must be created under the Unity project's Assets/Editor/UnityOps/ directory; the Skill's CS source files must not be modified from the Unity project. The skill is intended for controlled editor automation. Confirm before actions that force-close Unity, overwrite files, or risk losing unsaved scene data.