omniverse-ui-widgets

Create and validate disposable OvWidgets applications with ovrtx renderer requirements.

51|5|Updated May 18, 2026
One-click install
npx skills add https://github.com/NVIDIA-Omniverse/ovui --skill omniverse-ui-widgets
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: omniverse-ui-widgets
Source: https://github.com/NVIDIA-Omniverse/ovui/tree/main/skills/omniverse-ui-widgets
Command: npx skills add https://github.com/NVIDIA-Omniverse/ovui --skill omniverse-ui-widgets

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Use this skill when a user asks to create or validate a disposable standalone OvUI/ovwidgets application from the existing widget set. The application source should live outside the repo unless the user explicitly asks to productize it. The skill covers exact imports, runtime environment, ovrtx proof requirements, widget wiring, menu/file-open wiring, and screenshot-first QA expectations. Do not use this skill for raw omni.ui atomic widget construction; use the omniverse-ui-apis skill instead.

Core Features & Use Cases

  • Provide durable, production-ready skeletons for disposable OvWidgets apps that reuse existing widgets while keeping app code outside the main repo.
  • Enforce ovrtx renderer requirements, stage/viewport/property wiring, and File > Open integration.
  • Use cases include quick demos, QA testing, or temporary prototyping without polluting the repository.

Quick Start

Create a disposable OvWidgets trial app using the provided references and open the included USD fixture to validate rendering.

Frequently Asked Questions about omniverse-ui-widgets

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a disposable OvWidgets app for QA testing?

This skill automates creating disposable OvWidgets applications for QA testing by generating standalone app skeletons from existing widgets. It enforces runtime environments, wiring patterns, and screenshot-first QA expectations while keeping app code outside the main repository.

What is the best way to prototype a standalone UI app without polluting the main repository?

Prototyping a standalone UI app without polluting the repository involves generating a disposable OvWidgets application. This skill enforces runtime environments, wiring patterns, and ovrtx renderer requirements while keeping the temporary app code outside the main source.

Can I use this skill to build raw omni.ui atomic widgets?

No, you cannot use this skill to build raw omni.ui atomic widgets. This skill focuses on wiring existing widgets into disposable applications for testing and demos. You should use the omniverse-ui-apis skill instead for atomic widget construction.

Does a disposable OvWidgets app require specific renderer and stage wiring configurations?

Yes, a disposable OvWidgets app requires specific renderer and stage wiring configurations. This skill enforces ovrtx renderer requirements, stage/viewport/property wiring, and File > Open integration to validate rendering and ensure functional standalone applications.

How do I validate USD rendering in a temporary Omniverse widget application?

To validate USD rendering in a temporary Omniverse widget application, this skill enforces screenshot-first QA expectations and provides references for USD fixtures. You open the included USD fixture to validate rendering within the generated disposable app.

When should I avoid using disposable OvWidgets applications for development?

You should avoid using disposable OvWidgets applications when building raw omni.ui atomic widgets or when you explicitly need to productize the application inside the main repository. This skill targets temporary testing, demos, and prototyping only.