Uloop Get Hierarchy
Apps & Automationuloop-get-hierarchyUloop Get Hierarchy is an Agent Skill for apps & automation published in the kurotu/VRCQuestTools repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Get the Unity scene hierarchy as a structured tree. Use for parent-child structure, descendants, roots, or subtrees under objects the user currently selected.
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/kurotu/VRCQuestTools/blob/HEAD/.claude/skills/uloop-get-hierarchy/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/uloop-get-hierarchy, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
npx --yes [email protected] 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
npx --yes [email protected] 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) |
--include-components | boolean | true | Include component information |
--include-inactive | boolean | true | Include inactive GameObjects |
--include-paths | boolean | false | Include full path information |
--use-components-lut | string | auto | Use LUT for components (auto, true, false) |
--use-selection | boolean | false | Use selected GameObject(s) as root(s). When true, --root-path is ignored. |
Global Options
| Option | Description |
|---|---|
--project-path <path> | Optional. Use only when the target Unity project is not the current directory. |
Examples
# Get entire hierarchy
npx --yes [email protected] get-hierarchy
# Get hierarchy from specific root
npx --yes [email protected] get-hierarchy --root-path "Canvas/UI"
# Limit depth
npx --yes [email protected] get-hierarchy --max-depth 2
# Without components
npx --yes [email protected] get-hierarchy --include-components false
# Get hierarchy from currently selected GameObjects
npx --yes [email protected] get-hierarchy --use-selection
Output
Returns JSON with:
message(string): Human-readable guidance pointing at the saved filehierarchyFilePath(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.).