interpret-validators

Convert saved USD validator artifacts into tier-classified failure reports.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill converts saved validator outputs (CSV/JSON artifacts) into a clear, tier-classified report so you can quickly understand what failed and what to do next.

Core Features & Use Cases

  • Structured failure reporting: Produces a header, per-rule severity summary (including affected prims), and expanded failure details without re-running validation.
  • Base + Scene Optimizer coverage: Classifies issues across base omni.asset_validator rules and Scene Optimizer checker rules, and shows a unified family breakdown.
  • Tier-aware fix guidance: Adds fix tier and backing operation for Scene Optimizer rules when mapped, and falls back to CSV suggestions for unknown/manual cases.
  • Missing-artifact resilience: Supports replay with sibling issues.csv when available, and performs findings-driven partial-report derivation when only summary.json is present.

Quick Start

Use the interpret-validators skill on a saved validation summary by running it with the path to your summary.json file, and then ask which prims are affected by a specific failing RuleName.

Frequently Asked Questions about interpret-validators

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

FAQPage Schema
How do I interpret USD validator artifacts without re-running validation?

To interpret USD validator artifacts without re-running validation, use this Skill to parse saved summary.json files and generate an actionable, tier-classified report with per-rule prim lists and fix recommendations.

What is the best way to generate a triage report from a USD issues.csv file?

Generating a triage report from a USD issues.csv file involves applying CSV-backed summarization to align rule, severity, and failure groups into a consistent schema, producing structured failure details with affected prims.

Does this reporting tool work if my validation summary.json is missing an issues.csv file?

Yes, the reporting tool supports missing-artifact resilience by performing findings-driven partial-report derivation when only summary.json is present, or replaying with sibling issues.csv when available.

How does tiered triage map Scene Optimizer rules to fix operations?

Tiered triage maps Scene Optimizer rules to fix operations by classifying issues across base and Scene Optimizer checker rules, adding fix tier and backing operation for mapped rules, and falling back to CSV suggestions for unknown cases.

Can I identify which specific prims are affected by a failing USD validation rule?

Yes, you can identify affected prims by running the Skill on your saved validation summary and querying which prims are impacted by a specific failing RuleName, yielding a structured per-rule severity summary.