Capture clean render-only images and movies from Kit-CAE visualizations. Produces output without application UI - just the rendered scene. Supports high-resolution PNG/EXR screenshots, MP4 video with NVENC hardware encoding, and animated camera orbits. Triggers on requests for "capture image", "render screenshot"…
Shared foundation for Kit-CAE agent skills. Contains import APIs, visualization commands, stage discovery, format references, and utility scripts used by cae-visualization and cae-capture. Not invoked directly by users - loaded as a dependency by other CAE skills.
Run Kit-CAE as a WebRTC-streamed application that remote clients can view and control via data-channel messages. Provides a streaming-enabled .kit dep set, the wire-protocol reference, the messaging-API reference, a small reusable Python helper (OmniverseAPI), and a runnable reference handler (loadscene + scenes…
AGENTS.md instructions for NVIDIA-Omniverse/ovui, covering agents.md - ai agent guide for ovui, what this repo is, start here, repo layout (high-level) and common workflows.
Use when creating, modifying, inspecting, or reasoning about ovui UI from low-level atomic ovui widgets, including layout, Pixel/Percent/Fraction sizing, model-view widgets, TreeView/stage hierarchy trees, inputs, menus, windows, docking, viewport-like ovrtx panels, styling, or strict UI validation. Use when an agent…
Use this skill when the user asks to inspect, screenshot, automate, click, type into, or drive a running ovui/ovui-widgets application through the ovui-inspect FastAPI inspector. The skill provides an importable ovuiinspect module, an ovui-inspect CLI, and a screenshot-first mouse/keyboard workflow for controlling…
Install and run the packaged ovui USD Viewer with ovrtx and either OpenUSD, ovstage, or both data adapters. Use when creating a clean virtual environment from published wheels, selecting the adapter configuration, or launching ovuiwidgets.app against a USD file.
Use this skill when a user asks to create or validate a disposable standalone ovui/ovui-widgets application from the existing widget set. The application source should live outside the repo unless the user explicitly asks to productize it. The skill gives exact imports, runtime environment, ovrtx proof requirements…