Download for MacApple silicon, macOS 14+
Skill

unity-package-management

@unity-technologies Updated 2026-10-23

Adds, removes, upgrades, and discovers Unity (UPM) packages from outside the Editor, with the Pipeline package commands first and a C# script as the fallback. Use for package installs, verifying package IDs and versions, or choosing which packages a game needs.

Install

With your agent

Install OMGSkills skill "unity-technologies/unity-agent-plugin:skills/unity-package-management" 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/unity-package-management ~/.claude/skills/unity-package-management

From README

Unity Package Management (Pipeline commands first, C# script as the fallback) Add, remove, upgrade, and discover UPM (Unity Package Manager) packages with the package commands of the project's Pipeline package, run through unity command. Only when no Editor can answer those commands, fall back to UnityEditor.PackageManager.Client driven headless from a script (see Fallback). Do not hand-edit Packages/manifest.json: the Package Manager resolves dependencies and compatible versions correctly, whereas manual edits routinely break resolution. This complements the unity-cli skill (editor , project creation, build/test), which documents unity command, unity status and unity pipeline . Use the package commands first The Pipeline package registers a package command group: add, remove, list, resolve, search and status. They need a running Editor whose project has com.unity.pipeline (add it with unity pipeline , then unity open, then wait with unity status --until-ready).