sprite-editor
Edits Unity sprite rectangles, borders, pivots, outlines, and slicing by generating C# scripts. Use when the user works with sprite sheets or sprite slicing.
Install
With your agent
Install OMGSkills skill "unity-technologies/unity-agent-plugin:skills/sprite-editor" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.
Manual command
git clone https://github.com/Unity-Technologies/unity-agent-plugin /tmp/unity-agent-plugin && ln -s /tmp/unity-agent-plugin/skills/sprite-editor ~/.claude/skills/sprite-editorFrom README
Sprite Editor Sprite metadata (rects, borders, pivots, outlines) lives inside the importer, not in a file you can edit — reaching it means running C# through a live Editor. The unity-cli skill owns getting you there — installing the CLI, confirming a connected Editor, adding the project's com.unity.pipeline package, telling a genuinely absent Editor apart from one stuck in Safe Mode, and discovering the Editor's command catalog. Follow it first; don't re-derive any of it here. Two things it can't know for you: You need eval in particular, not just a reachable Editor. Confirm it appears in the catalog — its presence depends on the Pipeline package version, not on the CLI. Never hand-edit a .meta file to change sprite metadata. The importer owns that data and the capability checks below exist to prevent corruption, so an unreachable Editor is a stop, not a cue to improvise. Run C# through the connected Editor with the eval command.
More from this repo
audio-setup-mixers
Routes Audio Sources into existing Audio Mixer Groups, classifying each source by what it plays.
build-live-game
Builds and operates live games with Unity Services.
migrate-birp-to-urp
Plans, executes, and troubleshoots migration from the Built-in Render Pipeline to URP.