uloop-get-hierarchy — Claude Code skill: Unity scene hierarchy
uloop-get-hierarchy pulls a Unity scene hierarchy as a tree, either the whole scene, from a root path, or from what is currently selected. Useful when an agent has to know how the scene is put together.
MIT 1 installs ★ 602 updated 2026-10-29
npx skills add hatayama/unity-cli-loop --skill uloop-get-hierarchy -a claude-codeWhat uloop-get-hierarchy does
Under the hood it calls uloop get-hierarchy and dumps the scene tree. Depth is capped with --max-depth, and the default -1 means no cap.
Components and inactive objects come along unless you pass --no-include-components or --no-include-inactive. Add --include-paths for full paths; --use-components-lut accepts auto, true or false. For details or component values on the selected object, the skill points you at find-game-objects --search-mode selected instead.
The tree is not part of the command response. You get Message and HierarchyFilePath, while the actual payload sits in the file at that path, so the agent has to open it. One gotcha: --use-selection makes --root-path irrelevant, so pick one of the two up front.
What it helps with
- see how the whole scene is nested
- dump the subtree under the selected object
- export the tree without inactive objects
- get full paths for objects in the scene
- limit traversal depth on a big scene
Example prompts for the agent
- Show me the scene hierarchy under
Canvas, two levels deep - Dump the tree under what I have selected, skip inactive objects
- I need full paths for every object, run
uloop get-hierarchy --include-paths
How to install uloop-get-hierarchy
1Skills CLI (Vercel)
npx skills add hatayama/unity-cli-loop --skill uloop-get-hierarchy -a claude-code2Manually: put the files in place
~/.claude/skills/uloop-get-hierarchy/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/uloop-get-hierarchy/
1Skills CLI (Vercel)
npx skills add hatayama/unity-cli-loop --skill uloop-get-hierarchy -a codex2Manually: put the files in place
.agents/skills/uloop-get-hierarchy/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add hatayama/unity-cli-loop --skill uloop-get-hierarchy -a cursor2Manually: put the files in place
.cursor/skills/uloop-get-hierarchy/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install hatayama/unity-cli-loop .claude/skills/uloop-get-hierarchy2Manually: put the files in place
.github/skills/uloop-get-hierarchy/SKILL.md1Skills CLI (Vercel)
npx skills add hatayama/unity-cli-loop --skill uloop-get-hierarchy -a gemini-cli2Platform CLI
gemini skills install https://github.com/hatayama/unity-cli-loop --path .claude/skills/uloop-get-hierarchyManually: put the files in place
.devin/skills/uloop-get-hierarchy/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add hatayama/unity-cli-loop --skill uloop-get-hierarchy -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about uloop-get-hierarchy
How to install uloop-get-hierarchy in Claude Code?
Run npx skills add hatayama/unity-cli-loop --skill uloop-get-hierarchy -a claude-code. The skill file then sits at ~/.claude/skills/uloop-get-hierarchy/SKILL.md.
What does uloop-get-hierarchy do?
It runs uloop get-hierarchy and saves the Unity scene tree to a file, returning the path to it. Options cover the root object, depth, components and inactive objects.
How is it different from find-game-objects?
This one gives you the parent-child structure. For component properties and details on the selected object, the skill recommends find-game-objects --search-mode selected.
Source text
SKILL.md · MIT
--- name: uloop-get-hierarchy toolName: get-hierarchy description: "Get the Unity scene hierarchy as a structured tree. Use for parent-child structure, descendants, roots, or subtrees under objects the user currently selected." --- # uloop get-hierarchy Get Unity Hierarchy structure from the whole scene, a root path, or selected Hierarchy objects. Use this for hierarchy structure, especially descendants under the current selection. Use `find-game-objects --search-mode selected` when you need selected object details or component properties. ## Usage ```bash uloop get-hierarchy [options] ``` ## Parameters | Parameter | Type | Default | Description | |-----------|------|---------|-------------| | `--root-path` | string | - | Root GameObject path to start from | | `--max-depth` | integer | `-1` | Maximum depth (-1 for unlimited) | | `--no-include-components` | flag | - | Exclude component information | | `--no-include-inactive` | flag | - | Exclude inactive GameObjects | | `--include-paths` | flag | - | Include full path information | | `--use-components-lut` | string | `auto` | Use LUT for components (`auto`, `true`, `false`) | | `--use-selection` | flag | - | Use selected GameObject(s) as root(s). When set, `--root-path` is ignored. | ## Output Returns JSON with: - `Message` (string): Human-readable guidance pointing at the saved file - `HierarchyFilePath` (string): Filesystem path to the JSON file that contains the actual hierarchy data The hierarchy itself is **not** in the response — it is written to the file at `HierarchyFilePath`. Open that file to read the `Context` and `Hierarchy` payload (GameObject tree, components, etc.).
© hatayama · MIT · hatayama/unity-cli-loop