Omniverse Realtime Viewer
Ship an RTX-rendered OpenUSD viewer or demo app on Omniverse using the ovrtx skill package and focused reference guides.
Overview
Omniverse Realtime Viewer is an agent skill for the Build phase that guides creation of RTX-rendered OpenUSD viewer apps with ovrtx and Omniverse-focused delivery, UI, interaction, and validation references.
Install
npx skills add https://github.com/nvidia/skills --skill omniverse-realtime-viewerWhat is this skill?
- Default prompt targets Omniverse Realtime Viewer apps with ovrtx USD rendering
- Skill package splits guidance across delivery, UI, interaction, and validation references
- RTX-rendered USD viewer focus for agent-led Omniverse app builds
- NVSkills-Eval external profile documented pre-publication (overall verdict FAIL in report)
- Benchmark dimensions: security, correctness, discoverability, effectiveness, efficiency
- 3-Tier NVSkills-Eval evaluation summarized in skill readme
Adoption & trust: 1 installs on skills.sh; 1.1k GitHub stars; trending (+100% hot-view momentum).
What problem does it solve?
You need an Omniverse USD viewer with RTX rendering but lack a structured agent workflow for delivery, UI, interaction, and validation.
Who is it for?
Indie or solo technical artists and engineers building Omniverse/OpenUSD viewer prototypes on RTX with agent assistance.
Skip if: Teams not using Omniverse or USD who only need a standard 2D web dashboard or unrelated API backend.
When should I use this skill?
Build an Omniverse Realtime Viewer app using ovrtx for USD rendering and the appropriate focused references for delivery, UI, interaction, and validation.
What do I get? / Deliverables
You get an agent-led path to a Realtime Viewer-style USD app using ovrtx and the skill’s reference slices, with evaluation caveats noted before you rely on it in production workflows.
- Realtime Viewer-oriented USD app structure guided by ovrtx references
- UI, interaction, and validation steps aligned to skill references
- Documented pre-publication eval outcome for workflow risk awareness
Recommended Skills
Journey fit
Canonical shelf is Build because the skill drives implementing viewer apps, UI, interaction, and delivery—not distribution or production ops. Frontend fits RTX viewport apps, USD scene presentation, and user interaction patterns described in the Realtime Viewer workflow.
How it compares
Use as a specialized Omniverse viewer workflow skill, not as a generic frontend component library or MCP server.
Common Questions / FAQ
Who is omniverse-realtime-viewer for?
Solo builders and small teams shipping RTX OpenUSD viewer experiences on NVIDIA Omniverse who want packaged agent instructions instead of piecing together docs manually.
When should I use omniverse-realtime-viewer?
During Build when you are implementing viewer delivery, viewport UI, interaction hooks, or validation for a Realtime Viewer app—typically after you have committed to Omniverse and USD as your runtime.
Is omniverse-realtime-viewer safe to install?
Review the Security Audits panel on this Prism page and the skill’s NVSkills-Eval security dimension notes; do not invent audit pass counts—validate permissions and sandbox Omniverse tooling in your environment.
SKILL.md
READMESKILL.md - Omniverse Realtime Viewer
interface: display_name: "Omniverse Realtime Viewer" short_description: "Build RTX-rendered USD viewer apps with the OV skill package." default_prompt: "Build an Omniverse Realtime Viewer app using ovrtx for USD rendering and the appropriate focused references for delivery, UI, interaction, and validation." # Evaluation Report Evaluation of the `omniverse-realtime-viewer` skill before publication through NVSkills-Eval. This benchmark summarizes 3-Tier Evaluation from NVSkills-Eval results for the skill. The goal is to document whether the skill is safe, discoverable, effective, and useful for agents before it is published for broader workflow use. ## Evaluation Summary - Skill: `omniverse-realtime-viewer` - Evaluation date: 2026-05-28 - NVSkills-Eval profile: `external` - Overall verdict: FAIL - Tier 3 live agent evaluation: not available in this report ## Agents Used - Tier 3 agent details were not available in this report. ## Metrics Used Reported benchmark dimensions: - Security: checks whether skill-assisted execution avoids unsafe behavior such as secret leakage, destructive commands, or unauthorized access. - Correctness: checks whether the agent follows the expected workflow and produces the correct final output. - Discoverability: checks whether the agent loads the skill when relevant and avoids using it when irrelevant. - Effectiveness: checks whether the agent performs measurably better with the skill than without it. - Efficiency: checks whether the agent uses fewer tokens and avoids redundant work. Underlying evaluation signals used in this run: - No Tier 3 evaluation signal details were available in this report. ## Test Tasks Tier 3 evaluation task details were not available in this report. ## Results Tier 3 dimension rollup was not available in this report. ## Tier 1: Static Validation Summary Tier 1 validation passed with observations. NVSkills-Eval ran 9 checks and found 32 total findings. Top findings: - MEDIUM PII/gps_coordinates: GPS coordinates (location information) (`references/stage-hierarchy/fallback-worker-protocol.md:55`) - MEDIUM PII/gps_coordinates: GPS coordinates (location information) (`references/stage-hierarchy/fallback-worker-protocol.md:56`) - MEDIUM PII/gps_coordinates: GPS coordinates (location information) (`references/headless-shm-cli/README.md:156`) - MEDIUM PII/gps_coordinates: GPS coordinates (location information) (`references/headless-shm-cli/README.md:169`) - MEDIUM PII/gps_coordinates: GPS coordinates (location information) (`references/cpp-native-viewer/interaction-features.md:20`) ## Tier 2: Deduplication Summary Tier 2 validation reported findings. NVSkills-Eval ran 2 checks and found 21 total findings. Top findings: - HIGH DUPLICATE/duplicate: Duplicate content found across references/stage-hierarchy/README.md and references/stage-queries/README.md: "### `prim_list_handle` Use" in references/stage-hierarchy/README.md (lines 91-102) vs "## `prim_list_handle`" in references/stage-queries/README.md (lines 124-129) (`references/stage-hierarchy/README.md:91`) - HIGH DUPLICATE/duplicate: Duplicate content found across SKILL.md and references/conventions.md and references/routing.md and references/stage-hierarchy/fallback-worker-protocol.md and references/streaming-messages/server-handler-map.md and references/streaming-server/frame-loop-and-continuity.md and references/troubleshooting/scenario-playbooks.md and references/validation.md: "(preamble)" in SKILL.md (lines 1-3) vs "(preamble)" in references/conventions.md (lines 1-3) vs "(preamble)" in references/routing.md (lines 1-3) vs "(preamble)" in references/stage-hierarchy/fallback-worker-protocol.md (lines 1-3) vs "(preamble)" in references/streaming-messages/server-handler-map.md (lines 1-3) vs "(preamble)" in references/streaming-server/frame-loop-and-continuity.md (lines 1-3) vs "(preamble)" in references/troubleshooting/scenario-playbooks.md (lines 1-3) vs "(preamble)" in refe