chore: publish 12 skills (asset-transformer-toolkit, audio-setup-mixers, build-live-game, +9)

skills/asset-transformer-toolkit/SECURITY.md

@@ -1,6 +1,6 @@
 # Security notes: asset-transformer-toolkit
 
-This skill has the agent write C# and run it inside the user's live Unity Editor, to create and edit Asset Transformer RuleSets. It doesn't say which command runs the code; with the `unity` CLI that is `unity command eval`. Automated skill scanners flag running generated code as a powerful capability. It is intentional, and it is limited by the safeguards below.
+This skill has the agent write C# and run it inside the user's live Unity Editor, to create and edit Asset Transformer RuleSets. It doesn't say which command runs the code; with the `unity` CLI that is `unity command script eval`. Automated skill scanners flag running generated code as a powerful capability. It is intentional, and it is limited by the safeguards below.
 
 ## Accepted risks
 

skills/audio-setup-mixers/SECURITY.md

@@ -1,16 +1,16 @@
 # Security notes: audio-setup-mixers
 
-This skill has the agent run C# inside the user's open Unity Editor through `unity command eval`. Automated skill scanners flag that as a powerful capability. It is intentional, and it is limited by the safeguards below.
+This skill has the agent run C# inside the user's open Unity Editor through `unity command script eval`. Automated skill scanners flag that as a powerful capability. It is intentional, and it is limited by the safeguards below.
 
 ## Accepted risks
 
 | Risk | Capability | Why it is accepted |
 |---|---|---|
-| `SEC_POWER_CAP` | Runs C# in the user's open Editor through `unity command eval` | It only reaches the Editor the user already has open, on their own machine, as that user, so it grants nothing they couldn't do themselves. `eval` sits behind the Pipeline capability gate. No code fetched from a remote source is run. Where a named `unity command` covers a step, the skill uses that instead of `eval`. |
+| `SEC_POWER_CAP` | Runs C# in the user's open Editor through `unity command script eval` | It only reaches the Editor the user already has open, on their own machine, as that user, so it grants nothing they couldn't do themselves. `script eval` sits behind the Pipeline capability gate. No code fetched from a remote source is run. Where a named `unity command` covers a step, the skill uses that instead of `script eval`. |
 
 ## Mitigations
 
-- **Only the user's own Editor.** `unity command eval` talks to the Editor open on this machine. It can't reach another machine or another user's Editor.
-- **Capability gate.** `eval` is only available when the project's Pipeline package provides it.
+- **Only the user's own Editor.** `unity command script eval` talks to the Editor open on this machine. It can't reach another machine or another user's Editor.
+- **Capability gate.** `script eval` is only available when the project's Pipeline package provides it.
 - **No remote code.** The agent runs C# it writes from this skill's own recipes. Nothing downloaded from outside is executed.
-- **Named commands first.** When a dedicated `unity command` covers a step, the skill uses it instead of `eval`.
+- **Named commands first.** When a dedicated `unity command` covers a step, the skill uses it instead of `script eval`.

skills/audio-setup-mixers/SKILL.md

@@ -30,23 +30,23 @@ re-derive any of it here.
 
 Two things it can't know for you:
 
-- **You need `eval` in particular**, not just a reachable Editor. Confirm it appears in the
+- **You need `script eval` in particular**, not just a reachable Editor. Confirm it appears in the
   catalog. Its presence depends on the Pipeline package version, not on the CLI, so a
   healthy install can still lack it — if it's missing, say so and stop.
 - **Do not fall back to editing `.mixer` files by hand.** Mixer routing is not safely
   authorable blind, so an unreachable Editor is a stop, not a cue to improvise.
 
-Once `eval` is available, that is how each C# step below runs.
+Once `script eval` is available, that is how each C# step below runs.
 
-Run C# through the connected Editor with the `eval` command. Discover its parameter shape
+Run C# through the connected Editor with the `script eval` command. Discover its parameter shape
 from `unity command --format json` rather than assuming one — the inline form is
-`unity command eval --caller plugin --skill audio-setup-mixers --code '<snippet>'`, and some Pipeline versions also register
-`eval_file` for running a snippet from a file. **Check the catalog before reaching for
-`eval_file`; it is frequently absent.** `unity command` defaults to a 30 second timeout.
+`unity command script eval --caller plugin --skill audio-setup-mixers --code '<snippet>'`, and some Pipeline versions also register
+`script eval_file` for running a snippet from a file. **Check the catalog before reaching for
+`script eval_file`; it is frequently absent.** `unity command` defaults to a 30 second timeout.
 
-### Passing C# to `eval`
+### Passing C# to `script eval`
 
-`eval` compiles a **statement block, not a file**. Two consequences, both of which cause a
+`script eval` compiles a **statement block, not a file**. Two consequences, both of which cause a
 compile error rather than a warning:
 
 - **No `using` directives.** The compiler reads `using UnityEngine;` as a resource-disposal
@@ -55,7 +55,7 @@ compile error rather than a warning:
   (`CS0246` / `CS0103`), and a bare `Object` is ambiguous with `object` (`CS0104`).
 
 Where a snippet below is written as a file — with usings, for readability, or because it is
-meant to be saved into the project — qualify the types before passing it to `eval`.
+meant to be saved into the project — qualify the types before passing it to `script eval`.
 
 ## Step 1: Pre-flight
 If the user hasn't explicitly asked for Audio Mixers, confirm that they want to proceed with setting them up.

skills/audio-setup-mixers/references/api.md

@@ -27,7 +27,7 @@ to add any missing groups (two clicks in a window they already have open), and t
 routing itself. The tedious part — walking dozens of Audio Sources and classifying them — is the
 part that was worth automating anyway.
 
-All snippets below are written for `unity command eval --caller plugin --skill audio-setup-mixers --code '<snippet>'`: fully qualified, no
+All snippets below are written for `unity command script eval --caller plugin --skill audio-setup-mixers --code '<snippet>'`: fully qualified, no
 `using` directives, returning their result rather than logging it.
 
 ## Inventory the project's mixers and their groups