Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →nvidia/omniverse-realtime-viewer
Use as the top-level router for Omniverse Realtime Viewer USD app requests and focused viewer reference documents.
Passed 18 of 21 test cases with the skill, and 6 of 21 without it.
and 14 more in the full report
13 fixed6 passed either way3 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 12 test cases the skill fixed. Same model, same prompt, with and without the skill.
Users reporting network latency issues during WebRTC streaming sessions need bandwidth and packet loss diagnostics. Which reference provides network diagnostic guidance for streaming clients?
| Checked | Without skill | With skill |
|---|---|---|
| The diagnostic tooling uses references/cloud-deployment/webrtc-network-diagnostics.md for troubleshooting streaming network performance. | Missed | Passed |
The instructions your model reads when the skill loads.
This is the top-level entry point for the Omniverse Realtime Viewer skill package. It is self-contained: all required routing, conventions, and validation guidance live in the selected references.
Use the focused reference documents as implementation recipes. This file chooses the right recipes and preserves the architectural rules that must hold across all generated viewer apps.
Start by classifying the requested viewer, then read only the references needed
for that delivery path and feature set. Implement the render path first, layer
interaction and UI behavior on top of it, and finish by capturing validation
evidence from references/validation.md.
references/routing.md to choose the delivery path and focused references.references/conventions.md before implementing camera, input,
selection, viewport, streaming protocol, scene loading, or environment
behavior.references/usd-viewer-app/README.md.references/streaming-vs-local/README.md.references/viewer-ux-workflow/README.md and then the focused viewer UI references.
This applies to React/WebRTC, Tauri, Electron, ovui, ovwidgets, and Dear
ImGui apps; "frontend" means user-facing UI, not only browser UI.references/viewer-input-routing/README.md before
references/camera-controls/README.md, references/native-picking-selection/README.md, or references/object-selection/README.md.ovstage references before
renderer, scene loading, stage management, camera, selection, or transform
write references.references/cloud-deployment/nvcf-self-hosted.md before the selected cloud-deployment and streaming references.references/validation.md to capture review evidence before handoff.test cases passed, vs 6 / 21 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.