Use as the top-level router for Omniverse Realtime Viewer USD app requests and focused viewer reference documents.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionomniverse-realtime-viewerExecute the skills CLI command in your project's root directory to begin installation:
Fetches omniverse-realtime-viewer from nvidia/skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate omniverse-realtime-viewer. Access via /omniverse-realtime-viewer in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
0
total installs
0
this week
1.7K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
1.7K
stars
| name | omniverse-realtime-viewer |
| description | "Use as the top-level router for Omniverse Realtime Viewer USD app requests and focused viewer reference documents." |
| version | "0.1.0" |
| license | Apache-2.0 |
| tools | - Read - Shell - Write |
| compatibility | > 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. |
| metadata | author: NVIDIA Omniverse tags: - omniverse - usd - viewer - workflow domain: ai-ml languages: - python - typescript - cpp |
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.references/validation.md to capture review evidence before handoff.ovrtx for all USD and 3D rendering.ovstream WebRTC video stream plus UI. The browser
does not render USD geometry.ovrtx path and document the runtime requirement. Do not add a
browser-renderer fallback.renderer.step(), stage mutation, native picking,
selection writes, and live attribute writes.references/dependencies/README.md and deployment choices in
references/cloud-deployment/README.md; do not duplicate package locations or deployment setup.references/usd-viewer-app/README.md, references/streaming-viewer-recipe/README.md,
references/ovui-local-viewer-recipe/README.md, references/streaming-vs-local/README.md, references/electron-shm-viewer/README.md,
references/ovwidgets-editor-shell/README.md.references/ovrtx-rendering/README.md, references/stage-loading/README.md, references/stage-management/README.md,
references/render-settings/README.md, references/aov-switching/README.md, references/stage-hierarchy/README.md, references/stage-queries/README.md,
references/stage-attribute-reads/README.md, references/prim-transform-safety/README.md, references/usd-sample-data/README.md.references/streaming-server/README.md, references/streaming-client/README.md,
references/streaming-messages/README.md, references/streaming-lifecycle/README.md, references/local-viewer/README.md,
references/tauri-local-viewer/README.md, references/cpp-native-viewer/README.md, references/headless-shm-cli/README.md,
references/viewer-backend-interface/README.md, references/webgl-shm-transport/README.md.references/viewer-ux-workflow/README.md, references/viewer-layout-patterns/README.md,
references/viewer-control-patterns/README.md, references/viewer-data-view-patterns/README.md,
references/viewer-feedback-status/README.md.references/viewer-input-routing/README.md, references/camera-controls/README.md,
references/object-selection/README.md, references/native-picking-selection/README.md, references/selection-feedback/README.md,
references/selection-animation/README.md, references/transform-manipulator/README.md, references/gl-viewport-overlay/README.md,
references/ovui-library/README.md, references/prim-pick-effects/README.md, references/prim-info-display/README.md,
references/viewport-overlays/README.md.references/dependencies/README.md, references/windows-native-setup/README.md, references/cloud-assets/README.md,
references/cloud-deployment/README.md, references/troubleshooting/README.md.references/conventions.md.references/validation.md.Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
nvidia/skills
nvidia/skills
nvidia/skills
nvidia/skills
nvidia/skills
nvidia/skills
We added omniverse-realtime-viewer from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Useful defaults in omniverse-realtime-viewer — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
omniverse-realtime-viewer has been reliable in day-to-day use. Documentation quality is above average for community skills.
Solid pick for teams standardizing on skills: omniverse-realtime-viewer is focused, and the summary matches what you get after install.
omniverse-realtime-viewer reduced setup friction for our internal harness; good balance of opinion and flexibility.
omniverse-realtime-viewer is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
omniverse-realtime-viewer reduced setup friction for our internal harness; good balance of opinion and flexibility.
omniverse-realtime-viewer has been reliable in day-to-day use. Documentation quality is above average for community skills.
omniverse-realtime-viewer fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
omniverse-realtime-viewer is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
showing 1-10 of 27