scene_skill

Overview

This skill manages Unity scenes with simple commands to create, load, save, inspect, and capture screenshots. It exposes operations to query scene metadata and traverse the hierarchy so you can automate scene workflows inside the Unity editor. Use it to script scene setup, validation, and visual previews.

How this skill works

The skill issues Unity editor actions to create or open scene assets, save current scene state, and return structured metadata about the active scene. It can enumerate root objects and build a nested hierarchy up to a configurable depth. For visual checks it captures a frame and writes a screenshot file to the project root.

When to use it

• Automate scene creation during project setup or CI
• Open scenes programmatically for batch processing or conversion
• Save or checkpoint the current scene before major changes
• Inspect scene metadata to validate build-ready state
• Capture screenshots for previews or automated QA reports

Best practices

• Always call scene_save before switching scenes to avoid data loss
• Use additive loading for overlays, UI, or multi-scene workflows
• Limit hierarchy traversal depth when scanning very large scenes to keep performance predictable
• Organize GameObjects under empty parents to make hierarchy outputs easier to read
• Use scene_get_info to confirm scene cleanliness (isDirty) before automated builds

Example use cases

• Create a new level asset and populate it via automation after scene_create
• Load multiple scenes additively to assemble a runtime test environment
• Run a pre-commit check that uses scene_get_info to ensure no unsaved changes
• Extract the hierarchy with scene_get_hierarchy for documentation or migration tooling
• Produce an image preview of a scene with scene_screenshot for art or QA review