Agent skill · software engineering · nvidia
omniverse-realtime-viewer
Use as the top-level router for Omniverse Realtime Viewer USD apps, XR delivery, SPG GPU processing, stylized rendering, and focused viewer reference documents.
Why this skill is useful
Provides specific architectural rules and implementation recipes for building Omniverse Realtime Viewer applications that the AI wouldn't reliably generate on its own.
What it needs
Requires electron, node, python, react, tauri installed locally. About 3k tokens when loaded. Last updated 2026-08-07. 2,816 stars on the source repository.
What this skill does
<!-- SPDX-FileCopyrightText: Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved. --> <!-- SPDX-License-Identifier: Apache-2.0 --> Omniverse Realtime Viewer Build responsive USD viewers by composing OVRTX rendering, OVStage scene state, and the delivery/UI libraries appropriate to the app. Use this package for viewer architecture and interaction; use each selected SDK's upstream guidance for installation and exact release-specific APIs. Start With The App 1. When delivery is explicit, select its recipe through references/routing.md and follow its current phase. Otherwise start with references/usd-viewer-app/README.md. For an existing app, keep its architecture and read only the references for the requested change. Broad app, conventions and UI catalogs are lookups as needed. 2. Resolve the selected libraries through references/dependencies/README.md. Preserve the project's manifest unless an upgrade is requested. 3. Build a working frame and camera interaction in the chosen shell, then add the requested capabilities. Read references/conventions.md for shared input, camera, selection, and protocol conventions. 4. Use references/viewer-ux-workflow/README.md for broader interface design. Loading, selection feedback, errors, and input responsiveness belong in the first working app, alongside rendering. 5. Validate the actual delivery path with references/validation.md. A browser screenshot does not validate a native window or a different transport. Architecture Owner Responsibility --- --- Viewer runtime Own the live OVStage, publication clock, OVRTX renderer, scene changes, and render stepping. UI and input adapter Display frames and copied app state; send user intent to the runtime owner. Storage/query/simulation workers Perform their assigned work and return results through the selected integration boundary. Delivery adapter Present locally or stream through ovstream; respect frame ownership and backpressure. Use OVRTX for USD/3D rendering. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills nvidia/omniverse-realtime-viewer