ReddRadar
Agent skill
uloop-find-game-objects
Find GameObjects in the active scene by various criteria. Use when you need to: (1) Search for objects by name, regex, or path, (2) Find objects with specific components, tags, or layers, (3) Get currently selected GameObjects in Unity Editor. Returns matching GameObjects with hierarchy paths and components.
Install this agent skill to your Project
npx add-skill https://github.com/hatayama/unity-cli-loop/tree/main/Packages/src/Editor/Api/McpTools/FindGameObjects/Skill
SKILL.md
uloop find-game-objects
Find GameObjects with search criteria or get currently selected objects.
Usage
uloop find-game-objects [options]
Parameters
| Parameter | Type | Default | Description |
|---|---|---|---|
--name-pattern |
string | - | Name pattern to search |
--search-mode |
string | Exact |
Search mode: Exact, Path, Regex, Contains, Selected |
--required-components |
array | - | Required components |
--tag |
string | - | Tag filter |
--layer |
integer | - | Layer filter (layer number) |
--max-results |
integer | 20 |
Maximum number of results |
--include-inactive |
boolean | false |
Include inactive GameObjects |
--include-inherited-properties |
boolean | false |
Include inherited properties in results |
Search Modes
| Mode | Description |
|---|---|
Exact |
Exact name match (default) |
Path |
Hierarchy path search (e.g., Canvas/Button) |
Regex |
Regular expression pattern |
Contains |
Partial name match |
Selected |
Get currently selected GameObjects in Unity Editor |
Global Options
| Option | Description |
|---|---|
--project-path <path> |
Target a specific Unity project (mutually exclusive with --port) |
-p, --port <port> |
Specify Unity TCP port directly (mutually exclusive with --project-path) |
Examples
# Find by name
uloop find-game-objects --name-pattern "Player"
# Find with component
uloop find-game-objects --required-components Rigidbody
# Find by tag
uloop find-game-objects --tag "Enemy"
# Regex search
uloop find-game-objects --name-pattern "UI_.*" --search-mode Regex
# Get selected GameObjects
uloop find-game-objects --search-mode Selected
# Get selected including inactive
uloop find-game-objects --search-mode Selected --include-inactive
Output
Returns JSON with matching GameObjects.
For Selected mode with multiple objects, results are exported to file:
- Single selection: JSON response directly
- Multiple selection: File at
.uloop/outputs/FindGameObjectsResults/ - No selection: Empty results with message
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
hatayama/unity-cli-loop
uloop-simulate-mouse-ui
Simulate mouse click, long-press, and drag on PlayMode UI elements via EventSystem screen coordinates. Use when you need to: (1) Click buttons or interactive UI elements during PlayMode testing, (2) Drag UI elements from one position to another, (3) Hold a drag at a position for inspection before releasing, (4) Long-press UI elements that respond to sustained pointer-down. For game logic that reads Input System (e.g. WasPressedThisFrame), use simulate-mouse-input instead.
hatayama/unity-cli-loop
uloop-execute-menu-item
Execute Unity Editor menu commands programmatically. Use when you need to: (1) Trigger menu commands like save, build, or refresh, (2) Automate editor actions via menu paths, (3) Run custom menu items defined in project scripts.
hatayama/unity-cli-loop
uloop-simulate-keyboard
Simulate keyboard key input in PlayMode via Input System. Use when you need to: (1) Press game control keys like WASD, Space, or Shift during PlayMode, (2) Hold keys down for continuous movement or actions, (3) Combine multiple held keys for complex input like Shift+W for sprint.
hatayama/unity-cli-loop
uloop-run-tests
Execute Unity Test Runner and get detailed results. Use when you need to: (1) Run EditMode or PlayMode unit tests, (2) Verify code changes pass all tests, (3) Diagnose test failures with error messages and stack traces. Auto-saves NUnit XML results on failure.
hatayama/unity-cli-loop
uloop-control-play-mode
Control Unity Editor play mode (play/stop/pause). Use when you need to: (1) Start play mode to test game behavior, (2) Stop play mode to return to edit mode, (3) Pause play mode for frame-by-frame inspection.
hatayama/unity-cli-loop
uloop-clear-console
Clear all Unity Console log entries. Use when you need to: (1) Clear console before running tests or compilation, (2) Start a fresh debugging session, (3) Remove noisy logs to isolate specific output.
Didn't find tool you were looking for?