unity-perception

Analyze Unity scenes, projects, and scripts with read-only inspection skills.

Updated Aug 18, 2026
One-click install
npx skills add https://github.com/ethanJPope/Our-Main-Hackathon-Game --skill unity-perception-ethanjpope
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: unity-perception
Source: https://github.com/ethanJPope/Our-Main-Hackathon-Game/tree/main/.agents/skills/unity-skills/skills/perception
Command: npx skills add https://github.com/ethanJPope/Our-Main-Hackathon-Game --skill unity-perception-ethanjpope

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Understanding an unfamiliar Unity scene or project before editing is slow and error-prone. This Skill provides read-only analysis of scene hierarchies, components, dependencies, and project stacks so AI agents and developers can gather context without risking unintended changes. ## Core Features & Use Cases - Scene Analysis & Health Checks: Summarize scenes, detect deep hierarchies, empty nodes, missing scripts, and performance hotspots with skills like scene_analyze, scene_health_check, and scene_find_hotspots. - Context Export & Dependency Analysis: Export structured hierarchy/component/reference data via scene_context, compare snapshots with scene_diff, and trace object or script dependencies with scene_dependency_analyze and script_dependency_graph. - Project Stack Detection: Detect render pipeline, input system, UI framework, packages, and test setup with project_stack_detect. - Use Case: Before refactoring a MonoBehaviour, run script_dependency_graph to see which scripts must change, then use scene_dependency_analyze to check which scene objects would break if a target object is removed. ## Quick Start Ask the AI to run scene_analyze on the current Unity scene to get a full diagnosis with findings, warnings, and recommended next steps.

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 before editing it?

Call scene_analyze for a combined scene and project diagnosis returning summary, findings, warnings, and recommendations. For a faster overview use scene_summarize, or scene_health_check for hygiene issues like missing scripts and deep hierarchies.

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

scene_summarize gives a fast overview of object counts and top components. scene_analyze provides broad diagnosis with findings and next-skill hints. scene_health_check focuses on red flags like duplicate names, empty nodes, and deep hierarchies.

How do I check what breaks if I delete a Unity scene object?

Use scene_dependency_analyze with the target object's path to see which in-scene references depend on it. Omit the savePath parameter to keep the operation fully read-only with results returned in the response.

Does scene_dependency_analyze modify my Unity project?

Only if you pass savePath, which creates a directory, writes a markdown report, and imports it as an asset. Without savePath it performs pure analysis and writes nothing to disk.

How do I find which scripts depend on a MonoBehaviour class?

Use script_dependency_graph with the script class name to get an N-hop dependency closure. Control depth with maxHops and add includeDetails for richer output showing which scripts must change together.

Can I export Unity scene context for another AI coding step?

Yes, scene_context exports structured hierarchy, components, and references, with options like rootPath for subtree export, includeValues for serialized fields, and includeCodeDeps for scene-to-code dependency mapping.