isaac-sim-validator

Validates Isaac Sim scripts, renders, USD scenes, and RL training outputs before delivery.

4.0k|530|Updated May 28, 2025
One-click install
npx skills add https://github.com/isaac-sim/IsaacSim --skill isaac-sim-validator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: isaac-sim-validator
Source: https://github.com/isaac-sim/IsaacSim/tree/main/skills/isaac-sim-validator
Command: npx skills add https://github.com/isaac-sim/IsaacSim --skill isaac-sim-validator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Isaac Sim outputs often fail silently: black renders from missing lights, deprecated omni.isaac.* imports, hardcoded user paths, undersized SimulationApp configs, and malformed RL checkpoints. This Skill acts as a final quality gate that rejects defective simulation scripts, renders, USD scenes, and training artifacts before they reach the user.

Core Features & Use Cases

  • Script and structure validation: Checks isaacsim.* namespace usage, SimulationApp window arguments, lighting setup, render mode, and configurable output directories, with a three-level bash validator (syntax, structure, runtime).
  • Render frame analysis: Rejects black or low-energy frames using file size, mean RGB, pixel variance, and histogram checks.
  • RL training validation: Enforces AppLauncher ordering, isaaclab.* imports, checkpoint naming (model_XXXX.zip), and multi-seed runs.
  • Use Case: A sub-agent produces a warehouse render and training script; run the validator to catch a missing DomeLight, a hardcoded /home/user path, and a wrong checkpoint name before delivery.

Quick Start

Validate this Isaac Sim script and its rendered output before I deliver it to the user.

Frequently Asked Questions about isaac-sim-validator

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

FAQPage Schema
How do I validate an Isaac Sim script before running it?

Run validate_sim.sh with a level flag: --level 1 checks Python syntax and SimulationApp usage, --level 2 checks headless mode and import ordering, and --level 3 executes the script with a timeout and inspects the output directory for non-empty files.

Why is my Isaac Sim render black or empty?

Black renders usually come from missing lights or MDL-only shaders. The validator requires a DomeLight with intensity at least 100 and a DistantLight at least 500, and rejects frames under 150 KB or with mean RGB below 30.

Is omni.isaac.core still supported in Isaac Sim scripts?

No, omni.isaac.core and omni.isaac.lab are deprecated. Scripts must use the isaacsim.* and isaaclab.* namespaces, and the validator rejects any output using the old import paths.

What checkpoint format should Isaac Lab RL training produce?

Accepted outputs are model_XXXX.zip or policy_only_XXXX.pt, plus log.csv, a wandb URL, or results.json with episode data. A bare policy.pt name is rejected, and reward curves such as episode/reward_mean must be logged.

When should I use PathTracing instead of RayTracedLighting?

Use RayTracedLighting for iteration because PathTracing is too slow during development. Reserve PathTracing for final hero shots only; the validator rejects PathTracing in iterative workflows.