fix(package): Trim redundant generic content from tool skills

.agents/skills/uloop-clear-console/SKILL.md

@@ -20,22 +20,6 @@ uloop clear-console [--add-confirmation-message]
 |-----------|------|---------|-------------|
 | `--add-confirmation-message` | flag | - | Add confirmation message after clearing |
 
-## Global Options
-
-| Option | Description |
-|--------|-------------|
-| `--project-path <path>` | Optional. Use only when the target Unity project is not the current directory. |
-
-## Examples
-
-```bash
-# Clear console
-uloop clear-console
-
-# Clear with confirmation
-uloop clear-console --add-confirmation-message
-```
-
 ## Output
 
 Returns JSON with:

.agents/skills/uloop-compile/SKILL.md

@@ -22,25 +22,6 @@ uloop compile [--force-recompile] [--no-wait-for-domain-reload] [--stop-on-exter
 | `--no-wait-for-domain-reload` | flag | - | Return before Domain Reload completion |
 | `--stop-on-external-scene-changes` | flag | - | Stop before compilation if open Scene files changed externally instead of auto-reloading them |
 
-## Global Options
-
-| Option | Description |
-|--------|-------------|
-| `--project-path <path>` | Optional. Use only when the target Unity project is not the current directory. |
-
-## Examples
-
-```bash
-# Check compilation
-uloop compile
-
-# Start compilation without waiting for Domain Reload completion
-uloop compile --no-wait-for-domain-reload
-
-# Stop instead of auto-reloading externally changed open Scene files
-uloop compile --stop-on-external-scene-changes
-```
-
 ## Output
 
 Returns JSON:

.agents/skills/uloop-control-play-mode/SKILL.md

@@ -21,31 +21,6 @@ uloop control-play-mode [options]
 | `--action` | string | `Play` | Action to perform: `Play`, `Stop`, `Pause`, `Step` |
 | `--timeout-seconds` | integer | `180` | Maximum seconds to wait for the requested play mode state |
 
-## Global Options
-
-| Option | Description |
-|--------|-------------|
-| `--project-path <path>` | Optional. Use only when the target Unity project is not the current directory. |
-
-## Examples
-
-```bash
-# Start play mode
-uloop control-play-mode --action Play
-
-# Start play mode with a longer wait budget
-uloop control-play-mode --action Play --timeout-seconds 600
-
-# Stop play mode
-uloop control-play-mode --action Stop
-
-# Pause play mode
-uloop control-play-mode --action Pause
-
-# Advance exactly one frame while paused (Next Frame button)
-uloop control-play-mode --action Step
-```
-
 ## Output
 
 Returns JSON with the current play mode state:
@@ -59,5 +34,5 @@ Returns JSON with the current play mode state:
 ## Notes
 
 - Stop on an already-stopped Editor sets `Changed: false`, `WasAlreadyStopped: true`
-- Step is independent of `Time.timeScale`; requires PlayMode to be running
+- `Step` advances exactly one frame and leaves PlayMode paused (the Editor's Next Frame button); it is independent of `Time.timeScale` and requires PlayMode to be running
 - The command waits for the requested state before returning. Increase `--timeout-seconds` for projects with slow PlayMode entry.

.agents/skills/uloop-execute-dynamic-code/SKILL.md

@@ -13,24 +13,16 @@ For basic selected GameObject discovery or property inspection, use `find-game-o
 
 This tool can inspect reachable Unity state, such as GameObjects, components, public properties, static values, and method results. It cannot directly read local variables or intermediate calculations inside an already-running method. When those values matter, enable a source pause point on that line instead (`uloop enable-pause-point --file <file> --line <line>`, see the `uloop-wait-for-pause-point` skill): the hit response's `CapturedVariables` already contains the locals, parameters, and instance fields at that line, with no code edit or recompile. Do not try to reconstruct those values with execute-dynamic-code.
 
-## Workflow
-
-1. Read the relevant reference file(s) from the Code Examples section below
-2. Construct C# code based on the reference examples
-3. Execute with `--code` or `--code-file` using the active shell's quoting guidance
-4. Report the execution result
-
 ## Parameters
 
 - `--code '<code>'`: Inline C# statements to execute. Use direct statements only; `return` is optional, and `using` directives may appear at the top of the snippet.
 - `--code-file <path>`: Read the C# statements from a file instead of `--code`. Use this when the active shell or launcher cannot preserve inline code exactly. Exactly one of `--code` or `--code-file` is required; combining them is an error.
-- **Shell-specific quoting**: Read [references/playmode-automation-powershell.md](references/playmode-automation-powershell.md) for Windows/PowerShell multiline commands and [references/playmode-automation-zsh.md](references/playmode-automation-zsh.md) for zsh/macOS examples.
 - `--parameters {}` (advanced, optional): Pass a shell-quoted JSON object literal when reusing a snippet with varying data or when keeping values outside the code. Values are exposed as `parameters["param0"]`, `parameters["param1"]`, and so on. Omit this flag for most snippets. Do not pass a JSON string value such as `"{\"param0\":\"value\"}"`.
 - `--wait-for-domain-reload` (optional): Wait for Domain Reload recovery after snippets that intentionally trigger Unity script reload or import work. Omit this for normal inspection and editor-state workflows.
 
 ## Code Rules
 
-Write direct statements only — no class/namespace/method wrappers. Return is optional.
+Write direct statements from your own Unity API knowledge — no class/namespace/method wrappers. Return is optional.
 
 ```csharp
 using UnityEngine;
@@ -40,6 +32,26 @@ return x;
 
 Prefer terminal commands for file operations and keep snippets focused on Unity Editor state that existing uloop tools cannot inspect or change.
 
+## Shell Quoting
+
+- zsh/bash: single-quote the whole snippet so C# double quotes pass through unchanged: `--code 'return "hi";'`. For a single quote inside the snippet, close and reopen the shell string with `'\''`.
+- PowerShell 7 (`pwsh`): for multiline snippets, assign a single-quoted here-string (`$code = @'` ... `'@`) and pass `--code $code`. Inline, single-quoted arguments preserve C# double quotes; double an inner single quote (`''`).
+- Windows PowerShell 5.1 removes unescaped double quotes from native command arguments: escape them as `\"`, or prefer `--code-file`.
+- Pass `--parameters` as a single-quoted JSON object literal in both shells, for example `--parameters '{"param0":"value"}'`.
+- On Windows, multiline `--code` requires the native `uloop.exe`. If `(Get-Command uloop).Source` resolves to a legacy `.cmd` shim, run `uloop install` and open a new terminal.
+- If quoting still mangles the snippet, switch to `--code-file`.
+
+## When To Use Input Simulation Tools Instead
+
+Calling UI handlers or runtime methods directly from a snippet is the better choice for targeted automation, direct state control, or quick diagnostics. Switch to the dedicated input tools only when the input route itself is part of what you need to verify:
+
+| Scenario | Recommended tool | Why |
+|----------|------------------|-----|
+| Verify that a uGUI element responds through the real EventSystem pointer path | `simulate-mouse-ui` | Fires `PointerDown` / `PointerUp` / `PointerClick` / drag events through EventSystem raycasts instead of bypassing the UI input route. |
+| Test gameplay that reads `Mouse.current`, button state, delta, or scroll | `simulate-mouse-input` | Injects Input System mouse state into `Mouse.current` so game code observes it like player input. Requires the New Input System (`Input System Package (New)` or `Both`); when that is unavailable, prefer an execute-dynamic-code workaround instead of changing project settings just to use the tool. |
+| Jump straight to a known callback, invoke a method, inspect state, or set up a test precondition | `execute-dynamic-code` | Direct automation without reproducing the full input pipeline. |
+| Drive custom runtime behavior that does not map cleanly to the built-in input tools | `execute-dynamic-code` | Calls project-specific methods and prototypes one-off flows immediately. |
+
 ## Output
 
 Returns JSON:
@@ -54,34 +66,3 @@ Returns JSON:
 - `Diagnostics`: object[] — structured diagnostics; same shape as `CompilationErrors`, usually populated together with it
 
 On `Success: false`, inspect `CompilationErrors` first. If empty, read `ErrorMessage` (and `Logs` for extra context) — the failure may be a runtime exception, cancellation, or an "execution in progress" rejection, all of which return empty `CompilationErrors`. Both EditMode and PlayMode are supported targets — the snippet runs in whichever mode the Editor is currently in.
-
-## Code Examples by Category
-
-For detailed code examples, refer to these files:
-
-- **Prefab operations**: See [references/prefab-operations.md](references/prefab-operations.md)
-  - Create prefabs, instantiate, add components, modify properties
-- **Material operations**: See [references/material-operations.md](references/material-operations.md)
-  - Create materials, set shaders/textures, modify properties
-- **Asset operations**: See [references/asset-operations.md](references/asset-operations.md)
-  - Find/search assets, duplicate, move, rename, load
-- **ScriptableObject**: See [references/scriptableobject.md](references/scriptableobject.md)
-  - Create ScriptableObjects, modify with SerializedObject
-- **Scene operations**: See [references/scene-operations.md](references/scene-operations.md)
-  - Create/modify GameObjects, set parents, wire references, load scenes
-- **Batch operations**: See [references/batch-operations.md](references/batch-operations.md)
-  - Bulk modify objects, batch add/remove components, rename, layer/tag/material replacement
-- **Cleanup operations**: See [references/cleanup-operations.md](references/cleanup-operations.md)
-  - Detect broken scripts, missing references, unused materials, empty GameObjects
-- **Undo operations**: See [references/undo-operations.md](references/undo-operations.md)
-  - Undo-aware operations: RecordObject, AddComponent, SetParent, grouping
-- **Selection operations**: See [references/selection-operations.md](references/selection-operations.md)
-  - Get/set selection, multi-select, filter by type/editability
-- **PlayMode automation (PowerShell/Windows)**: See [references/playmode-automation-powershell.md](references/playmode-automation-powershell.md)
-  - Click UI buttons, invoke methods, set fields, tool combination workflows for PowerShell users
-- **PlayMode automation (zsh/macOS)**: See [references/playmode-automation-zsh.md](references/playmode-automation-zsh.md)
-  - Click UI buttons, invoke methods, set fields, tool combination workflows for zsh users
-- **PlayMode UI controls**: See [references/playmode-ui-controls.md](references/playmode-ui-controls.md)
-  - InputField, Slider, Toggle, Dropdown, drag & drop simulation, list all UI controls
-- **PlayMode inspection**: See [references/playmode-inspection.md](references/playmode-inspection.md)
-  - Scene info, game state via reflection, physics state, raycast checks, GameObject search, position/rotation