unity-cli (and others): com.unity.pipeline no longer ships the unity-pipeline skill — unity skill install --local instructions are stale #105

Plugin: 0.1.8-beta (main @ 3831ddb) · CLI: 1.0.0-beta.14 · com.unity.pipeline: 0.9.1-exp.1 (current latest on packages.unity.com) · Unity: 6000.6.7f1

Problem

Several skills say the package carries a unity-pipeline agent skill (.claude/skills/unity-pipeline/) to be mirrored with unity skill install <client> --local:

• skills/unity-cli/SKILL.md L68
• skills/unity-cli/references/integration-advanced.md L199 (and the unity skill disable unity-pipeline example at L248)
• skills/new-unity-project/SKILL.md L172–174 and L278 (tells the agent to read .claude/skills/unity-pipeline/SKILL.md inside Library/PackageCache/com.unity.pipeline@*)
• skills/create-2d-physics/SKILL.md L16, skills/optimize-web/SKILL.md L9, skills/unity-cli/SECURITY.md L19

Evidence

• com.unity.pipeline CHANGELOG, [0.9.0-exp.1], Changed: "Moved the unity-pipeline agent skill out of the package to the repository root."
• 0.9.1-exp.1 has no .claude/ folder (package root: CHANGELOG.md, CODEOWNERS, CodeGen, Documentation~, Editor, LICENSE.md, README.md, Runtime, Third Party Notices.md, package.json). A project still on 0.8.0-exp.1 does have .claude/skills/unity-pipeline/.
• With this plugin installed, unity skill install claude-code --local --dry-run only considers unity-cli (would-skip-plugin-provided); there is no unity-pipeline entry.

So agents run an install that adds nothing and look for a skill file that no longer exists.

Suggested fix

• Publish the unity-pipeline skill where agents can get it (e.g. in this plugin, since the package's repository root isn't visible to clients) and point these lines there;
• or remove the references / limit them to "com.unity.pipeline ≤ 0.8.x".

Related: #61 (its suggestion 3 also assumes unity-pipeline still lives in Library/PackageCache).