Generated banner for Omniverse Realtime Viewer
Generated logo for Omniverse Realtime Viewer

Omniverse Realtime Viewer

NVIDIAOfficialCreated by NVIDIA Omniverse

  • Skill
  • Tool integration
  • Software development
  • Apache-2.0
  • Medium risk

From the author

Use as the top-level router for Omniverse Realtime Viewer USD apps, XR delivery, SPG GPU processing, stylized rendering, and focused viewer reference documents.
— the description by NVIDIA Omniverse

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

The Omniverse Realtime Viewer skill acts as a central routing and architectural framework for developing USD-based 3D viewer applications. It provides a structured approach to composing rendering, scene state, and delivery mechanisms, ensuring that developers can integrate OVRTX rendering, OVStage scene management, and various UI or streaming adapters effectively. The skill emphasizes a modular architecture where the viewer runtime, UI/input adapters, and delivery systems are decoupled, allowing for consistent behavior across local and streamed environments.

What it does

  • Provides a routing architecture for USD viewer apps, XR delivery, and GPU-accelerated rendering.
  • Defines the separation of concerns between viewer runtime, UI adapters, and delivery systems.
  • Offers guidance on integrating OVRTX for high-fidelity 3D rendering.
  • Establishes conventions for camera interaction, scene state management, and input handling.
  • Supports the implementation of specialized features like stylized rendering and CAE/CFD visualization.
  • Provides protocols for agent-to-UI communication and scene control.

When to use it

  • When starting the development of a new USD-based realtime viewer application.
  • When integrating advanced rendering features like stylized visualization or AOV switching.
  • When building XR or spatial editing capabilities into an existing Omniverse application.
  • When you need to standardize the architecture for local and streamed viewer deployments.
  • When implementing chat-driven scene control or agent-based inspection of a 3D scene.

Advantages

  • Promotes a clean, modular architecture that separates rendering logic from UI and transport.
  • Ensures consistent behavior across different delivery methods, such as local windows or WebRTC streaming.
  • Provides clear paths for extending functionality without disrupting the core viewer runtime.
  • Facilitates the integration of complex simulation and visualization data into the viewer.
  • Standardizes conventions for scene state, selection, and camera control.

Usage examples

“How do I set up a basic USD viewer application using the Omniverse Realtime Viewer architecture?”
The agent will guide you to start with the viewer app reference, resolve dependencies, and implement the core runtime owner to manage the OVStage and OVRTX renderer.
“I need to add stylized rendering to my existing viewer. Where should I start?”
The agent will direct you to the stylized visualization references to implement the required USD/Lua/CUDA nodes within your existing runtime owner.
“How can I enable an AI agent to control the viewer scene?”
The agent will point to the A2UI Scene Copilot reference to implement an operation interface that allows the agent to send commands through the existing runtime owner.
“How do I switch between different render outputs like beauty and depth in my viewer?”
The agent will explain how to use the AOV switching reference to map RenderVars and update the RenderProduct's orderedVars through the runtime owner.

Install

  1. Download the skill as a ZIP:

    https://autogineer.com/agent-skills/nvidia/omniverse-realtime-viewer/download
  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip omniverse-realtime-viewer.zip -d .agents/skills

Documentation by NVIDIA Omniverse

<!-- 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

OwnerResponsibility
Viewer runtimeOwn the live OVStage, publication clock, OVRTX renderer, scene changes, and render stepping.
UI and input adapterDisplay frames and copied app state; send user intent to the runtime owner.
Storage/query/simulation workersPerform their assigned work and return results through the selected integration boundary.
Delivery adapterPresent locally or stream through ovstream; respect frame ownership and backpressure.

Use OVRTX for USD/3D rendering. Browser apps display its WebRTC video; local apps present its output through their native shell. A missing GPU means rendering is unverified, not a reason to substitute a browser 3D renderer.

Keep viewer cameras, settings, effects, and transient edits in app-owned session or runtime state so the source USD stays intact. Serialize scene mutation and render stepping through the runtime owner. Read references/ovstage-ovrtx-integration/README.md for that loop, then the population or data-plane references when implementing scene loading or attribute writes.

Keep expensive loading and metadata work off the UI and render threads. Keep transport details behind a delivery adapter so camera, selection, properties, and loading state can be reused across local and streamed shells.

Add Capabilities As Needed

Use references/routing.md to select camera/picking, scene management, render settings, cloud assets, simulation, editor tools, deployment, or CAE/CFD visualization. Read the selected capability's implementation flow and its linked contract; the full reference catalog is not a prerequisite for a first frame.

For simulation, use the routing reference's Simulation Ecosystem section plus references/realtime-sim-integration/README.md. For UI-driven forces or control, add references/interaction-round-trip/README.md.

For example scenes, use references/usd-sample-data/README.md. When a runtime failure needs diagnosis, use references/troubleshooting/README.md and the selected SDK's matching release guidance before changing the architecture.

Solid Modeling: Upstream First

For usd-brep, exact BRep, solid modeling, kernel failures, CAD topology, or BrepArray questions, first read references/dependencies/README.md → USD BRep. Follow the owning repository's current agent guidance, skills, operation docs, and package API before selecting local integration references. Discover the upstream router rather than assuming skill names or directory layouts remain fixed. Upstream owns modeling semantics, schema rules, tuning, and diagnostics; this package owns OVRTX display, worker handoff, selection mapping, and publication timing.

GPU Processing And Stylized Viewers

For custom GPU processing, chained outputs and lens sampling, read references/spg-processing/README.md. For toon, ink, technical/X-Ray styles, geometry strokes or full wireframe, continue to references/stylized-visualization/implementation.md. Its USD/Lua/CUDA starting node and geometry/depth/composite build sequence work with the selected viewer recipe; use references/stylized-visualization/style-recipes.md for the preset math and references/stylized-visualization/README.md for supporting contracts. Implement the result inside the existing OVRTX/runtime owner and deliver the published processed output. These instructions do not require a sample checkout or a prior stylized-rendering implementation.

For an optional usd-brep geometry source, first read references/dependencies/README.md → USD BRep and the owning repository's current agent guidance, skills, and operation docs; then read references/stylized-visualization/usd-brep-source.md for the display boundary.

XR Viewers

For headsets, immersive viewers, or spatial editors, start with references/xr-viewer-recipe/README.md. Resolve SDK setup and contracts through references/dependencies/ovxr.md; the library owns OpenXR lifecycle and frame submission. For controllers, hands, navigation, or scene tools, add references/xr-spatial-input/README.md and references/ovxr-python-interactions/README.md. For projection-integrated UI, read references/ovxr-composition-ui/README.md and references/ovxr-composition-ui-validation/README.md.

Files

BENCHMARK.md

Skill Benchmark: omniverse-realtime-viewer

✅ Overall verdict: PASS — Recommended for publication

Publication Recommendation

Recommended for publication based on the completed evaluation evidence in this report.

Evaluation Metadata

  • Skill: omniverse-realtime-viewer

  • Validation status: passed

  • Evaluation date: 2026-11-06

  • Evaluator version: 1.6.9

  • Agents: Claude Code (aws/anthropic/bedrock-claude-opus-5-5), Codex (openai/openai/gpt-6.1-sol)

  • Tasks: 8 evaluation tasks (7 positive, 1 negative)

  • Dataset digest: sha256:b6a6c8ae48e6631377089dd22912257405540a3a1fecd6db54bdcce1e550ee79 (skill-evaluator-dataset-snapshot/1)

  • Attempts per task: 1

  • Environment: k8s-sandbox

  • Tier 2 evidence: required for publication

  • Tier 3 evidence: required for publication

Each task attempt ran in its own isolated sandbox pod.

Tier 1 LLM Provenance

SkillSpector provider, model, analyzer revision, and determinism evidence retained for this scan.

SkillProviderAdapterAnalyzerModelRevisionDeterminism
omniverse-realtime-viewernv_inferenceopenaimcp_tool_poisoningaws/anthropic/bedrock-claude-opus-5-52.13.4nondeterministic / provider_defaults
omniverse-realtime-viewernv_inferenceopenaisemantic_developer_intentaws/anthropic/bedrock-claude-opus-5-52.13.4nondeterministic / provider_defaults
omniverse-realtime-viewernv_inferenceopenaisemantic_quality_policyaws/anthropic/bedrock-claude-opus-5-52.13.4nondeterministic / provider_defaults
omniverse-realtime-viewernv_inferenceopenaisemantic_security_discoveryaws/anthropic/bedrock-claude-opus-5-52.13.4nondeterministic / provider_defaults
omniverse-realtime-viewernv_inferenceopenaimeta_analyzeraws/anthropic/bedrock-claude-opus-5-52.13.4nondeterministic / provider_defaults
  • Controls for omniverse-realtime-viewer: temperature=not set (source=provider_default, forwarded=no); seed=not set (source=unset, forwarded=no); reasoning_effort=not set (source=provider_default, forwarded=no)

What This Report Answers

The three-tier evaluation checks whether the skill:

  • is safe to use;

  • produces correct answers;

  • is discovered and activated when needed;

  • helps the agent complete the user's goal and expected workflow; and

  • avoids wasted skill and tool usage.

Results at a Glance

MeasureClaude Code (Baseline → Skill Uplift)Codex (Baseline → Skill Uplift)
Overall93.9% — baseline ran, but no comparable score was available; uplift unavailable88.0% — baseline ran, but no comparable score was available; uplift unavailable
Security100.0% → 100.0% (±0.0 points)100.0% → 93.8% (-6.2 points)
Correctness42.5% → 100.0% (+57.5 points)80.0% → 100.0% (+20.0 points)
Discoverability93.6% — baseline ran, but no comparable score was available; uplift unavailable91.4% — baseline ran, but no comparable score was available; uplift unavailable
Effectiveness54.2% → 89.1% (+34.9 points)66.7% → 82.3% (+15.6 points)
Efficiency86.9% — baseline ran, but no comparable score was available; uplift unavailable72.4% — baseline ran, but no comparable score was available; uplift unavailable

How to read this table: baseline is the same task attempted without the target skill. Scores are rounded to one decimal; threshold-adjacent values use additional precision so their displayed band matches the verdict. Uplift is derived from those displayed scores and shown in percentage points.

Example: 47.0% → 92.0% (+45.0 points) means the skill-assisted run scored 92.0%, 45.0 percentage points above its 47.0% no-skill baseline.

A partial dimension was calculated from only the available configured signals; review the detailed report before relying on it.

Comparison details

Shared-source comparisons use the same signals and weights on both conditions. They do not replace the full dimension scores above or change the publication verdict.

AgentDimensionBasisBaseline → With skill (uplift)Explanation
claude-codeDiscoverabilityDimension comparisonN/ADiscoverability is not applicable to the no-skill baseline; there is no installed skill to discover.
claude-codeEfficiencyToken-only comparison92.3% → 86.0% (-6.3 points)Only Token Efficiency is comparable; the full dimension scores use different evaluator sources.
codexDiscoverabilityDimension comparisonN/ADiscoverability is not applicable to the no-skill baseline; there is no installed skill to discover.
codexEfficiencyToken-only comparison84.7% → 81.8% (-2.9 points)Only Token Efficiency is comparable; the full dimension scores use different evaluator sources.

Token Usage

Actual Tier 3 execution usage is reported for every observed agent/case pair and both conditions.

AgentDataset caseWith skillWithout skillDeltaChangeCoverage
claude-codeAll cases2,843,994735,099+2,108,895+286.89%skill 8/8; base 8/8
claude-codeunrelated-python-median35,30235,140+162+0.46%skill 1/1; base 1/1
claude-codeviewer-browser-plan496,31375,284+421,029+559.25%skill 1/1; base 1/1
claude-codeviewer-native-plan758,17474,747+683,427+914.32%skill 1/1; base 1/1
claude-codeviewer-no-gpu282,641109,197+173,444+158.84%skill 1/1; base 1/1
claude-codeviewer-nvcf-cleanup-plan358,536109,072+249,464+228.71%skill 1/1; base 1/1
claude-codeviewer-pick-and-normal-review332,760109,120+223,640+204.95%skill 1/1; base 1/1
claude-codeviewer-scene-replacement361,339112,163+249,176+222.16%skill 1/1; base 1/1
claude-codeviewer-source-metadata218,929110,376+108,553+98.35%skill 1/1; base 1/1
codexAll cases1,388,192488,082+900,110+184.42%skill 8/8; base 8/8
codexunrelated-python-median13,31713,253+64+0.48%skill 1/1; base 1/1
codexviewer-browser-plan143,60949,170+94,439+192.07%skill 1/1; base 1/1
codexviewer-native-plan99,69558,871+40,824+69.34%skill 1/1; base 1/1
codexviewer-no-gpu75,06258,192+16,870+28.99%skill 1/1; base 1/1
codexviewer-nvcf-cleanup-plan656,841110,393+546,448+495.00%skill 1/1; base 1/1
codexviewer-pick-and-normal-review188,42898,380+90,048+91.53%skill 1/1; base 1/1
codexviewer-scene-replacement125,03441,679+83,355+199.99%skill 1/1; base 1/1
codexviewer-source-metadata86,20658,144+28,062+48.26%skill 1/1; base 1/1
ALL AGENTSDataset aggregate4,232,1861,223,181+3,009,005+246.00%skill 16/16; base 16/16

Prompt tokens include cached reads, so total tokens are prompt + completion (cached is not added twice). The Efficiency score uses (prompt - cached) + completion. Change is 100 * (with - without) / without; negative means fewer tokens. N/A comparisons include their reason in the coverage column; coverage is never estimated.

Tier Status

TierPurposeStatusEvidence
Tier 1Static validationPASSED WITH OBSERVATIONS11 validator(s); 70 finding(s)
Tier 2Semantic deduplicationPASSED WITH OBSERVATIONS2 validator(s); 54 finding(s)
Tier 3Live agent evaluationPASS2 agent(s); 8 task(s)

Findings and Observations

<details> <summary>Show detailed findings and successful checks</summary>

  • HIGH DUPLICATE/duplicate: Duplicate content found across references/aov-switching/README.md and references/ovrtx-rendering/README.md and references/usd-viewer-app/README.md: "## Processed GPU outputs" in references/aov-switching/README.md (lines 206-213) vs "## Processed GPU outputs" in references/ovrtx-rendering/README.md (lines 433-440) vs "## Processed GPU outputs" in references/usd-viewer-app/README.md (lines 91-98) (references/aov-switching/README.md:206)

  • HIGH DUPLICATE/duplicate: Duplicate content found across SKILL.md and references/dependencies/README.md and references/routing.md: "## Solid Modeling: Upstream First" in SKILL.md (lines 67-76) vs "## USD BRep: Public Solid Modeling Dependency" in references/dependencies/README.md (lines 77-108) vs "## Solid Modeling: Upstream First" in references/routing.md (lines 349-362) (SKILL.md:67)

  • HIGH DUPLICATE/duplicate: Duplicate content found across references/cpp-native-viewer/interaction-features.md and references/native-picking-selection/README.md and references/object-selection/README.md: "## Native Picking" in references/cpp-native-viewer/interaction-features.md (lines 92-93) vs "## Native Picking" in references/cpp-native-viewer/interaction-features.md (lines 173-191) vs "## Decode Pick Results" in references/native-picking-selection/README.md (lines 144-183) vs "## Decode Pick Hits" in references/object-selection/README.md (lines 150-187) (references/cpp-native-viewer/interaction-features.md:92)

  • HIGH DUPLICATE/duplicate: Duplicate content found across references/dependencies/environment-validation.md and references/dependencies/ovrtx.md and references/ovrtx-rendering/README.md and references/ovui-local-viewer-recipe/setup-shell-renderer.md and references/streaming-viewer-recipe/server-runtime.md and references/troubleshooting/README.md: "## Environment Variable Summary" in references/dependencies/environment-validation.md (lines 3-43) vs "## ovrtx" in references/dependencies/ovrtx.md (lines 32-37) vs "## ovrtx" in references/dependencies/ovrtx.md (lines 43-51) vs "## Environment" in references/ovrtx-rendering/README.md (lines 338-347) vs "## Common Errors" in references/ovrtx-rendering/README.md (lines 408-432) vs "## 2. Install Dependencies And Configure The Environment" in references/ovui-local-viewer-recipe/setup-shell-renderer.md (lines 29-33) vs "## 2. Install Dependencies And Configure The Environment" in references/streaming-viewer-recipe/server-runtime.md (lines 43-49) vs "## Common Error Map" in references/troubleshooting/README.md (lines 63-101) (references/dependencies/environment-validation.md:3)

  • HIGH DUPLICATE/duplicate: Duplicate content found across references/ovui-local-viewer-recipe/interaction-features.md and references/render-settings/README.md and references/streaming-viewer-recipe/interaction-features.md: "## 11. Add Render Settings And Lighting Controls" in references/ovui-local-viewer-recipe/interaction-features.md (lines 190-196) vs "## Capability-Driven Settings" in references/render-settings/README.md (lines 22-54) vs "## 13. Add Render Settings And Lighting Controls" in references/streaming-viewer-recipe/interaction-features.md (lines 172-178) (references/ovui-local-viewer-recipe/interaction-features.md:190)

  • 119 additional finding(s) are available in the full evaluation artifacts.

</details>

Scoring Methodology

<details> <summary>Show dimension definitions, source signals, and thresholds</summary>

DimensionQuestionScored signals
SecurityIs it safe to use?security (100%)
CorrectnessIs the answer correct?accuracy (100%)
DiscoverabilityWas the right skill loaded when needed?skill_execution (100%)
EffectivenessDid the skill help complete the task?goal_accuracy (50%) + behavior_check (50%)
EfficiencyDid it avoid wasted tool calls and token usage?skill_efficiency (50%) + token_efficiency (50%)
  • Dimension bands: PASS at 50% or above; NEUTRAL from 40% to below 50%; FAIL below 40%.

  • Overall Tier 3 lift: PASS at +5 points or more; FAIL at -10 points or less; values between those bands are NEUTRAL.

  • Overall verdict: PASS only when every configured dimension passes for at least one supported agent. Lift is reported as diagnostic evidence and does not override this gate.

  • The 50% attempt pass threshold is a separate per-task gate; it is not the dimension pass threshold.

  • Effectiveness is the equal-weight mean of goal completion (goal_accuracy) and expected workflow adherence (behavior_check).

  • Efficiency is 50% tool-call productivity (the backward-compatible skill_efficiency wire id) and 50% token_efficiency. Positive-case skill routing is scored under Discoverability, not Efficiency; a negative case without a routing target is N/A. N/A sources are omitted, remaining weights are renormalized, and the dimension is marked partial.

Signals present in this run:

  • security (Security): unsafe operations, secret leakage, and unauthorized access.

  • skill_execution (Skill Execution): whether the expected skill was selected, decoys were avoided, and the workflow executed.

  • skill_efficiency (Tool Productivity): tool-call productivity (legacy wire id; routing is scored under Discoverability).

  • accuracy (Accuracy): final-answer correctness against the reference answer.

  • goal_accuracy (Goal Accuracy): whether the user's goal was achieved.

  • behavior_check (Behavior Check): whether the expected workflow behavior was followed.

  • token_efficiency (Token Efficiency): actual uncached prompt plus completion usage (50% of Efficiency).

</details>

Freshness

Regenerate this benchmark when the skill, evaluation dataset, target agent/model, evaluator version, environment, or scoring policy changes.

Requirements and compatibility

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Needs: Needs Python, Needs Node.js

The author says: Orchestrator skill. Downstream focused references may require NVIDIA GPUs, ovrtx, ovstream, ovui, OpenUSD, Python, Node/React, Tauri, Electron, C++, or cloud GPU deployment access depending on the selected viewer path.

Security

What our scanner noticed· Medium risk

  • Large base64-encoded blobs
  • Instructions that use the network

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Created by
NVIDIA Omniverse
Publisher
NVIDIA (Official)
Source
NVIDIA/skills · skills/omniverse-realtime-viewer · commit fce3cca
Licence
Apache License 2.0 (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE-APACHE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by NVIDIA Omniverse or NVIDIA.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download omniverse-realtime-viewer.zip