Skip to content
Closed
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion skills/using-unity/SKILL.md
Original file line number Diff line number Diff line change
Expand Up @@ -55,6 +55,6 @@ A skill may tell you to use, load or check for another skill by name, for exampl
- **ui-uitk**: Understands, edits, and generates Unity UI Toolkit UXML and USS with flex layouts. Use for requests involving UI Toolkit, UIElements, UIDocument, PanelSettings, custom elements, or UI runtime binding. File: `references/ui-uitk/ui-uitk.md`
- **unity-cli**: Controls Unity Editors and projects from the command line, including a running Editor. Make sure to use this skill when the user asks to install or manage Editors, licenses, or projects, set up version control, build, test, edit scenes, run C#, look up the scripting API or manual for the project's Unity version, or run any unity command. File: `references/unity-cli/unity-cli.md`
- **unity-package-management**: Adds, removes, upgrades, and finds Unity (UPM) packages from outside the Editor. Use for package installs, checking package IDs and versions, or choosing which packages a game needs. File: `references/unity-package-management/unity-package-management.md`
- **unity-pipeline**: Control a Unity Editor or Player via the unity-pipeline package. Compile, run tests, eval, method-reload code, enter Play Mode, capture screenshots. File: `references/unity-pipeline/unity-pipeline.md`
- **unity-pipeline**: Controls a Unity Editor or dev Player through the com.unity.pipeline package to compile, run tests, evaluate C#, method-reload code, enter Play Mode and capture screenshots. Make sure to use this skill when the user asks to drive, test, debug or inspect a running Unity Editor or Player from the command line. File: `references/unity-pipeline/unity-pipeline.md`
- **urp-postprocessing**: Sets up, configures, and debugs URP post-processing with the Volume framework. Use for bloom, tonemapping, color adjustments, depth of field, vignette, or other Volume overrides. File: `references/urp-postprocessing/urp-postprocessing.md`
- **validate-urp-render-graph-renderer-feature**: Reviews a Unity 6 URP ScriptableRendererFeature that uses the Render Graph API, checking resource wiring, material binding, execution structure, and best practices. Use to validate a renderer feature. File: `references/validate-urp-render-graph-renderer-feature/validate-urp-render-graph-renderer-feature.md`
6 changes: 3 additions & 3 deletions skills/using-unity/references/unity-pipeline/SECURITY.md
Original file line number Diff line number Diff line change
@@ -1,17 +1,17 @@
# Security notes: unity-pipeline

This skill has the agent run C# inside a Unity Editor or development Player the user already has running, through `unity command script eval`, `script eval_file`, `script run` and `script.methodreload reload`. 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 a Unity Editor or development Player the user already has running, through `unity command script eval`, `script run` and `script.methodreload reload`. 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 running Editor or development Player through `unity command script eval`, `script eval_file`, `script run` and `script.methodreload reload` | It only reaches an instance the user started, with the Pipeline package they installed, so it grants nothing they couldn't do in that Editor themselves. No code fetched from a remote source is run. The skill steers ad-hoc code into versioned project files run with `script run`, and keeps `script eval` for one-liners. |
| `SEC_POWER_CAP` | Runs C# in the user's running Editor or development Player through `unity command script eval`, `script run` and `script.methodreload reload` | It only reaches an instance the user started, with the Pipeline package they installed, so it grants nothing they couldn't do in that Editor themselves. No code fetched from a remote source is run. The skill steers ad-hoc code into versioned project files run with `script run`, and keeps `script eval` for one-liners. |

## Mitigations

- **Only the user's own instances.** Commands go to an Editor or development Player the user is running with the Pipeline package installed. Runtime commands need a development build; release Players have no Pipeline server.
- **No remote code.** The agent runs C# it writes for the user's task. Nothing downloaded from outside is executed.
- **Code lives in reviewable files.** Bulk work goes into scripts on disk run with `script run`, so the user can read and version what ran. `script eval` is reserved for short one-liners.
- **Compile-only check.** `script run --dry_run true` reports diagnostics without loading or running anything.
- **Compile-only check.** `script run --dry-run` reports diagnostics without loading or running anything.
- **Named commands first.** When a dedicated `unity command` covers a step, the skill uses it instead of running C#.
Loading
Loading