sprite-editor
An agent skill by Unity-Technologies, from Unity-Technologies/unity-agent-plugin. Tags: assets, automation, editor, sprites, validation.
What it does
Edits Unity sprite properties by generating C# editor scripts using ISpriteEditorDataProvider APIs. Handles sprite rectangles, borders, pivots, outlines, and slicing operations (automatic, grid, isometric). Use when working with sprite assets, sprite sheets, texture atlases, or sprite slicing.
Install
With the skills CLI, which installs into Claude Code, Codex, Cursor and other agents:
npx skills add Unity-Technologies/unity-agent-plugin --skill sprite-editor
Or copy the skill folder into Claude Code's skills directory by hand (~/.claude/skills for every project, or .claude/skills inside one):
git clone --depth 1 https://github.com/Unity-Technologies/unity-agent-plugin
cp -r unity-agent-plugin/skills/sprite-editor ~/.claude/skills/sprite-editor
Safety box score
Grade C, moderate risk: 21 of 100 risk points, rated 2026-10-14. The grade rates what the skill and its scripts can reach on the machine of whoever installs it, across eight categories from shell execution to secrets access. How the score works.
This skill runs C# inside the user’s open Unity Editor to edit sprite importer metadata such as rects, pivots, borders, outlines, and slicing. The main risk is broad in-editor code execution with the ability to bulk rewrite or delete sprite definitions in project assets.
| Category | Level | Why |
|---|---|---|
| Code & shell execution | 3 (high) | It explicitly runs code with `unity command eval --code '<snippet>'` and says to "Run C# through the connected Editor"; that is live code execution in the Unity Editor. |
| Network access | 0 (none) | The shipped files do not download from or send data to remote hosts; `SKILL.md` and the helper scripts only describe local Unity Editor and asset operations. |
| Filesystem reach | 1 (low) | The skill writes sprite metadata back through importer APIs like `SetSpriteRects(...)`, `SetOutlines(...)`, `Apply()`, and `SaveAndReimport()`, but the scope is the project/importer rather than outside the working tree. |
| Secrets & credentials | 0 (none) | No code or instructions access tokens, keys, passwords, `.env` files, browser sessions, or CLI logins. |
| Privilege & persistence | 0 (none) | There is no sudo, global install, service registration, shell startup editing, or OS-level privilege change in the shipped files. |
| Instruction hijack surface | 0 (none) | The files do not tell the agent to ignore rules, hide actions, or follow remote instructions; instead they emphasize capability checks and avoiding manual `.meta` edits. |
| Irreversible actions | 2 (moderate) | The slicing helpers can bulk replace or delete sprite rects, e.g. `AddNewSpriteMethod.DeleteAll` and `spriteDataProvider.SetSpriteRects(newRects.ToArray())`, which is a real destructive edit even though it stays inside the Unity project. |
| Transparency | 0 (none) | All reviewed files are plain text source and markdown; there are no binaries, embedded blobs, or runtime-downloaded code in the skill itself. |
Before installing
- Read `SKILL.md` and `references/templates.md` to confirm you’re comfortable with live C# execution in the open Editor.
- Test on a copy of the Unity project first; slicing can use `DeleteAll` and rewrite sprite metadata.
- Verify the target importer supports the needed capability (`EditSpriteRect`, `EditPivot`, `CreateAndDeleteSprite`) before relying on the helpers.
- Inspect any generated `eval` snippet before running it, since the skill executes C# directly in your session.
Rated 2026-10-14 by an automated review of 14 files from the skill's repository.
Source
- Repository
- Unity-Technologies/unity-agent-plugin (all skills from this repository)
- Path
- skills/sprite-editor/SKILL.md
- Branch
- main
- Updated
- 2026-09-22
Related skills
- manage-sprite-atlas — Manage SpriteAtlas using prebuild pipeline with IPreprocessBuildWithReport (DEFAULT approach).
- cli-for-agents — Designs or reviews CLIs so coding agents can run them reliably: non-interactive flags, layered --help with examples, stdin/pipelines, fast actionable errors.
- control-cli — Build or adapt a local harness to drive, inspect, and profile an interactive CLI or TUI without external services.
- control-ui — Build or adapt a local browser/CDP harness to drive and inspect a web, IDE, or Electron UI.
- create-verification-skill — Generate a project-local verification skill that drives your app the way a user does — any language, framework, or platform.
- principle-encode-lessons-in-structure — Apply when you catch yourself writing the same instruction a second time, or notice a recurring correction.