all publishers

NVIDIA-Omniverse

@nvidia-omniverse source repo

362 published skills · page 1 of 4

  1. ▌
    Blender Addon Extension Development · nvidia-omniverse bundle
    ---
    245 repo stars
  2. ▌
    Ovrtx Color Management · nvidia-omniverse bundle
    Choose and validate ownership of OVRTX display presentation between scene-linear HDR and display-encoded LDR, using the installed add-on enum and the official color-presentation probe. Use for double-transform, washed-out, too-dark, or Blender-versus-OVRTX display differences.
    245 repo stars
  3. ▌
    Extend Ovrtx Materialx Openpbr · nvidia-omniverse bundle
    Extend and test Blender material graph conversion to MaterialX OpenPBR in the OVRTX Blender add-on. Use when adding supported shader nodes, sockets, texture operations, UV handling, material bindings, fallback policy, conversion diagnostics, or OpenPBR parity.
    245 repo stars
  4. ▌
    Ovrtx Addon Install And Preflight · nvidia-omniverse bundle
    Install, enable and preflight the ovrtx Blender Example release package (add-on plus locked external SDK runtime) in stock Blender 5.2 or newer. Use for installation, upgrades, a missing render engine or runtime integrity diagnostics.
    245 repo stars
  5. ▌
    Blender MCP Setup · nvidia-omniverse bundle
    Connect an agent to a running Blender session through the user's Blender MCP server and verify a safe, usable scene-control loop. Use when a user is new to Blender MCP, asks to create or edit a scene through MCP, or reports that Blender tools cannot connect. This covers the Blender-side MCP connection only; OVRTX and OVPhysX runtime setup belongs to ovrtx-addon-install-and-preflight.
    245 repo stars
  6. ▌
    Ovstorage 2 · nvidia-omniverse bundle
    Deploy and develop against NVIDIA Omniverse Storage APIs on any Kubernetes cluster (MicroK8s, EKS, AKS, GKE, bare metal). Two storage adapters: (1) Example Storage Adapter — Python filesystem reference implementation + Discovery for learning and custom adapter development; (2) S3/Azure Production Storage Adapter — NVIDIA pre-built S3/Azure adapter + Discovery as minimum, expandable with Event Aggregation, Event Consumer, RabbitMQ, Envoy Auth Extension, Storage Navigator, and Contour ingress. Can deploy on the developer's behalf (generating scripts + .env) or guide manual deployment. Custom adapter development covers three APIs: Storage, Notifications, and Permissions. Use when a developer asks about deploying, configuring, validating, troubleshooting, or building any component of the Omniverse Storage APIs stack.
    245 repo stars
  7. ▌
    Loading Usd 3 · nvidia-omniverse
    Populate an ovstage instance from USD via the population API: open a USD file or inline USDA into the stage, choose data domains, drive the async populate op, and read populated prims back by usd-path. Use when the user asks to load/ingest USD into ovstage, populate from a .usd/.usda file or string, add/remove USD references, or propagate live USD edits.
    245 repo stars
  8. ▌
    Stage Queries 3 · nvidia-omniverse
    Find prims with filter queries — predicates over reserved metadata built-ins (usd-path, usd-prim-type, usd-parent, usd-children, usd-schemas) and attribute presence — instead of explicit path lists, then introspect what a query matched. Use when the user asks to query, filter, select, or find prims by type, path, parent, child, applied schema, or attribute presence, or to read a query result's count / attributes / reusable handle.
    245 repo stars
  9. ▌
    Error Handling 3 · nvidia-omniverse
    Error checking patterns for the ovstage C API. Use when user asks about error handling, checking return codes, debugging ovstage failures, or troubleshooting a failed enqueue, wait, or fetch.
    245 repo stars
  10. ▌
    Project Setup C 3 · nvidia-omniverse
    Setting up a C/C++ consumer of ovstage. Use when user asks to create a new ovstage consumer (test, benchmark, plugin, or app), declare an ovstage dependency, include the headers, or build code that links ovstage.
    245 repo stars
  11. ▌
    String Handling 3 · nvidia-omniverse
    Working with ovx_string_t and ovx_string_or_token_t in ovstage (C / C++). Use when user asks about passing or comparing strings, attribute names, or prim paths, or about choosing between a raw string and a pre-resolved path-dictionary token.
    245 repo stars
  12. ▌
    Application Flow 3 · nvidia-omniverse
    End-to-end ovstage application lifecycle: create an instance, identify prims/attributes via the path dictionary, write attribute columns at an ordinal, advance the write floor to seal them, query/read, and release. Use when user asks how to structure an ovstage program, what the main steps are, or how the pieces fit together.
    245 repo stars
  13. ▌
    Project Setup Python 3 · nvidia-omniverse
    Setting up a Python project that uses the ovstage Python bindings. Use when user asks to create a Python ovstage app, import ovstage, configure the library path, or scaffold Python code that reads/writes stage data.
    245 repo stars
  14. ▌
    Warmup 2 · nvidia-omniverse
    Warming up the renderer before capturing output. Use when user asks about warmup frames, image quality, texture streaming, path tracing convergence, or why renders look noisy/incomplete.
    245 repo stars
  15. ▌
    Contract First Ffi 2 · nvidia-omniverse bundle
    Maintain C ABIs and language bindings as exact, testable contracts. Use when evolving public headers, ctypes/cffi/pybind/Rust/JS bindings, shared libraries, struct layouts, GPU/native APIs, or any cross-language boundary where drift can cause crashes or silent corruption.
    245 repo stars
  16. ▌
    Renderer Gpu Interop 2 · nvidia-omniverse bundle
    Share renderer output zero-copy across GPU APIs and runtimes (Vulkan↔CUDA, Metal/MPS, DLPack to Warp/PyTorch) and own GPU resource lifetime and teardown across that boundary. Use when Codex wires external-memory/-semaphore interop, hands a render target to a training/compute consumer without a CPU bounce, or debugs interop fd ownership, cross-API sync, double-buffered overlap, ARC/handle lifetime, or teardown-order crashes.
    245 repo stars
  17. ▌
    Renderer Backend Port 2 · nvidia-omniverse bundle
    Port an existing nanoUSD renderer to a new GPU backend or API (e.g. Vulkan to Metal, DX12, or WebGPU) or stand up a second backend behind the shared renderer contract. Use when Codex adds a backend, translates shaders and RHI calls across graphics APIs, decides what to share versus reimplement versus stub, keeps backends at ABI and feature parity, or hits cross-API transform, struct-alignment, command-encoder, or resource-residency pitfalls.
    245 repo stars
  18. ▌
    AI Agent Orchestration 2 · nvidia-omniverse bundle
    Coordinate multiple AI agents or subagents on software work without duplicating effort or causing conflicts. Use when Codex is explicitly asked to delegate exploration, implementation, review, testing, integration, or parallel analysis across a codebase.
    245 repo stars
  19. ▌
    Graphics Debugging Lab 2 · nvidia-omniverse bundle
    Debug rendering, viewer, shader, material, camera, lighting, and GPU integration bugs with reproducible visual evidence. Use when scenes render blank, only appear after camera motion, show incorrect shading, diverge across backends, crash in GUI mode, or need pixel/screenshot verification.
    245 repo stars
  20. ▌
    Loading Usd 2 · nvidia-omniverse
    Loading USD scenes into the renderer from files, URLs, or inline USDA strings. Use when user asks to load a USD scene, compose USD content, add cameras or RenderProducts to an existing USD layer, add referenced content, or create runtime geometry.
    245 repo stars
  21. ▌
    Renderer Capability Abi 2 · nvidia-omniverse bundle
    Define and govern the shared renderer C ABI and backend capability contract so multiple backends stay interchangeable and parity is machine-checked. Use when Codex designs or changes the public renderer header, adds a capability/AOV/entry point, reports what a backend supports versus stubs, or wires renderer ABI conformance into CI. Pairs with contract-first-ffi (general FFI hygiene) and renderer-feature-validation-matrix (per-feature status).
    245 repo stars
  22. ▌
    Cuda Interop 2 · nvidia-omniverse
    GPU interop patterns for CUDA arrays, timeline semaphores, and Vulkan shared memory. Use when user asks about CUDA interop, GPU rendering pipelines, Vulkan interop, shared memory, or timeline semaphores.
    245 repo stars
  23. ▌
    Renderer Realtime Sensor 2 · nvidia-omniverse bundle
    Design real-time, headless, multi-camera renderers that produce reproducible sensor data for simulation and RL training. Use when Codex builds or reviews a renderer feeding a physics/RL loop (IsaacLab, Newton, MuJoCo), works on determinism/reproducibility, sensor AOVs (depth/segmentation/normals), multi-camera tiling, or the fidelity-versus-throughput target for a training sensor rather than an offline beauty render.
    245 repo stars
  24. ▌
    Renderer Simulation Loop 2 · nvidia-omniverse bundle
    Drive a renderer from a physics/RL simulation loop (IsaacLab, Newton, MuJoCo) — per-step transform/visibility updates from physics state, time handling, frame pacing, and the consumer contract. Use when Codex integrates a renderer into a training/sim loop, plumbs physics transforms or time into the scene, or debugs bodies-render-at-origin, stale-frame, per-env update, or pacing problems.
    245 repo stars
  25. ▌
    Cloning Prims 2 · nvidia-omniverse
    Cloning USD subtrees to create copies at new paths. Use when user asks to clone, duplicate, copy a prim, or create instances of existing geometry.
    245 repo stars
  26. ▌
    Stage Queries 2 · nvidia-omniverse
    Discovering prims on the runtime stage and inspecting their attribute schemas. Use when user asks to find prims by type, filter by attribute, list all prims, or look up attribute types before reading or writing them.
    245 repo stars
  27. ▌
    Layered Boundary Refactor 2 · nvidia-omniverse bundle
    Refactor disjoint or duplicated projects into clear layered architecture with canonical contracts and thin adapters. Use when viewers, renderers, bindings, data libraries, plugins, or services overlap and need maintainable ownership boundaries without losing behavior.
    245 repo stars
  28. ▌
    Error Handling 2 · nvidia-omniverse
    Error checking patterns for both C and Python. Use when user asks about error handling, checking errors, debugging ovrtx failures, or troubleshooting.
    245 repo stars
  29. ▌
    Status Queries 2 · nvidia-omniverse
    Querying progress for asynchronous ovrtx operations. Use when user asks how to monitor long-running operations, show loading progress, inspect OperationStatus counters, use Operation.query_status(), or call ovrtx_query_op_status()/ovrtx_release_op_status().
    245 repo stars
  30. ▌
    Update 0 2 0 3 2 · nvidia-omniverse
    Upgrade skill to migrate an existing ovrtx codebase from 0.2.0 to 0.3.0. Use when the user asks to "upgrade from 0.2 to 0.3", migrate ovrtx API usage, update 0.2 projects to 0.3, or fix code after moving from ovrtx 0.2.x to 0.3.x.
    245 repo stars
  31. ▌
    Project Setup C 2 · nvidia-omniverse
    Setting up a new CMake C/C++ project that uses ovrtx. Use when user asks to create a new C project, set up CMake with ovrtx, scaffold a C++ app, or configure build dependencies.
    245 repo stars
  32. ▌
    Render Settings 2 · nvidia-omniverse
    Writing render settings to control rendering behavior. Use when user asks to change render settings, set max bounces, configure path tracing, change render quality, or modify RTX settings on a RenderProduct.
    245 repo stars
  33. ▌
    Semantic Labels 2 · nvidia-omniverse
    Assigning USD SemanticsAPI class and label metadata for semantic segmentation and ground-truth annotation outputs. Use when user asks to label objects, assign semantic class/label metadata, configure semantic segmentation labels, or author SemanticsAPI overrides.
    245 repo stars
  34. ▌
    String Handling 2 · nvidia-omniverse
    Working with ovx_string_t in C and C++. Use when user asks about printing, comparing, or converting ovx strings.
    245 repo stars
  35. ▌
    Application Flow 2 · nvidia-omniverse
    High-level overview of a typical ovrtx application lifecycle. Use when user asks how to structure an ovrtx program, what the main steps are, or how the pieces fit together.
    245 repo stars
  36. ▌
    Async Operations 2 · nvidia-omniverse
    Asynchronous operation patterns including polling, timeouts, and non-blocking workflows. Use when user asks about async rendering, non-blocking operations, polling, timeouts, or parallel rendering.
    245 repo stars
  37. ▌
    Agentic Codebase Cartography 2 · nvidia-omniverse bundle
    Map unfamiliar or multi-repository codebases before refactoring, integration, or feature work. Use when Codex needs to analyze submodules, ownership boundaries, APIs, duplicate implementations, build/test surfaces, risk areas, and a practical refactor sequence before changing code.
    245 repo stars
  38. ▌
    Portable Build Runtime Paths 2 · nvidia-omniverse bundle
    Make native builds, command-line tools, viewers, plugins, shaders, test harnesses, and packaged artifacts portable across working directories, install trees, copied build trees, users, and machines. Use when Codex works on CMake/install rules, RPATH/RUNPATH, dynamic library lookup, shader or asset discovery, CLI resource paths, packaging, deployment, or bugs that only reproduce outside the repo root.
    245 repo stars
  39. ▌
    Renderer Constrained Backend 2 · nvidia-omniverse bundle
    Build a renderer backend to a hard resource or capability budget — low VRAM, raster-only (no hardware ray tracing), or a portable/embedded GPU like OpenGL ES — where features must be baked, capped, or degraded rather than ported wholesale from the high-end backend. Use when Codex builds a low-end/portable backend, fits a GPU-memory budget, bakes materials instead of codegen, or makes a no-RT fallback match a reference renderer.
    245 repo stars
  40. ▌
    Verification Led Development 2 · nvidia-omniverse bundle
    Plan and execute code changes with focused verification at each layer. Use when implementing fixes or refactors that need builds, tests, smoke runs, screenshots, logs, benchmarks, or clear residual-risk reporting before handoff.
    245 repo stars
  41. ▌
    Binding Materials 2 · nvidia-omniverse
    Binding materials to prims at runtime. Use when user asks to assign a material, change a material, set material binding, or swap materials on a prim.
    245 repo stars
  42. ▌
    Picking Selection 2 · nvidia-omniverse
    Viewport picking, marquee selection, pick-hit decoding, pickability, and selection outline drawing. Use when implementing click picking, drag selection, printing picked prim names, or highlighting selected prims.
    245 repo stars
  43. ▌
    Renderer Creation 2 · nvidia-omniverse
    Creating and configuring an ovrtx renderer instance. Use when user asks to create a renderer, initialize ovrtx, configure renderer options, or set up ovrtx.
    245 repo stars
  44. ▌
    Attribute Bindings 2 · nvidia-omniverse
    Creating persistent attribute bindings for efficient repeated writes to the same prims and attribute. Use when user asks about persistent bindings, repeated writes, efficient animation loops, bind_attribute, or updating transforms every frame with caller-owned tensors. Use mapping-attributes when the hot path needs zero-copy direct writes into ovrtx buffers.
    245 repo stars
  45. ▌
    Camera Outputs Rt2 2 · nvidia-omniverse
    Available camera render outputs for Real-Time Path-Tracing (RT2) mode. Use when user asks what AOVs/render vars are available, what format or dtype an output has, or how to read a specific output like depth, normals, albedo, or distance.
    245 repo stars
  46. ▌
    Mapping Attributes 2 · nvidia-omniverse
    Zero-copy attribute map/unmap for direct memory access to ovrtx internal buffers. Use when user asks about zero-copy writes, map attribute, direct memory access, Warp/CUDA kernel writes into mapped tensors, or GPU attribute updates. Use attribute-bindings for repeated writes with caller-owned tensors when a copy is acceptable.
    245 repo stars
  47. ▌
    Reading Attributes 2 · nvidia-omniverse
    Reading scalar or array attributes from prims into CPU or GPU tensors. Use when user asks to read an attribute value, fetch mesh data (points, faceVertexCounts, etc.), inspect a render setting, or sample transforms.
    245 repo stars
  48. ▌
    Writing Attributes 2 · nvidia-omniverse
    Writing scalar and array attribute data to prims. Use when user asks to write an attribute, set a property, change a material, set a color, or modify mesh data.
    245 repo stars
  49. ▌
    Writing Transforms 2 · nvidia-omniverse
    Writing 4x4 transform matrices to move, rotate, or scale prims. Use when user asks to move an object, set a transform, update position, animate a transform, or set a camera transform.
    245 repo stars
  50. ▌
    Renderer Stalled Parity Triage 2 · nvidia-omniverse bundle
    Reset renderer/reference parity work when beauty images, scalar metrics, repeated local tweaks, or narrow target slices stop improving. Use when signed residuals stay structured, AOVs disagree with beauty, noise or denoising hides lighting/shadow detail, equal-spp comparisons are misleading, reference metadata is uncertain, or several exposure/material/light/denoiser/transport experiments have been rejected without progress.
    245 repo stars
  51. ▌
    Nonvisual Materials 2 · nvidia-omniverse
    Authoring non-visual material labels for sensor simulation. Use when user asks to assign lidar/radar/acoustic material semantics, choose nonvisual base materials, coatings, or attributes, debug material IDs, or bind sensor-facing USD materials.
    245 repo stars
  52. ▌
    Legacy Retirement Clean History 2 · nvidia-omniverse bundle
    Identify and remove obsolete legacy, fallback, staging, compatibility, duplicate, generated, and reference code before creating clean initial commits or new project history. Use when a repo is being reset, consolidated, or prepared for a cleaner public history.
    245 repo stars
  53. ▌
    Renderer Implementation Roadmap 2 · nvidia-omniverse bundle
    Sequence a nanoUSD renderer build from nothing into a correct, scalable backend using only the renderer skill set. Use when Codex starts a new renderer or backend, plans renderer milestones and phase order, decides what must be correct before the next layer, or needs the contracts-first build order and reduced-fixture corpus that turn the other renderer skills into a buildable plan with no reference renderer to copy from.
    245 repo stars
  54. ▌
    Project Setup Python 2 · nvidia-omniverse
    Setting up a new Python project that uses ovrtx. Use when user asks to create a new Python project, set up ovrtx in Python, create a pyproject.toml, or scaffold a Python app.
    245 repo stars
  55. ▌
    Renderer Shader Host Layout Sync 2 · nvidia-omniverse bundle
    Keep host C/C++ structs and the shaders that read them byte-for-byte in sync — SSBO/UBO/push-constant layout, binding indices, and shared constants across GLSL/MSL/SPIR-V. Use when Codex adds or changes a struct shared between host code and a shader, wires descriptor/binding layouts, shares a push-constant block across pipelines, or debugs "wrong pixels with no crash" layout-drift bugs.
    245 repo stars
  56. ▌
    Reading Render Output 2 · nvidia-omniverse
    Mapping rendered output to access pixel data on CPU or GPU. Use when user asks to get pixels, read an image, save a PNG, display rendered output, or access render var data.
    245 repo stars
  57. ▌
    Nanousd Renderer Scene Extraction 2 · nvidia-omniverse bundle
    Load USD scenes through NanoUSD and convert composed USD prims into renderer-ready geometry, material, light, camera, transform, instancing, texture, and diagnostic representations. Use when implementing, debugging, or validating NanoUSD-based scene ingestion, renderer scene structs, material/light extraction, texture path resolution, or loader parity against USD/OpenUSD semantics.
    245 repo stars
  58. ▌
    Renderer Image Comparison Testing 2 · nvidia-omniverse bundle
    Design, implement, and run golden-image renderer comparison harnesses for graphics and viewer projects. Use when Codex needs to capture renderer output, compare Vulkan/OpenGL/Metal or other backends against golden images, refresh baselines, choose image-difference thresholds, wire tests into CI/CTest, handle display/GPU constraints, inspect visual diffs, or report residual risk for renderer correctness.
    245 repo stars
  59. ▌
    Renderer Performance Architecture 2 · nvidia-omniverse bundle
    Design, review, or refactor high-performance renderer architecture for large USD scenes. Use when Codex needs to reason about target-quality/SOTA renderer architecture, instancing, batching, draw calls, frame-time budgets, geometry streaming, GPU buffer residency, texture/material upload, acceleration structures, shadows, forward/deferred render paths, readback, telemetry, performance validation, or replacing dead-end renderer paths.
    245 repo stars
  60. ▌
    Stepping And Rendering 2 · nvidia-omniverse
    Running a simulation step to produce rendered frames. Use when user asks to render a frame, step the renderer, simulate a sensor, or get an image from ovrtx.
    245 repo stars
  61. ▌
    Renderer Feature Validation Matrix 2 · nvidia-omniverse bundle
    Create and maintain renderer feature validation matrices for correctness, performance, backend parity, and test coverage. Use when Codex plans renderer milestones, delegates subagent work, compares against Kit/Hydra/reference output, or decides whether a renderer feature is implemented, degraded, missing, or untested.
    245 repo stars
  62. ▌
    Combining Scene With Runtime Prims 2 · nvidia-omniverse
    Loading a base USD scene with additional runtime prims in tests. Use when a doc test needs to combine a scene file with RenderProducts or other prims that aren't in the original scene.
    245 repo stars
  63. ▌
    Renderer Target Architecture Design 2 · nvidia-omniverse bundle
    Design renderer features from the target-quality architecture first, including radical subsystem replacement when incremental slices are exhausted. Use when Codex implements or plans path tracing, denoising, lighting, sampling, acceleration structures, scene residency, instancing, texture systems, material systems, render graphs, or major renderer features where state-of-the-art/proven production techniques are needed.
    245 repo stars
  64. ▌
    Physically Based Renderer Validation 2 · nvidia-omniverse bundle
    Design, debug, or validate physically based renderer behavior against a reference renderer. Use when Codex works on PBR materials, USD light semantics, shadows, transparency, GI, emissive sampling, tone mapping, AOVs, stochastic sampling, path tracing, ray tracing, or Omniverse Kit/Hydra/OVRTX visual parity.
    245 repo stars
  65. ▌
    Configuring Lidar Sensors 2 · nvidia-omniverse
    Authoring and configuring OmniLidar sensor prims and lidar PointCloud render outputs. Use when user asks to create a lidar scene, configure an OmniLidar prim, choose lidar output frame/coordinate behavior, or request lidar PointCloud channels.
    245 repo stars
  66. ▌
    Configuring Radar Sensors 2 · nvidia-omniverse
    Authoring and configuring OmniRadar sensor prims and radar PointCloud render outputs. Use when user asks to create a radar scene, configure an OmniRadar prim, choose radar output frame/coordinate behavior, configure radar scan outputs, or request radar PointCloud channels.
    245 repo stars
  67. ▌
    Reading Sensor Pointclouds 2 · nvidia-omniverse
    Mapping and reading lidar or radar PointCloud composite render-var tensors. Use when user asks how to access PointCloud output data, map Coordinates, Counts, Intensity, RCS, RadialVelocityMs, or TimeOffsetNs tensors, slice valid entries, or move sensor point clouds through CPU/CUDA memory. For channel meanings and units, use the interpreting-lidar-pointclouds or interpreting-radar-pointclouds skills.
    245 repo stars
  68. ▌
    Render Product Device Pinning 2 · nvidia-omniverse
    Restricting RenderProducts to specific CUDA-visible device indices with the USD deviceIds attribute. Use when a scene, test, or example must constrain a RenderProduct to CUDA-visible GPU 0 or another explicit set of CUDA-visible GPUs, especially for multi-GPU CI or viewport picking.
    245 repo stars
  69. ▌
    Interpreting Lidar Pointclouds 2 · nvidia-omniverse
    Interpreting already-read lidar PointCloud tensors: channel meanings, units, valid point ranges, coordinate-frame implications, flags, IDs, normals, velocity, and visualization values. Use reading-sensor-pointclouds when the user needs to map or fetch the tensors first.
    245 repo stars
  70. ▌
    Interpreting Radar Pointclouds 2 · nvidia-omniverse
    Interpreting already-read radar PointCloud tensors: channel meanings, units, valid detection ranges, RCS, signed radial velocity, time offsets, flags, counts, and visualization values. Use reading-sensor-pointclouds when the user needs to map or fetch the tensors first.
    245 repo stars
  71. ▌
    Brev CLI 2 · nvidia-omniverse bundle
    Manage Brev instances safely from the Brev CLI. Use when a workflow needs to list, create, access, copy to, execute on, port-forward, stop, or delete Brev instances for Content Agents dependency endpoints.
    245 repo stars
  72. ▌
    Quickstart 2 · nvidia-omniverse bundle
    Set up and route NVIDIA Content Agents through the default Agentic Content Workflow from the repository root. Use when the user asks for /quickstart, first-run setup, an unqualified supported content task, or prerequisite checks. Route an explicitly requested fixed pipeline CLI, REST, config, benchmark, or deployment through the fixed-pipeline umbrella without treating it as the default.
    245 repo stars
  73. ▌
    Fixed Pipeline 2 · nvidia-omniverse bundle
    Use when the user explicitly requests a fixed-pipeline Content Agent CLI, service client, deployment, benchmark, or maintenance workflow under apps/: material-agent-cli, material-agent-client, physics-agent-cli, physics-agent-client, joint-agent-cli, joint-agent-client, joint-agent-validation, texture-agent-cli, texture-agent-client, validation-agent-cli; deploy-collection, deploy-material-agent-docker, deploy-material-agent-brev, deploy-physics-agent-docker, deploy-physics-agent-brev, deploy-texture-agent-docker, deploy-texture-agent-brev, deploy-ovrtx-docker, deploy-embeddings-brev, deploy-image-gen-brev, or deploy-qwen-vlm-brev.
    245 repo stars
  74. ▌
    Usd CLI 2 · nvidia-omniverse
    Run explicit low-level USD scene inspection, editing, rendering, material binding, physics authoring, and raw validation with the in-tree usd-cli package. Use when the user asks for direct scene mechanics on a USD/USDA/USDC/USDZ asset or asks to set up usd-cli. Domain workflows must route to their content-workflow-* skill; usd-cli never owns workflow policy, orchestration, artifacts, recovery, or acceptance.
    245 repo stars
  75. ▌
    Image Generation 2 · nvidia-omniverse bundle
    Generate or edit raster images for agentic workflows through the coding agent's companion image generator by default or an explicitly configured World Understanding image backend. Use when a workflow needs text-to-image, conditioned image editing, or a recorded generated-image artifact with provider, prompt, input, and output provenance.
    245 repo stars
  76. ▌
    Content Workflow CLI 2 · nvidia-omniverse
    Default launcher for supported Content Agent tasks from the repository root, including deterministic Geometry handoff, conversion, material or physics authoring, texture, segmentation, validation, large scenes, durable articulation, composed assets, review, and resume. Use fixed-pipeline app CLIs only when the user explicitly requests fixed control flow, YAML configuration, REST, benchmarking, or a named fixed-pipeline command.
    245 repo stars
  77. ▌
    Content Texture Scope 2 · nvidia-omniverse
    Inspect an explicit USD material or prim scope, existing bindings, and UV readiness before texture generation. Use for bounded Texture workflow inspection and UV-preparation decisions.
    245 repo stars
  78. ▌
    Content Sdf Operations 2 · nvidia-omniverse bundle
    Use when a content agent needs bounded signed- or unsigned-distance-field operations such as mesh rasterization, field booleans, offsets, filtering, sampling, topology conversion, surface extraction, or admitted field output through an in-process backend.
    245 repo stars
  79. ▌
    Content Workflow Asset 2 · nvidia-omniverse bundle
    Run one prompt-specific asset workflow through a sole outer reasoner that supplies and freezes a typed public-leaf dependency graph. Use for selective, resumable asset composition without a built-in domain or stage order. Explicit compatibility-fixed mode still composes Geometry preparation, articulation review, material assignment, bounded texture generation, physics authoring, validation, and final USDZ packaging as one durable single-asset workflow.
    245 repo stars
  80. ▌
    Geometry Source Intake 2 · nvidia-omniverse bundle
    Classify and prepare one geometry.source.v1 bundle or CAD, mesh, USD, URDF, MJCF, GLTF, GLB, or 3MF artifact while preserving units, provenance, editability, representation roles, and source fidelity. Use before Geometry, repair, segmentation, material, physics, or SimReady workflows need canonical geometry input.
    245 repo stars
  81. ▌
    Content Texture Publish 2 · nvidia-omniverse
    Validate a Texture decision chain and publish a portable scoped USD result. Use after all bounded generation and visual-review steps reach a terminal decision.
    245 repo stars
  82. ▌
    Content Texture Quality 2 · nvidia-omniverse
    Collect matched Texture evidence, optionally request advisory critique, and record the outer multimodal review. Use after explicit candidate generation.
    245 repo stars
  83. ▌
    Content Workflow Physics 2 · nvidia-omniverse bundle
    Own agent-driven physics planning, policy, component decisions, guarded repair, authoring, optional attested VoMP mass properties, simulation-backed validation, refinement, acceptance, and durable artifacts for a USD asset, using usd-cli only for low-level scene operations.
    245 repo stars
  84. ▌
    Content Workflow Texture 2 · nvidia-omniverse bundle
    Use one outer Codex or Claude reasoner to select and invoke focused, digest-bound Texture capabilities without a nested Texture workflow controller.
    245 repo stars
  85. ▌
    Geometry Evidence Review 2 · nvidia-omniverse bundle
    Gather and interpret geometry inspection, OVRTX render, topology, USD, projection, source-fidelity, and protected-feature evidence for one candidate. Use when an interactive session or workflow must decide whether geometry is reviewable, what additional evidence is needed, which defect is present, or whether to accept, refine, repair, or block a candidate.
    245 repo stars
  86. ▌
    Product Image Decomposer 2 · nvidia-omniverse bundle
    Decompose product reference images into CAD-ready component crops, semantic part-plan evidence, exploded-view evidence, six-view prompts, and a reassembly manifest before geometry generation or reconstruction.
    245 repo stars
  87. ▌
    Content Texture Candidate 2 · nvidia-omniverse
    Generate, compare, and preview one bounded texture candidate set for exact texture-unit IDs. Use for initial generation or failed-unit regeneration without unrelated mutation.
    245 repo stars
  88. ▌
    Content Workflow Geometry 2 · nvidia-omniverse bundle
    Complete a provider-neutral Geometry handoff from CAD, mesh, generated, or existing USD. Use when a workflow needs source lineage, prepared and optimized geometry, OVRTX and USD evidence, semantic parts or parameters, and content_agents_manifest.json without claiming final physics, runtime behavior, or SimReady status.
    245 repo stars
  89. ▌
    Content Workflow Material 2 · nvidia-omniverse bundle
    Default material-authoring workflow for supported, unqualified USD material tasks. Use with usd-cli when a long-running coding agent assigns visual or non-visual materials, uses libraries, performs iterative visual review, and produces canonical artifacts and validation evidence; use material-agent-* only for explicit fixed pipeline requests.
    245 repo stars
  90. ▌
    Content Workflow Simready 2 · nvidia-omniverse bundle
    Use after USD conversion, material and physics authoring, or Joint Agent publication to preflight SimReady Foundation, formally validate the current staged USD or USDZ, conditionally conform it from the failed validation report, revalidate the conformed output, run Gate 3B validation, and preserve durable non-blocking remediation evidence.
    245 repo stars
  91. ▌
    Content Articulation Review 2 · nvidia-omniverse
    Select, reject, or safely edit every articulation candidate through a digest-bound decision patch. Use before human review or accepted-only authoring.
    245 repo stars
  92. ▌
    Content Workflow Validation 2 · nvidia-omniverse bundle
    Validate USD assets through deterministic preparation, one decision-only Codex or Claude planning child, outer-validated exact adapters, independent assessment/review, and non-mutating terminal receipts. Use for agentic standalone Validation; use focused commands for explicit compatibility operations and the fixed-pipeline umbrella for config-driven Validation Agent runs.
    245 repo stars
  93. ▌
    Content Workflow Large Scene 2 · nvidia-omniverse bundle
    Coordinate a large OpenUSD scene through decomposition, per-asset domain processing, and original-topology collection using durable run state and deterministic handoff gates. Use when a scene is too large or repetitive to process monolithically, when material/physics/other tasks must run over decomposed representatives, or when resuming or repairing a three-phase large-scene run.
    245 repo stars
  94. ▌
    Content Articulation Proposal 2 · nvidia-omniverse
    Propose bounded revolute or prismatic articulation candidates from exact inspection evidence. Use to reason about endpoints, axes, limits, confidence, and native readiness before review.
    245 repo stars
  95. ▌
    Content Workflow Articulation 2 · nvidia-omniverse
    Run durable Joint Agent articulation-v1 workflows that bind usd-cli inspection evidence, pause for explicit review, resume without repeating completed phases, author only approved revolute or prismatic joints, and verify exact saved USDZ readback. Use when prompt-driven joint, drawer, hinge, slider, mechanism, or articulation work needs the isolated agentic workspace.
    245 repo stars
  96. ▌
    Content Articulation Authoring 2 · nvidia-omniverse
    Author only approved articulation candidates, then validate saved-stage identity and joint-graph readback. Use after agent and required human review are durably bound.
    245 repo stars
  97. ▌
    Content Articulation Inspection 2 · nvidia-omniverse
    Inspect bounded USD hierarchy, existing articulation, and usd-cli evidence before proposing joints. Use for exact Articulation candidate preparation and targeted reinspection.
    245 repo stars
  98. ▌
    Content Workflow Convert To Usd 2 · nvidia-omniverse
    Use before USD-based content workflows when a source asset must be routed to OpenUSD through the existing content-workflow-cli conversion workflow, including dependency preflight, existing USD passthrough, CAD/mesh, URDF, MuJoCo/MJCF, durable reports, blocked results, and downstream USD handoff.
    245 repo stars
  99. ▌
    Content Workflow Geometry Repair 2 · nvidia-omniverse bundle
    Complete a source-preserving Geometry repair workflow for imported CAD, mesh, USD, URDF, or MJCF geometry with bounded topology work, collision separation, and explicit evidence. Use when a user or parent workflow needs a durable certified, conditional, rejected, blocked, failed, or cancelled geometry-repair outcome rather than one isolated diagnosis or edit.
    245 repo stars
  100. ▌
    Content Workflow Scene Collection 2 · nvidia-omniverse bundle
    Collect validated decomposed-asset task results back onto original OpenUSD topology through domain-specific projection, representative propagation, conflict harmonization, independent domain layers, composition, and a sealed Workflow 3 handoff. Use after asset-task processing or when repairing collection for material, physics, articulation, geometry, or mixed-domain outputs.
    245 repo stars