sync: align skills catalog with Unity-Technologies/skills

[unity-cli-skill-sync]

Aligns this plugin's skills/ with the approved catalog in Unity-Technologies/skills.

Opened automatically by the release-cli pipeline after the CLI v1.0.0-beta.10 release. Unity-Technologies/skills is the source of truth; this repo's skills/ follows its skills/ byte-for-byte.

Release: https://github.com/Unity-Technologies/unity-hub/releases/tag/cli-v1.0.0-beta.10

[ankerr]

Review: safe to merge — no blocking issues

Rather than line-reading the prose, I verified this PR's actual central claim. Git blob SHAs are content hashes, so comparing them between the two repos is a byte-for-byte proof:

Check	Result
skills/ vs Unity-Technologies/skills@main after this PR	199 blobs / 199 paths / 199 identical SHAs. Zero divergence.
Is 0 deletions correct?	Yes. main differs from upstream by exactly these 10 missing files — zero extra, zero modified. No stale or drifted content existed to remove, so a purely additive sync is the right shape.
Manifest changes owed?	None. All four manifests checked (.claude-plugin/plugin.json, .codex-plugin/plugin.json, both marketplace.json) — none enumerates individual skills or files, and Codex uses a directory-wide "skills": "./skills/". These files add docs/evals to three skills that already had a SKILL.md, so no new skill is being registered.
Do the new files' internal references resolve?	All of them. The 4 file:// paths in the eval configs (../SKILL.md, ../references/{init-and-login,voice-channels,text-chat}.md) exist; the levelplay README's "What's in this folder" listing of 12 references/ files matches the tree exactly; the IAP README's references/pre-check.md exists.
CI	Green — Cycode SAST / Secrets / Vulnerable Dependencies, 0 findings each.

Three observations — all upstream-owned, none blocking

None of these should be fixed in this PR. Patching here would break the byte-for-byte invariant the pipeline enforces, and the next sync would revert it. These belong in Unity-Technologies/skills:

1. Stale version badge. levelplay-unity-integration/README.md carries badge/version-0.7.0, while the CHANGELOG.md added in this same PR tops out at v0.10.0 — 2026-08-21. Cosmetic, but this PR is what makes the contradiction visible in this repo, so it's a natural moment to file it upstream.

2. An internal hostname is published to a public repo. Both repos are public, and evals/.env.example + evals/README.md cite uai-litellm.internal.unity.com. Low severity and not new — upstream already publishes the identical bytes — but this PR does duplicate it into a second public repo. Credential handling itself is correct: the value is the placeholder your-litellm-api-key-here, .env is gitignored, and the secrets scan is clean.

3. Developer-only eval harness ships in the distributed plugin payload. Because Codex takes the whole ./skills/ tree, the 6 promptfoo files go out to plugin consumers. They're inert — no SKILL.md, and nested inside an existing skill, so nothing will mistake evals/ for a skill — but setup-vivox-voice-chat is the only 1 of 31 skills carrying an evals/ dir. Worth a catalog-policy decision upstream on whether eval scaffolding belongs in the shipped payload. The same sparseness applies to the other two files (only 4 of 31 skills have a README, 2 of 31 a CHANGELOG), so the catalog's ancillary-file coverage is uneven — this PR faithfully mirrors that unevenness rather than causing it.

One process note, independent of the diff: this is bot-authored with a single unsigned commit. If this repo expects signed commits, that's a release-cli pipeline-side question.

🤖 Generated with Claude Code