
from claude-unity-bridge19
Bridge Claude Code to the Unity Editor using a tested file-based command protocol and CLI to run tests, compile, control play mode, retrieve logs, and build pro
This skill provides a robust file-based bridge and CLI (unity-bridge) that lets an agent trigger Unity Editor operations from outside the editor. It handles UUID-based command tracking, atomic writes, polling, file locking, and cleanup so commands like running tests, compiling scripts, refreshing assets, retrieving console logs, and building projects execute deterministically and safely.
Use this when you need an agent to operate on a Unity project: run EditMode/PlayMode tests, compile scripts, fetch console logs, control play/pause/step in Play Mode, or run builds (including custom pipeline methods). It is meant for environments where Unity Editor is open and the project contains the required package.
Inferred compatibility: Claude Code and any agent capable of invoking the CLI or running Python scripts; suitable for agentic workflows that require reliable deterministic execution of editor commands.
Well-crafted Unity Editor bridge skill using a file-based protocol for deterministic, secure communication. SKILL.md is thorough with clear examples, error handling, and progressive disclosure. The CLI-based approach avoids variability between sessions. No security concerns — no network exposure, no hardcoded credentials, no destructive commands. Niche but valuable for game developers using Unity with Claude Code.
No scripts bundled in the DB entry; the actual CLI code is in a separate pip package. File-based protocol is a good security pattern — no ports, no network. Very clean SKILL.md with excellent documentation quality.