`unity-cli` skill ships in three channels that drift out of sync with the installed CLI

[uayten]

Problem

The same unity-cli skill reaches an agent through three independent channels: this plugin (unity:unity-cli), unity skill install <client> --local (embedded in the CLI binary), and npx skills add Unity-Technologies/skills (suggested by the CLI on every install). Each updates on its own schedule, separately from the unity binary itself, so an agent can end up following instructions written for a different CLI version.

Repro

Windows 11, Claude Code, plugin 0.1.6-beta, CLI 1.0.0-beta.8.

The plugin's skill says to pass --caller plugin --skill <name> on every unity command. On CLI 1.0.0-beta.8 that fails:

unity command console_status --caller plugin --skill unity-cli
Error: Invalid arguments for console_status:
  console_status has no parameter --caller.
  console_status has no parameter --skill.

Updating to 1.0.0-beta.11 fixed it, but nothing told the agent or the user that the versions didn't match.

After running unity skill install claude-code --local, the project also has a second unity-cli skill that differs from the plugin's. Claude Code can't disable a single plugin skill, so the only way to drop the plugin's copy is to uninstall the whole plugin.

Suggestions

1. Single source of truth. Have the plugin ship a thin unity-cli stub that points the agent at the binary's own docs (e.g. unity skill show), instead of a static copy.
2. Declare compatibility. State the minimum CLI version in the skill, so the agent can compare it with unity --version and suggest unity self-update up front.
3. Detect the plugin. When the plugin is present, unity skill install should install only what's missing (unity-pipeline, which is hidden in Library/PackageCache) rather than a second unity-cli.
4. One recommended channel. Pick one of plugin / skill install / npx skills add as the primary path and document the others as alternatives.
5. Clarify the docs. The Claude Code plugin page doesn't say that the plugin installs neither the CLI nor com.unity.pipeline, which makes it look like there are two CLIs.