unity-perception

Analyze Unity scenes, project stacks, and scripts with read-only inspection tools.

Updated Jun 21, 2026
One-click install
npx skills add https://github.com/du-qwq/Shader-Writing-Architecture-and-Specifications --skill unity-perception-du-qwq
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: unity-perception
Source: https://github.com/du-qwq/Shader-Writing-Architecture-and-Specifications/tree/main/.agents/skills/unity-skills/skills/perception
Command: npx skills add https://github.com/du-qwq/Shader-Writing-Architecture-and-Specifications --skill unity-perception-du-qwq

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Before editing a Unity project, AI agents and developers often lack reliable context about scene structure, project stack, and script dependencies, leading to blind edits and broken references. This Skill provides read-only analysis of scenes, hierarchies, components, materials, and scripts so changes are made with full structural awareness. ## Core Features & Use Cases - Scene Analysis & Health Checks: Summarize scenes, detect deep hierarchies, empty nodes, missing scripts, and duplicate names with scene_analyze, scene_health_check, and scene_find_hotspots. - Context Export & Reports: Export structured hierarchy, components, and references via scene_context, or save a durable markdown report with scene_export_report. - Project & Script Insight: Detect render pipeline, input, UI, and packages with project_stack_detect, and map script dependency closures with script_dependency_graph. - Use Case: Before refactoring a MonoBehaviour, run script_dependency_graph to see every script affected, then use scene_dependency_analyze to check which scene objects reference it. ## Quick Start Ask the AI to analyze the current Unity scene and report any health issues, hotspots, and the detected project stack before making changes.

Frequently Asked Questions about unity-perception

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I analyze a Unity scene structure before editing?

Use scene_analyze for a combined diagnosis with findings and recommendations, or scene_summarize for a quick overview of object counts, hierarchy depth, and top components. Both are read-only and safe to run in any mode.

How to find script dependencies in a Unity project?

Use script_dependency_graph with a script class name to get an N-hop dependency closure showing which scripts must change together. For scene object references instead of code, use scene_dependency_analyze.

What is the difference between scene_summarize, scene_analyze, and scene_health_check?

scene_summarize gives a fast overview of counts and top components, scene_analyze provides broad diagnosis with warnings and next-step hints, and scene_health_check focuses on hygiene issues like missing scripts, duplicate names, and empty nodes.

Can these Unity analysis skills modify my scene?

No. Seventeen of the eighteen skills are marked ReadOnly, covering analysis, health checks, and context export. The only exception, scene_export_report, writes a markdown report file to disk but never alters scene objects.

How do I detect which render pipeline and packages a Unity project uses?

Run project_stack_detect with no parameters. It reports the render pipeline, input system, UI framework, installed packages, test setup, and folder conventions of the project.

When should I use scene_context instead of hierarchy_describe?

Use hierarchy_describe for a lightweight human-readable text tree. Use scene_context when another AI step needs structured hierarchy, components, references, and optional code dependencies as machine-consumable context.