New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Official agent skill

Omniverse Realtime Viewer

by NVIDIA in NVIDIA/skills

Use as the top-level router for Omniverse Realtime Viewer USD app requests and focused viewer reference documents.

OfficialApache-2.0Auto-check passed

Install Omniverse Realtime Viewer

skills CLI
$ npx skills add NVIDIA/skills --skill omniverse-realtime-viewer -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install NVIDIA/skills omniverse-realtime-viewer --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/NVIDIA/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/omniverse-realtime-viewer .claude/skills/omniverse-realtime-viewer && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
omniverse-realtime-viewer
GitHub stars
3.5k
Token cost
~2.7k tokens
SKILL.md length
838 words
Files
183 (incl. references)
Skills in repo
386
Repo updated
First seen
Licence
Apache-2.0

At a glance

Use as the top-level router for Omniverse Realtime Viewer USD app requests and focused viewer reference documents.

  • Works in 10 steps: Read references/routing.md to choose the… → Read references/conventions.md before… → For broad viewer requests, read… → …
  • SKILL.md covers Instructions, Read Order, Non-Negotiables and Focused Reference Families, plus 4 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Omniverse Realtime Viewer is an agent skill from NVIDIA/skills, published by the product's own GitHub organization. Use as the top-level router for Omniverse Realtime Viewer USD app requests and focused viewer reference documents.

Its SKILL.md is about 2.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 188 other files, including reference files (for example `BENCHMARK.md`, `agents/openai.yaml` and `evals/evals.json`). Compatibility notes: Orchestrator skill. Downstream focused references may require NVIDIA GPUs, ovrtx, ovstream, ovui, OpenUSD, Python, Node/React, Tauri, Electron, C++, or cloud…

The repository describes itself as: Agent Skills for NVIDIA products — install into Claude Code, Codex, and other coding agents to run Physical AI, robotics, simulation, CUDA, and RAG workflows end to end. The licence is Apache-2.0.

Example prompts

  • “/omniverse-realtime-viewer”

Requirements

  • Python 3
  • Compatibility (from SKILL.md): 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.

Workflow steps

10 steps, taken from the first numbered list in SKILL.md.

  1. Read references/routing.md to choose the delivery path and focused references.
  2. Read references/conventions.md before implementing camera, input,
  3. For broad viewer requests, read references/usd-viewer-app/README.md.
  4. If the delivery path is unclear, read references/streaming-vs-local/README.md.
  5. If the prompt includes layout, panels, controls, inspectors, status, or UX,
  6. For viewport interaction, read references/viewer-input-routing/README.md before
  7. For new viewer apps or ovrtx work, read the ovstage references before
  8. For NVCF self-hosted deployment, read references/cloud-deployment/nvcf-self-hosted.md before the selected cloud-deployment and streaming…
  9. Read only the focused capability references needed for the requested app.
  10. Use references/validation.md to capture review evidence before handoff.

What it can do on your machine

Read from SKILL.md and the folder at commit dfdd080. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • 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.

    From compatibility in the SKILL.md frontmatter.

Context cost

Omniverse Realtime Viewer loads about 2.7k tokens when it runs, and up to ~292k if it reads all its reference files. Until then it costs about 35 tokens; SKILL.md has 838 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~35
When it runs · the whole SKILL.md, loaded when a task matches
~2.7k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~292k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from NVIDIA/skills at commit dfdd080, republished under its Apache-2.0 licence (© NVIDIA). 838 words, ~2,734 tokens.

Download SKILL.mdSave it as .claude/skills/omniverse-realtime-viewer/SKILL.md (or your agent's skills folder). This skill also uses 182 other files; get the full folder from GitHub.
name
omniverse-realtime-viewer
description
Use as the top-level router for Omniverse Realtime Viewer USD app requests and focused viewer reference documents.
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.
version
0.2.0
license
Apache-2.0
tools
Read, Shell, Write
metadata.author
NVIDIA Omniverse
metadata.tags
omniverse, usd, viewer, workflow
metadata.domain
ai-ml
metadata.languages
python, typescript, cpp
<!-- SPDX-FileCopyrightText: Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved. -->
<!-- SPDX-License-Identifier: Apache-2.0 -->

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

  1. Read references/routing.md to choose the delivery path and focused references.
  2. Read references/conventions.md before implementing camera, input, selection, viewport, streaming protocol, scene loading, or environment behavior.
  3. For broad viewer requests, read references/usd-viewer-app/README.md.
  4. If the delivery path is unclear, read references/streaming-vs-local/README.md.
  5. If the prompt includes layout, panels, controls, inspectors, status, or UX, read 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.
  6. For viewport interaction, read references/viewer-input-routing/README.md before references/camera-controls/README.md, references/native-picking-selection/README.md, or references/object-selection/README.md.
  7. For new viewer apps or ovrtx work, read the ovstage references before renderer, scene loading, stage management, camera, selection, or transform write references.
  8. For NVCF self-hosted deployment, read references/cloud-deployment/nvcf-self-hosted.md before the selected cloud-deployment and streaming references.
  9. Read only the focused capability references needed for the requested app.
  10. Use references/validation.md to capture review evidence before handoff.

Non-Negotiables

  • Use ovrtx for all USD and 3D rendering.
  • Browser apps display an ovstream WebRTC 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 ovrtx path 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, OVStage runtime state, or app state.
  • Keep one owner for renderer.step(), stage mutation, native picking, selection writes, OVStage publication, and live attribute writes.
  • Use OVStage runtime writes for interchangeable transform animation, material/effect attributes, visibility toggles, physics pose samples, and reversible viewer-owned state. Keep native OVRTX APIs for rendering, pick queues, and selection outline visualization.
  • Keep dependency acquisition in references/dependencies/README.md and deployment choices in references/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/ovstage-runtime/README.md, references/ovstage-population/README.md, references/ovstage-data-plane/README.md, references/ovstage-ovrtx-integration/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/camera-auto-select/README.md, references/camera-picker/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/physics-simulation/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/physics-simulation/README.md.
  • Infrastructure: references/dependencies/README.md, references/windows-native-setup/README.md, references/cloud-assets/README.md, references/cloud-deployment/README.md, references/cloud-deployment/nvcf-self-hosted.md, references/cloud-deployment/nvcf-viewer-container-contract.md, references/cloud-deployment/gpu-container-runtime.md, references/cloud-deployment/container-image-build.md, references/cloud-deployment/webrtc-network-diagnostics.md, references/troubleshooting/README.md.
  • AI/Agent: references/a2ui-scene-copilot/README.md.
  • CAE/CFD visualization: references/cae-cfd-visualization/README.md, references/cae-cfd-visualization/data-and-operators.md, references/cae-cfd-visualization/cae-data-ingestion.md, references/cae-cfd-visualization/temporal-playback.md, references/cae-cfd-visualization/usd-authoring-and-materials.md, references/cae-cfd-visualization/ovstage-render-and-camera.md, references/cae-cfd-visualization/ovui-controls.md, references/cae-cfd-visualization/glyphs.md, references/cae-cfd-visualization/volume-rendering.md, references/cae-cfd-visualization/driving-cae-viz-via-ovstage.md, references/cae-cfd-visualization/emitter-and-seed-sources.md, references/cae-cfd-visualization/streaming-cae-viewer.md, references/cae-cfd-visualization/rtwt-blueprint-recreation.md, references/cae-cfd-visualization/coordinate-systems-and-up-axis.md.
Show full SKILL.md (323 more words)Show less

Build Workflow

  1. Classify the prompt by delivery path, target user, required capabilities, runtime environment, validation needs, and explicit constraints.
  2. 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.
  3. Read selected references before writing app code. Follow their build order, import order, data-channel contracts, and renderer ownership rules.
  4. Implement the OVStage population/data-plane path and core render path first, then input routing and camera, then selection and data panels, then scene/settings features, then packaging or deployment.
  5. Treat the selected references as the behavior contract for API shape, compatibility, and generated project structure.
  6. 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.
  • For a "visualize CAE/CFD data in realtime" request, treat CAE/CFD as a layer, not a standalone app: first pick the delivery path (references/streaming-vs-local/README.md), build the base viewer with the matching recipe (references/ovui-local-viewer-recipe/README.md or references/streaming-viewer-recipe/README.md), then layer references/cae-cfd-visualization/README.md (data → operators → USD authoring → scene) and wire controls via references/cae-cfd-visualization/driving-cae-viz-via-ovstage.md.

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.

ovstage References

For all new viewer applications, read these before renderer, scene, interaction, or delivery references:

  • references/ovstage-runtime/README.md — runtime ownership, ordinals, publication, and recovery.
  • references/ovstage-population/README.md — composed USD population and scene generations.
  • references/ovstage-data-plane/README.md — queries, writes, transforms, and runtime DTOs.
  • references/ovstage-ovrtx-integration/README.md — attached renderer loop and runtime integration contract.

© NVIDIA, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 182 other files (references) in skills/omniverse-realtime-viewer of NVIDIA/skills.

  • SKILL.md
  • BENCHMARK.md
  • agents/openai.yaml
  • evals/evals.json
  • references/a2ui-scene-copilot/README.md
  • references/aov-switching/README.md
  • references/cae-cfd-visualization/README.md
  • references/cae-cfd-visualization/cae-data-ingestion.md
  • references/cae-cfd-visualization/coordinate-systems-and-up-axis.md
  • references/cae-cfd-visualization/data-and-operators.md
  • references/cae-cfd-visualization/driving-cae-viz-via-ovstage.md
  • references/cae-cfd-visualization/emitter-and-seed-sources.md
  • references/cae-cfd-visualization/glyphs.md
  • references/cae-cfd-visualization/ovstage-render-and-camera.md
  • references/cae-cfd-visualization/ovui-controls.md
  • … and 168 more

Open the folder on GitHubat commit dfdd080

Compare with similar skills

Omniverse Realtime Viewer next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Omniverse Realtime Viewer compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Omniverse Realtime Viewer this skillNVIDIA/skills3.5k—~2.7kAutomated safety check: PassApache-2.0
Router Onweave-os/router5.6k—~169Automated safety check: PassApache-2.0
Router Offweave-os/router5.6k—~183Automated safety check: PassApache-2.0
Acp Routeropenclaw/openclaw392k—~2.4kAutomated safety check: PassMIT
React Router Developmentremix-run/react-router57k1 repos~1.5kAutomated safety check: PassMIT
Developing PDF ViewerTriliumNext/Trilium38k—~1.8kAutomated safety check: PassAGPL-3.0

Similar skills

  • Router On

    weave-os/router

    Route Codex through the Weave Router again (turn it back on).

    5.6k GitHub stars~169 tokensUpdated today
    Auto-check passed

  • Router Off

    weave-os/router

    Route Codex to its default provider again (turn the Weave Router off).

    5.6k GitHub stars~183 tokensUpdated today
    Auto-check passed

  • Acp Router

    openclaw/openclaw

    Route plain-language requests for Claude Code, Cursor, Copilot, OpenClaw ACP, OpenCode, Gemini CLI, Qwen, Kiro, Kimi, iFlow, Factory Droid, Kilocode, or explicit ACP harness work into either…

    392k GitHub stars~2.4k tokensUpdated today
    Writing & ContentAuto-check passed

  • React Router Development

    remix-run/react-router

    Guides work on React Router apps by first identifying whether the app uses Framework, Data or Declarative mode, then loading the matching reference and the installed package docs.

    57k GitHub starsUsed in 1 repo~1.5k tokens
    Frontend & DesignAuto-check passed

  • Developing PDF Viewer

    TriliumNext/Trilium

    A skill your agent uses when changing Trilium's built-in PDF viewer — anything under packages/pdfjs-viewer (the code injected into Mozilla's PDF.js viewer: bootstrap.ts, annotations.ts, pages.ts…

    38k GitHub stars~1.8k tokensUpdated today
    Documents & OfficeAuto-check passed

  • Server TRPC Router Guide

    lobehub/lobehub

    Conventions for LobeHub's server tRPC routers: file locations, middleware that injects models into ctx, procedure patterns, aggregated detail endpoints and return shapes.

    83k GitHub stars~904 tokensUpdated today
    Backend & APIsAuto-check passed

More from NVIDIA/skills

All 386 skills in this repo

  • Vss Deploy Detection Tracking 2D

    NVIDIA/skills

    Official

    A skill your agent uses when the user wants to deploy, run, debug, tear down, or call the REST API of the RTVI-CV 2D detection / tracking microservice.

    3.5k GitHub starsUsed in 1 repo~4.5k tokens
    Auto-check passed

  • HSB IP Def File Tool

    NVIDIA/skills

    Official

    Generates, validates, compares and explains HOLOLINK_def.svh macro files for the HSB IP, using bundled Python scripts and asking before it writes anything.

    3.5k GitHub stars~2.9k tokensUpdated yesterday
    Auto-check passed

  • Isaac Sim Mission Control Showcase

    NVIDIA/skills

    Official

    Runs and validates an end-to-end Mission Control demo in a locally installed Isaac Sim, with a Nova Carter robot driven through a Python server.

    3.5k GitHub stars~4.8k tokensUpdated yesterday
    Auto-check passed

  • Defect Image Generation with Cosmos AnomalyGen

    NVIDIA/skills

    Official

    Orchestrates defect image generation for PCBA, metal surface and glass inspection with NVIDIA Cosmos AnomalyGen on OSMO, from cold-start Day 0 to real-photo Day 1 labeling.

    3.5k GitHub stars~5k tokensUpdated yesterday
    Auto-check: notes

  • Physical AI Video Augmentation on OSMO

    NVIDIA/skills

    Official

    Orchestrates video data augmentation and auto-labeling workflows on OSMO, from flow selection and preflight checks to submission, monitoring and output download.

    3.5k GitHub stars~4.7k tokensUpdated yesterday
    Auto-check: notes

  • TAO Detection KPI Analysis

    NVIDIA/skills

    Official

    Runs NVIDIA TAO Data Services KPI analysis on object detection results, comparing predictions to ground truth and writing per-class precision, recall and AP to a CSV.

    3.5k GitHub stars~2.7k tokensUpdated yesterday
    Auto-check: notes

Questions about Omniverse Realtime Viewer

What does Omniverse Realtime Viewer do?

Use as the top-level router for Omniverse Realtime Viewer USD app requests and focused viewer reference documents. Omniverse Realtime Viewer is an agent skill from NVIDIA/skills, published by the product's own GitHub organization. Use as the top-level router for Omniverse Realtime Viewer USD app requests and focused viewer reference documents.

How do I install Omniverse Realtime Viewer in Claude Code?

Run `npx skills add NVIDIA/skills --skill omniverse-realtime-viewer -a claude-code`. Or copy the skill folder (skills/omniverse-realtime-viewer in NVIDIA/skills) into .claude/skills/omniverse-realtime-viewer in your project. Claude Code loads it when a task matches its description.

How do I install Omniverse Realtime Viewer in Codex?

Run `npx skills add NVIDIA/skills --skill omniverse-realtime-viewer -a codex`. Or copy the skill folder (skills/omniverse-realtime-viewer in NVIDIA/skills) into .agents/skills/omniverse-realtime-viewer in your project. Codex loads it when a task matches its description.

Can I use Omniverse Realtime Viewer in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add NVIDIA/skills --skill omniverse-realtime-viewer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/omniverse-realtime-viewer, .gemini/skills/omniverse-realtime-viewer, .github/skills/omniverse-realtime-viewer and .opencode/skills/omniverse-realtime-viewer in your project.

What does Omniverse Realtime Viewer need to run?

SKILL.md names no scripts, command-line tools or credentials: Omniverse Realtime Viewer is instructions for the agent only. Our summary lists: Python 3. Compatibility (from SKILL.md): 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. .

Does Omniverse Realtime Viewer access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Omniverse Realtime Viewer safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Omniverse Realtime Viewer use?

Omniverse Realtime Viewer is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Omniverse Realtime Viewer use?

About 2.7k tokens (SKILL.md is roughly 11k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 289k tokens, read only when the agent opens those files.

What are the alternatives to Omniverse Realtime Viewer?

Skills that share tags, products or a category with Omniverse Realtime Viewer: Router On (weave-os/router, 5.6k stars), Router Off (weave-os/router, 5.6k stars), Acp Router (openclaw/openclaw, 392k stars) and React Router Development (remix-run/react-router, 57k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Omniverse Realtime Viewer?

NVIDIA (a GitHub organization, an official publisher) maintains it in NVIDIA/skills, which has 3,546 GitHub stars. The repository holds 386 skills in this directory. The repository was last updated on October 9, 2026.

Source: NVIDIA/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.