run-validators

Run Scene Optimizer and asset-validator checks on USD assets, producing CSV, JSON, and log artifacts.

31|4|Updated May 21, 2026
One-click install
npx skills add https://github.com/NVIDIA-Omniverse/usd-optimize --skill run-validators
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: run-validators
Source: https://github.com/NVIDIA-Omniverse/usd-optimize/tree/main/.agents/skills/run-validators
Command: npx skills add https://github.com/NVIDIA-Omniverse/usd-optimize --skill run-validators

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Run Scene Optimizer and asset-validator performance checks on a USD asset and persist the results so you can interpret them later without re-running the whole validation.

Core Features & Use Cases

  • Comprehensive validator sweep: Executes Scene Optimizer SceneOptimizer* rules alongside the asset-validator base DefaultPlugin rules in a single run.
  • Deterministic artifact capture: Writes issues CSV, summary JSON, a full run log, and an asset path into a stable per-asset directory for downstream replay.
  • Runtime-aware fallback: Uses wrapper-driven driver execution when available, otherwise runs a standalone analysis-mode approximation for the Scene Optimizer rule family only (not the base rule family).
  • Use case: When you have a complex USD stage that’s failing your pipeline checks, run this skill to generate issues.csv and summary.json, then hand them to interpret-validators to pinpoint affected prims and remediation steps.

Quick Start

Run the validator on your USD by telling the agent: validate the file at /path/to/asset.usd and write the resulting artifacts for interpretation.

Frequently Asked Questions about run-validators

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

FAQPage Schema
How do I validate USD assets and save the validation results for later analysis?

To validate USD assets, run a comprehensive sweep of Scene Optimizer and asset-validator base rules on your .usd, .usda, .usdc, or .usdz files, which captures issues CSV, summary JSON, and a run log into a stable per-asset directory.

What USD file formats are supported for pipeline validation workflows?

Pipeline validation workflows support .usd, .usda, .usdc, and .usdz asset formats, executing Scene Optimizer and asset-validator base rules while persisting issues CSV and summary JSON artifacts.

Can I run Scene Optimizer validators if the asset-validator wrapper is unavailable?

If the wrapper is unavailable, a runtime-aware standalone analysis-mode fallback executes an approximation for the Scene Optimizer rule family only, skipping the asset-validator base rule family while still producing output artifacts.

How does artifact generation work for long-running USD validation jobs?

Artifact generation for long-running USD validation jobs captures issues CSV, summary JSON, and a full run log with progress logging into a stable per-asset directory, ensuring deterministic results for downstream replay without re-running validation.

Why do I need a fallback output schema compatible with interpret-validators?

A fallback output schema compatible with interpret-validators is required so that standalone analysis-mode artifacts can be parsed downstream to pinpoint affected USD prims and determine remediation steps.