omniverse-realtime-viewer
Use as the top-level router for Omniverse Realtime Viewer USD app requests and focused viewer reference documents.
Works with
0
total installs
0
this week
1.7K
GitHub stars
0
upvotes
Install Skill
Run in your terminal
0
installs
0
this week
1.7K
stars
Installation Guide
How to use omniverse-realtime-viewer on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your machine
- ›Node.js 16+ with npm — verify with
node --version - ›Active project directory where you want to add
omniverse-realtime-viewer
Run the install command
Execute 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.
Select Cursor when prompted
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Verify installation
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.
Security Notice
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.
Documentation
| 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 |
Omniverse Realtime Viewer
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.
Instructions
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.
Read Order
- Read
references/routing.mdto choose the delivery path and focused references. - Read
references/conventions.mdbefore implementing camera, input, selection, viewport, streaming protocol, scene loading, or environment behavior. - For broad viewer requests, read
references/usd-viewer-app/README.md. - If the delivery path is unclear, read
references/streaming-vs-local/README.md. - If the prompt includes layout, panels, controls, inspectors, status, or UX,
read
references/viewer-ux-workflow/README.mdand 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. - For viewport interaction, read
references/viewer-input-routing/README.mdbeforereferences/camera-controls/README.md,references/native-picking-selection/README.md, orreferences/object-selection/README.md. - Read only the focused capability references needed for the requested app.
- Use
references/validation.mdto capture review evidence before handoff.
Non-Negotiables
- Use
ovrtxfor all USD and 3D rendering. - Browser apps display an
ovstreamWebRTC video stream plus UI. The browser does not render USD geometry. - Do not substitute WebGL, Three.js, Babylon.js, PlayCanvas, A-Frame, model-viewer, react-three-fiber, glTF browser viewers, or other client-side 3D renderers.
- If local validation cannot run because the GPU/runtime environment is absent,
scaffold the
ovrtxpath and document the runtime requirement. Do not add a browser-renderer fallback. - Keep user USD files unmodified. Viewer cameras, render products, render vars, settings, selection metadata, and runtime state belong in session/composite layers or app state.
- Keep one owner for
renderer.step(), stage mutation, native picking, selection writes, and live attribute writes. - Keep dependency acquisition in
references/dependencies/README.mdand deployment choices inreferences/cloud-deployment/README.md; do not duplicate package locations or deployment setup.
Focused Reference Families
- Entry points and recipes:
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. - Rendering and stage:
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. - Delivery and runtime:
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. - Viewer UI/UX:
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. - Interaction:
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. - Infrastructure:
references/dependencies/README.md,references/windows-native-setup/README.md,references/cloud-assets/README.md,references/cloud-deployment/README.md,references/troubleshooting/README.md.
Build Workflow
- Classify the prompt by delivery path, target user, required capabilities, runtime environment, validation needs, and explicit constraints.
- Select a small reference set. Start with the recipe or routing reference, then add focused capabilities such as camera, picking, hierarchy, properties, render settings, transform tools, cloud assets, or deployment.
- Read selected references before writing app code. Follow their build order, import order, data-channel contracts, and renderer ownership rules.
- Implement the core render path first, then input routing and camera, then selection and data panels, then scene/settings features, then packaging or deployment.
- Treat the selected references as the behavior contract for API shape, compatibility, and generated project structure.
- Capture validation evidence before calling the viewer ready.
Examples
- For a browser viewer request, use the streaming recipe references plus camera, picking, hierarchy, properties, render settings, and stream-status references.
- For a local workstation viewer request, use the local or native delivery references plus renderer setup, stage loading, viewport input, and validation.
Completion Checklist
- Selected references match the user's intent and delivery path.
- No code path uses a browser-side 3D renderer for USD.
- The generated app has one clear owner for render stepping and stage mutation.
- User USD files remain untouched by viewer-owned session data.
- Camera, input, selection, scene loading, and stream behavior follow
references/conventions.md. - Setup/build/run results and visual interaction evidence are captured with
references/validation.md.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases
Task Automation & Efficiency
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Knowledge Enhancement
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Quality Improvement
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
Implementation Guide
Prerequisites
- ›Claude Desktop or compatible AI client with skill support
- ›Clear understanding of task or problem to solve
- ›Willingness to iterate and refine outputs
Time Estimate
15-45 minutes depending on use case complexity
Steps
- 1Install skill using provided installation command
- 2Test with simple use case relevant to your work
- 3Evaluate output quality and relevance
- 4Iterate on prompts to improve results
- 5Integrate into regular workflow if valuable
Common Pitfalls
- ⚠Expecting perfect results without iteration
- ⚠Not providing enough context in prompts
- ⚠Using skill for tasks outside its intended scope
- ⚠Accepting outputs without review and validation
Best Practices
✓ Do
- +Start with clear, specific prompts
- +Provide relevant context and constraints
- +Review and refine all outputs before using
- +Iterate to improve output quality
- +Document successful prompt patterns
✗ Don't
- −Don't use without understanding skill limitations
- −Don't skip validation of outputs
- −Don't share sensitive information in prompts
- −Don't expect skill to replace human judgment
💡 Pro Tips
- ★Be specific about desired format and style
- ★Ask for multiple options to choose from
- ★Request explanations to understand reasoning
- ★Combine AI efficiency with human expertise
When to Use This
✓ 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.
Learning Path
- 1Familiarize yourself with skill capabilities and limitations
- 2Start with low-risk, non-critical tasks
- 3Progress to more complex and valuable use cases
- 4Build expertise through regular use and experimentation
Related Skills
jetson-memory-audit
0nvidia/skills
cuopt-server-api-python
0nvidia/skills
jetson-print-bsp-info
0nvidia/skills
dynamo-troubleshoot
0nvidia/skills
cuopt-numerical-optimization-formulation
0nvidia/skills
jetson-customize-pcie
0nvidia/skills
Reviews
- DDhruvi Jain★★★★★Dec 24, 2024
We added omniverse-realtime-viewer from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- LLi Okafor★★★★★Dec 20, 2024
Useful defaults in omniverse-realtime-viewer — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- IIsabella Bhatia★★★★★Dec 4, 2024
omniverse-realtime-viewer has been reliable in day-to-day use. Documentation quality is above average for community skills.
- BBenjamin Rao★★★★★Nov 23, 2024
Solid pick for teams standardizing on skills: omniverse-realtime-viewer is focused, and the summary matches what you get after install.
- OOshnikdeep★★★★★Nov 15, 2024
omniverse-realtime-viewer reduced setup friction for our internal harness; good balance of opinion and flexibility.
- GGanesh Mohane★★★★★Oct 6, 2024
omniverse-realtime-viewer is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- LLuis Robinson★★★★★Sep 21, 2024
omniverse-realtime-viewer reduced setup friction for our internal harness; good balance of opinion and flexibility.
- NNaina Park★★★★★Sep 9, 2024
omniverse-realtime-viewer has been reliable in day-to-day use. Documentation quality is above average for community skills.
- NNaina Ndlovu★★★★★Aug 28, 2024
omniverse-realtime-viewer fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- CCharlotte Harris★★★★★Aug 12, 2024
omniverse-realtime-viewer is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
showing 1-10 of 27
Discussion
Comments — not star reviews- No comments yet — start the thread.