NVIDIA-Omniverse
- 362 skills
- 0 followers
- 245 repo stars
- last week last updated
- ▌ Blender Python Execution · nvidia-omniverse bundleExecute and validate Blender Python through a Blender MCP provider using small, context-safe, idempotent transactions. Use when an agent must inspect or mutate a Blender scene, translate a Blender task into bpy code, recover from Blender code execution errors, or prove that an MCP-driven edit actually changed the intended scene.
- ▌ Blender Workflow Routing · nvidia-omniverse bundlePlan and route a Blender task across MCP, local OVRTX workflows, and optional upstream community production skills. Use for multi-step scene work, complete-scene requests, or when a user is unsure which Blender workflow to follow. Use blender-python-execution locally and blender-community-skill-bootstrap when detailed generic production recipes are not installed.
- ▌ Geometry Nodes For Ovrtx · nvidia-omniverse bundleAuthor, inspect, and prepare Blender Geometry Nodes assets for predictable OVRTX rendering and USD handoff. Use for procedural geometry, instances, fields, modifiers, or geometry that must survive add-on evaluation through documented add-on and runtime interfaces.
- ▌ Ovrtx Lighting And World · nvidia-omniverse bundleAuthor, inspect, and debug Blender 5.x lights and World/HDRI state for OVRTX conversion. Use when a scene is dark, overexposed, flat, contains unsupported light fields, or differs from a Blender reference.
- ▌ Nonvisual Materials · nvidia-omniverseAuthoring non-visual material labels for sensor simulation. Use when user asks to assign lidar/radar/acoustic material semantics, choose nonvisual base materials, coatings, or attributes, debug material IDs, or bind sensor-facing USD materials.
- ▌ Renderer Capability Abi · nvidia-omniverse bundleDefine and govern the shared renderer C ABI and backend capability contract so multiple backends stay interchangeable and parity is machine-checked. Use when Codex designs or changes the public renderer header, adds a capability/AOV/entry point, reports what a backend supports versus stubs, or wires renderer ABI conformance into CI. Pairs with contract-first-ffi (general FFI hygiene) and renderer-feature-validation-matrix (per-feature status).
- ▌ Blender Render And Export · nvidia-omniverse bundleRender Blender stills and export named scene objects to GLB or USD with explicit cameras, frames, absolute output paths, context preservation, operator capability checks, file verification, and structured JSON results. Use when an agent must produce a generic Blender render or interchange file without relying on optional community skills or confusing Blender output with native OVRTX output.
- ▌ Project Setup Python · nvidia-omniverseSetting up a new Python project that uses ovrtx. Use when user asks to create a new Python project, set up ovrtx in Python, create a pyproject.toml, or scaffold a Python app.
- ▌ Renderer Realtime Sensor · nvidia-omniverse bundleDesign real-time, headless, multi-camera renderers that produce reproducible sensor data for simulation and RL training. Use when Codex builds or reviews a renderer feeding a physics/RL loop (IsaacLab, Newton, MuJoCo), works on determinism/reproducibility, sensor AOVs (depth/segmentation/normals), multi-camera tiling, or the fidelity-versus-throughput target for a training sensor rather than an offline beauty render.
- ▌ Renderer Simulation Loop · nvidia-omniverse bundleDrive a renderer from a physics/RL simulation loop (IsaacLab, Newton, MuJoCo) — per-step transform/visibility updates from physics state, time handling, frame pacing, and the consumer contract. Use when Codex integrates a renderer into a training/sim loop, plumbs physics transforms or time into the scene, or debugs bodies-render-at-origin, stale-frame, per-env update, or pacing problems.
- ▌ Extend Ovrtx Lidar Capture · nvidia-omniverse bundleExtend the OVRTX Blender add-on with native LiDAR sensor authoring, runtime capability discovery, raw-return capture, coordinate conversion, accumulation, viewport presentation, and evidence. Use when adding LiDAR support rather than producing a synthetic point overlay.
- ▌ Extend Ovrtx Semantic Aovs · nvidia-omniverse bundleExtend the OVRTX Blender add-on with stable semantic and instance identity authoring, native semantic render-variable requests, typed buffer parsing, ID maps, tight boxes, UI controls, and validation. Use when adding semantic or instance AOV support.
- ▌ Ovrtx Semantic Aov Capture · nvidia-omniverse bundleDevelop and validate semantic or ID RenderVar capture through the public OVRTX add-on and native client. Use when developers customize semantic class, instance, segmentation, or ID AOV support. This skill requires typed native readback and durable USD semantics; it does not treat colored postprocessing as native evidence.
- ▌ Usd Inspect And Provenance · nvidia-omniverse bundleInspect a Blender-exported or supplied USD stage for composition, transforms, units, materials, cameras, render products, semantics, and physics while retaining source-to-derived provenance. Use before OVRTX/OVPhysX handoff, when a render looks wrong, or when a flattened package must be audited without mutating the original.
- ▌ Reading Render Output · nvidia-omniverseMapping rendered output to access pixel data on CPU or GPU. Use when user asks to get pixels, read an image, save a PNG, display rendered output, or access render var data.
- ▌ Layered Boundary Refactor · nvidia-omniverse bundleRefactor disjoint or duplicated projects into clear layered architecture with canonical contracts and thin adapters. Use when viewers, renderers, bindings, data libraries, plugins, or services overlap and need maintainable ownership boundaries without losing behavior.
- ▌ Extend Ovrtx Lighting World · nvidia-omniverse bundleExtend the OVRTX Blender add-on's light and World conversion, initial USD presentation, USD prim resolution, and interactive live edits. Use when adding Blender light fields or families, dome/World policies, topology classification, typed USD attributes, depsgraph routing, retained edits, or tests.
- ▌ Ovrtx Creative Hero Journey · nvidia-omniverse bundleTake a current Blender scene through a concise artist-facing path to a polished native OVRTX hero still: preserve a derivative, preflight, refine camera/look, run a smoke, render the final, and label provenance honestly. Use when an artist wants the whole presentation workflow without manually selecting every specialist skill.
- ▌ Ovrtx Lidar Runtime Capture · nvidia-omniverse bundleDevelop and validate a native OVRTX LiDAR capture path in the public add-on, including sensor/product identity, typed raw-return decoding, timing, coordinate frames, and truthfulness gates. Use when developers customize the add-on for LiDAR. The current multi-sensor LdrColor probe validates routing only and must not be presented as LiDAR output.
- ▌ Stepping And Rendering · nvidia-omniverseRunning a simulation step to produce rendered frames. Use when user asks to render a frame, step the renderer, simulate a sensor, or get an image from ovrtx.
- ▌ Onedrive Deployment · nvidia-omniverse bundleGuide for deploying, configuring, and integrating the OneDrive Storage Service for NVIDIA Omniverse with Kit App Streaming. Use when configuring Entra ID / Azure AD authentication (tenant ID, client ID, client secret, Graph API endpoints), setting up Microsoft Graph delegated permissions, choosing between Bearer pass-through and On-Behalf-Of (OBO) token flows, wiring the service into Kit App Streaming (discovery endpoints, redirect URIs, ingress auth extension), validating end-to-end connectivity, or troubleshooting deployment failures (invalid/expired credentials, missing Graph permissions, token acquisition/exchange failures, tenant ID / redirect URI mismatches). Also explains the underlying Graph API implementation and the OBO token lifecycle (acquisition, caching, expiry, renewal) and why each auth component is required.
- ▌ Usd Paths · nvidia-omniverseUse this skill when implementing or verifying USD path syntax, construction, and ordering.
- ▌ Extend Ovrtx Render Settings · nvidia-omniverse bundleExtend the OVRTX Blender add-on with renderer modes, RTPT controls, RenderProduct opinions, primvars, color presentation, diagnostics, and tests. Use when adding or changing renderer settings.
- ▌ Ovrtx Current Scene Workflow · nvidia-omniverse bundleBuild, edit, preview, and render the current Blender scene through the OVRTX Blender add-on. Use when a user wants OVRTX output from a new or existing `.blend`, wants to drive Blender through MCP and see live viewport updates, or needs a reproducible still from the current scene. The workflow uses the add-on's Blender boundary and an installed runtime
- ▌ Texture Uv Material Workflow · nvidia-omniverse bundleCreate and validate Blender UVs, atlases, PBR image materials, decals, and bake targets for Blender and OVRTX. Use when textures stretch, colors are wrong, alpha is black, baking fails, or a material must survive USD/MaterialX handoff. The OVRTX runtime/client is installed and not a required source checkout.
- ▌ Start Server · nvidia-omniverseUse when asked to start, run, launch, restart, or bring up the OVRTX Dev Variant Presenter server, stream, or viewport in this repo — also called the "variant studio" in the walkthrough video and earlier releases — or after the stream / GPU / server was lost and needs recovering. RTX required; validated on Windows.
- ▌
- ▌ Extend Ovrtx Render Sequences · nvidia-omniverse bundleExtend the OVRTX Blender add-on with persistent-session animated rendering, atomic scene updates, bounded refinement, one readback per frame, resume records, and temporal validation. Use when adding sequence capture or Blender final-render animation support.
- ▌ Extend Ovrtx Scene Generation · nvidia-omniverse bundleExtend the OVRTX Blender add-on's authored-scene generation for evaluated geometry, mesh topology, modifiers, Geometry Nodes, and object instances. Use when changing Blender-to-USD export coverage, identity mapping, topology fingerprints, sparse generation reconciliation, or tests.
- ▌ Agentic Codebase Cartography · nvidia-omniverse bundleMap unfamiliar or multi-repository codebases before refactoring, integration, or feature work. Use when Codex needs to analyze submodules, ownership boundaries, APIs, duplicate implementations, build/test surfaces, risk areas, and a practical refactor sequence before changing code.
- ▌ Portable Build Runtime Paths · nvidia-omniverse bundleMake native builds, command-line tools, viewers, plugins, shaders, test harnesses, and packaged artifacts portable across working directories, install trees, copied build trees, users, and machines. Use when Codex works on CMake/install rules, RPATH/RUNPATH, dynamic library lookup, shader or asset discovery, CLI resource paths, packaging, deployment, or bugs that only reproduce outside the repo root.
- ▌ Renderer Constrained Backend · nvidia-omniverse bundleBuild a renderer backend to a hard resource or capability budget — low VRAM, raster-only (no hardware ray tracing), or a portable/embedded GPU like OpenGL ES — where features must be baked, capped, or degraded rather than ported wholesale from the high-end backend. Use when Codex builds a low-end/portable backend, fits a GPU-memory budget, bakes materials instead of codegen, or makes a no-RT fallback match a reference renderer.
- ▌ Verification Led Development · nvidia-omniverse bundlePlan and execute code changes with focused verification at each layer. Use when implementing fixes or refactors that need builds, tests, smoke runs, screenshots, logs, benchmarks, or clear residual-risk reporting before handoff.
- ▌ Extend Ovrtx Interactive Edits · nvidia-omniverse bundleExtend the OVRTX Blender add-on with new interactive transform, material, light, world, UV, camera, physics, or semantic edit families. Use when implementing Blender depsgraph extraction, typed USD value conversion, live runtime submission, durable write routing, topology fallback, user diagnostics, and tests.
- ▌ Ovrtx Render Products And Aovs · nvidia-omniverse bundleProbe, customize, and validate OVRTX render-product and RenderVar/AOV readback in the public add-on and native client. Use when developers add beauty, HDR, depth, ID, semantic, or other products, or when diagnosing product identity, selection, iteration, dimensions, and decoding. Availability is capability-specific, not implied by this skill.
- ▌ Reference To 3d Reconstruction · nvidia-omniverse bundleReconstruct a measured Blender asset from one or more image references, wireframes, logos, or orthographic views, then validate scale, registered cameras, landmarks, silhouette, materials, and OVRTX output. Use for reference-locked modeling, orthographic image registration, pixel-to-world calibration, or explicit inferred-depth reporting; it needs Blender/MCP and the installed add-on.
- ▌ Configuring Lidar Sensors · nvidia-omniverseAuthoring and configuring OmniLidar sensor prims and lidar PointCloud render outputs. Use when user asks to create a lidar scene, configure an OmniLidar prim, choose lidar output frame/coordinate behavior, or request lidar PointCloud channels.
- ▌ Configuring Radar Sensors · nvidia-omniverseAuthoring and configuring OmniRadar sensor prims and radar PointCloud render outputs. Use when user asks to create a radar scene, configure an OmniRadar prim, choose radar output frame/coordinate behavior, configure radar scan outputs, or request radar PointCloud channels.
- ▌ Ovphysx Drop Contact Acceptance · nvidia-omniverse bundleAuthor and accept a reproducible OVPhysX rigid-body drop or contact test from Blender, including collision proxies, authoritative pose readback, settling, and visible contact evidence. Use when a user needs to prove that a SimReady prop falls, collides, and comes to rest through the installed OVRTX/OVPhysX runtime rather than a Blender-only animation.
- ▌ Reading Sensor Pointclouds · nvidia-omniverseMapping and reading lidar or radar PointCloud composite render-var tensors. Use when user asks how to access PointCloud output data, map Coordinates, Counts, Intensity, RCS, RadialVelocityMs, or TimeOffsetNs tensors, slice valid entries, or move sensor point clouds through CPU/CUDA memory. For channel meanings and units, use the interpreting-lidar-pointclouds or interpreting-radar-pointclouds skills.
- ▌ Renderer Stalled Parity Triage · nvidia-omniverse bundleReset renderer/reference parity work when beauty images, scalar metrics, repeated local tweaks, or narrow target slices stop improving. Use when signed residuals stay structured, AOVs disagree with beauty, noise or denoising hides lighting/shadow detail, equal-spp comparisons are misleading, reference metadata is uncertain, or several exposure/material/light/denoiser/transport experiments have been rejected without progress.
- ▌ Blender Sanitized Support Bundle · nvidia-omniverse bundleCollect Blender diagnostics locally and create a separate, sanitized support bundle for sharing. Use when preparing logs, reports, screenshots, scene metadata, or reproduction artifacts for troubleshooting or review.
- ▌ Legacy Retirement Clean History · nvidia-omniverse bundleIdentify and remove obsolete legacy, fallback, staging, compatibility, duplicate, generated, and reference code before creating clean initial commits or new project history. Use when a repo is being reset, consolidated, or prepared for a cleaner public history.
- ▌ Renderer Implementation Roadmap · nvidia-omniverse bundleSequence a nanoUSD renderer build from nothing into a correct, scalable backend using only the renderer skill set. Use when Codex starts a new renderer or backend, plans renderer milestones and phase order, decides what must be correct before the next layer, or needs the contracts-first build order and reduced-fixture corpus that turn the other renderer skills into a buildable plan with no reference renderer to copy from.
- ▌ Usd Layer Open · nvidia-omniverseUse this skill when implementing or verifying the generic boundary that opens a resolved USD layer resource and dispatches it to a registered layer-format handler.
- ▌ Animation Quality And Frame Range · nvidia-omniverse bundleAuthor, render, and review Blender animation over a declared frame range, including keyframes, shape keys, drivers, texture states, and camera motion. Use for OVRTX sequences, contact sheets, flicker/framing checks, or export decisions through the installed add-on/runtime.
- ▌ Blender Community Skill Bootstrap · nvidia-omniverse bundleLocate and install optional community Blender production skills from their upstream GitHub repository instead of rebundling them in this catalog. Use when an agent needs detailed generic recipes for Blender modeling, materials, UVs, lighting, cameras, rendering, animation, export, full-scene orchestration, or multi-skill harmonization and those skills are not already installed.
- ▌ Setup Environment · nvidia-omniverseUse when setting up a fresh clone of this repo to run OVRTX Dev Variant Presenter (also called the "variant studio" in the walkthrough video and earlier releases) — no .venv yet, ovrtx/ovstage/ovstream not installed, ModuleNotFoundError on ovrtx/ovstage/ovstream, or "how do I install / get this running". RTX + uv; validated on Windows.
- ▌ Renderer Shader Host Layout Sync · nvidia-omniverse bundleKeep host C/C++ structs and the shaders that read them byte-for-byte in sync — SSBO/UBO/push-constant layout, binding indices, and shared constants across GLSL/MSL/SPIR-V. Use when Codex adds or changes a struct shared between host code and a shader, wires descriptor/binding layouts, shares a push-constant block across pipelines, or debugs "wrong pixels with no crash" layout-drift bugs.
- ▌ Usda Layer Open · nvidia-omniverseUse this skill when implementing or verifying the USDA text-layer format handler used by layer opening.
- ▌ Usdc Layer Open · nvidia-omniverseUse this skill when implementing or verifying the concrete USDC layer-format handler used by generic layer opening.
- ▌ Usdz Layer Open · nvidia-omniverseUse this skill when implementing or verifying opening a single layer from a USDZ package.
- ▌ Blender Content Safety And Privacy · nvidia-omniverse bundleSafely inspect, open, import, modify, and share externally supplied Blender, USD, texture, archive, and reference content. Use before handling content of unknown or third-party origin, downloading dependencies, or publishing scene evidence.
- ▌ Render Product Device Pinning · nvidia-omniverseRestricting RenderProducts to specific CUDA-visible device indices with the USD deviceIds attribute. Use when a scene, test, or example must constrain a RenderProduct to CUDA-visible GPU 0 or another explicit set of CUDA-visible GPUs, especially for multi-GPU CI or viewport picking.
- ▌ Ovrtx Timeline Nle · nvidia-omniverseBuild a multi-track, non-linear timeline (NLE) for USD variant + camera changes over time: a pure state-resolution engine (tracks/clips, state_at(t), frame sampling, mixer/slideshow presets), a client-side JS mirror for instant scrubbing, and a render-to-MP4 path on an ovrtx renderer. Use when adding a timeline/sequencer to a variant presenter.
- ▌ Nanousd Renderer Scene Extraction · nvidia-omniverse bundleLoad USD scenes through NanoUSD and convert composed USD prims into renderer-ready geometry, material, light, camera, transform, instancing, texture, and diagnostic representations. Use when implementing, debugging, or validating NanoUSD-based scene ingestion, renderer scene structs, material/light extraction, texture path resolution, or loader parity against USD/OpenUSD semantics.
- ▌ Renderer Image Comparison Testing · nvidia-omniverse bundleDesign, implement, and run golden-image renderer comparison harnesses for graphics and viewer projects. Use when Codex needs to capture renderer output, compare Vulkan/OpenGL/Metal or other backends against golden images, refresh baselines, choose image-difference thresholds, wire tests into CI/CTest, handle display/GPU constraints, inspect visual diffs, or report residual risk for renderer correctness.
- ▌ Renderer Performance Architecture · nvidia-omniverse bundleDesign, review, or refactor high-performance renderer architecture for large USD scenes. Use when Codex needs to reason about target-quality/SOTA renderer architecture, instancing, batching, draw calls, frame-time budgets, geometry streaming, GPU buffer residency, texture/material upload, acceleration structures, shadows, forward/deferred render paths, readback, telemetry, performance validation, or replacing dead-end renderer paths.
- ▌ Usda Spec Parser · nvidia-omniverseUse this skill when implementing or verifying the USDA single-layer parser.
- ▌ Usdc Spec Parser · nvidia-omniverseUse this skill when implementing or verifying mapping from USDC Crate sections into the shared USD document model.
- ▌ Getting Started · nvidia-omniverseBootstrap a project using the OpenUSD Exchange SDK (install via wheel or install_usdex; project layout; smoke test). Do NOT use for authoring.
- ▌ Usd Authoring · nvidia-omniverse bundleAuthor USD content via OpenUSD Exchange helpers (usdex.core, usdex.rtx, usdex.test). Use when writing or converting USD; do NOT use for install tasks.