usd-editor

Edit USD ASCII files with minimal changes while preserving stage structure.

60|8|Updated Dec 23, 2025
One-click install
npx skills add https://github.com/tomkrikorian/visionOSAgents --skill usd-editor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: usd-editor
Source: https://github.com/tomkrikorian/visionOSAgents/tree/main/skills/usd-editor
Command: npx skills add https://github.com/tomkrikorian/visionOSAgents --skill usd-editor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Editing USD ASCII (.usda) files by hand is error-prone and risks breaking stage structure, composition arcs, and prim relationships. This Skill offers a safe, minimal-edit workflow that preserves formatting, respects existing composition, and reduces diffs.

Core Features & Use Cases

  • Inspect the stage to identify root prims, scopes, and relevant paths before making changes.
  • Choose the correct specifier (def vs over) to avoid unnecessary redefinitions.
  • Edit only the minimal set of attributes or relationships, preserving xformOpOrder and formatting.
  • Respect composition arcs (sublayers, references, payloads, and variants) unless explicitly requested.
  • Validate paths and relationships to ensure targets exist and types match, minimizing breakages.

Quick Start

  1. Locate the prim path you need to edit (e.g., </Root/Model>).
  2. Decide whether to use over to modify or def to create a new prim.
  3. Apply the smallest change necessary (attribute value, rel target, or child prim) and update xformOpOrder if you add transforms.
  4. Re-check touched paths, references, and any affected composition arcs.

Frequently Asked Questions about usd-editor

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

FAQPage Schema
How do I safely edit USD ASCII files without breaking stage composition?

To safely edit USD ASCII (.usda) files, apply minimal changes that preserve stage structure, respect existing composition arcs like sublayers and references, and maintain xformOporder to prevent scene breakage.

When should I use 'def' versus 'over' when editing prims in a .usda file?

Use the 'over' specifier to modify existing prim attributes or relationships without redefining them, and use 'def' only when creating a new prim to avoid unnecessary redefinitions that can alter composition.

How do I update transform operations in USD without corrupting xformOpOrder?

When adding transforms to a USD prim, apply the smallest change necessary and explicitly update the xformOpOrder attribute to include the new transform operation, ensuring the stage evaluates the hierarchy correctly.

What is the best way to modify composition arcs like references and payloads in USD?

The best way to modify composition arcs is to respect existing sublayers, references, payloads, and variants unless explicitly requested otherwise, validating that all target paths exist and types match to minimize stage breakages.

Why does editing a prim relationship in USD break my scene?

Editing a prim relationship in USD breaks the scene if the target path no longer exists or the types mismatch; validating paths and relationships before applying changes ensures targets resolve correctly.

Can I edit USD files manually without affecting the existing formatting and diffs?

Yes, you can edit USD files manually with minimal changes by preserving existing formatting, touching only the necessary attributes, and respecting the current composition to keep diffs clean and reduce errors.