SkillsAdd

tomkrikorian/visionosagents

usd-editor

Guide for modifying USD ASCII (.usda) files and command-line USD workflows, including prims, properties, composition arcs, variants, transforms, usdcat, usdchecker, usdrecord, usdtree, usdzip, and usdedit.

First seen Jan 29, 2026

Installation

$ npx skills add tomkrikorian/visionosagents --skill usd-editor
View on skills.sh ↗ GitHub repository ↗

Summary

  • Guide for modifying USD ASCII (.usda) files and command-line USD workflows, including prims, properties, composition arcs, variants, transforms, usdcat, usdchecker, usdrecord, usdtree, usdzip, and usdedit.
  • Use when editing or reviewing .usda files by hand, validating USD/USDZ assets, or working in an asset pipeline outside runtime Swift USDKit.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

agent-browser Shared topics
vercel-labs/agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, includ…

810.4K installs
vercel-react-best-practices Shared topics
vercel-labs/agent-skills 697.8K installs
web-design-guidelines Shared topics
vercel-labs/agent-skills

Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "chec…

617.3K installs
microsoft-foundry Shared topics
microsoft/azure-skills

Build, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and …

576.5K installs
azure-hosted-copilot-sdk Shared topics
microsoft/azure-skills 440.4K installs
azure-enterprise-infra-planner Shared topics
microsoft/azure-skills

Architect and provision enterprise Azure infrastructure from workload descriptions. For cloud a…

402.8K installs

Also in this package

Other skills from tomkrikorian/visionosagents · top by installs.

npx skills add tomkrikorian/visionosagents
realitykit-visionos-developer 102 arkit-visionos-developer 85 spatial-swiftui-developer 75 coding-standards-enforcer 66 shadergraph-editor 48 shareplay-developer 45 visionos-widgetkit-developer 33 spatial-app-architecture 30 visionos-immersive-media-developer 27 tkr-skill-writer 18

Browse all from tomkrikorian/visionosagents

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 60
License LICENSE
Default branch main
Open issues 0
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 4,605 B
  • docs SUMMARY.md 364 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 47 installs

SKILL.md

USD Editor

Quick Start

Use this skill for minimal, text-level USD or USDA edits and command-line USD inspection, conversion, packaging, rendering, and validation. Keep the change small and preserve existing composition unless the task explicitly says otherwise.

When authored Reality Composer Pro or USD content owns the scene, geometry, transform, animation, or material, keep that authored surface as the source of truth. Use Swift and RealityKit to load or adjust runtime state; do not recreate authored USD content in Swift unless the request is explicitly procedural.

If Swift code needs to open, edit, observe, or export stages in-process with USDStage, USDPrim, or USDLayer, switch to $usdkit-runtime-developer.

If the change is material- or shader-specific for RealityKit, prefer shadergraph-editor.

Load References When

Reference When to Use
[usd-syntax](references/usd-syntax.md) When you need a refresher on .usda syntax, values, and path formats.
[prims-properties](references/prims-properties.md) When adding or editing prims, attributes, or relationships.
[composition-variants](references/composition-variants.md) When touching sublayers, references, payloads, or variant sets.
[transforms-units](references/transforms-units.md) When editing transforms, xformOps, or stage units and up-axis metadata.
[time-samples](references/time-samples.md) When modifying animated or time-sampled properties.
[command-line-tools](references/command-line-tools.md) When you need a quick reference for common USD command-line tools.
[usdcat](references/usdcat.md) When converting, flattening, or inspecting USD files.
[usdchecker](references/usdchecker.md) When validating USD or USDZ assets, including RealityKit-focused checks.
[usdrecord](references/usdrecord.md) When rendering images from USD files.
[usdtree](references/usdtree.md) When inspecting the prim hierarchy of a USD file.
[usdzip](references/usdzip.md) When creating or inspecting USDZ packages.
[usdedit](references/usdedit.md) When you need the official text-editing workflow for a USD-readable file.
[visionos-runtime-loading.md](references/visionos-runtime-loading.md) When the question is how authored USD or USDZ actually loads and behaves in a visionOS app.
[apple-runtime-boundaries.md](references/apple-runtime-boundaries.md) When deciding whether to edit authored USD / Reality Composer Pro content, load it through RealityKit, or validate it for Apple platforms.

Workflow

  1. Identify the owner: authored USD / Reality Composer Pro asset, package

resource, or runtime-only Swift-generated content.

  1. Inspect the stage with usdtree, usdcat --loadOnly, or usdcat --flatten

before editing, depending on the risk.

  1. Locate the exact prim path and layer that owns the opinion.
  2. Choose over, def, or a list edit deliberately.
  3. Apply the minimum change needed.
  4. Re-check paths, transforms, or composition edges that were touched.
  5. Run the narrowest validation tool that matches the change, then run

usdchecker --arkit for shipping visionOS USDZ assets.

Guardrails

  • Do not replace a prim with def when over is the correct edit.
  • Avoid composition-arc changes unless they are explicitly requested.
  • If a RealityKit app loads the asset with Entity(named:in:),

Entity(contentsOf:withName:), or a generated Reality Composer Pro content bundle, prefer fixing the authored asset and validating the bundle/package over building a parallel Swift scene graph.

  • Do not hand-edit a .usdz package in place; inspect or unpack it, edit the

source layer, rebuild the package, and validate the result.

  • Validate final Apple-platform USDZ output with usdchecker --arkit --strict,

not just a source-layer parse check.

  • Preserve existing formatting and comments when possible.

Output Expectations

Provide:

  • the prim or path edited
  • which reference files were used
  • the exact class of USD change made
  • the validation step used
  • routing to $usdkit-runtime-developer, shadergraph-editor, or runtime

testing if needed