Omniverse Cad To Simready
NVIDIAOfficialCreated by OmniverseDistributed by NVIDIA
- Skill
- Workflow
- Software development
- Apache-2.0
- Medium risk
- Has scripts
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
This skill acts as an orchestrator for the CAD to SimReady pipeline, coordinating a series of specialized stages including asset conversion, material and physics assignment via Content Agents, validation, and final packaging. It is designed to manage the flow between discrete tools rather than replacing them, ensuring that assets meet specific simulation requirements through a structured, documentation-driven process.
What it does
- Coordinates end-to-end conversion from source CAD or mesh assets to SimReady USD.
- Manages property assignment for materials and physics using Content Agents.
- Performs multi-stage validation gates to ensure asset viability and conformance.
- Automates the assembly of deliverable packages including thumbnails and USD dependencies.
- Provides consolidated reporting on workflow status, validation findings, and stage outputs.
- Supports flexible execution modes including conversion-only and validation-only paths.
When to use it
- When you need to transform raw CAD or source assets into simulation-ready USD files.
- When you require automated material and physics assignment for 3D assets.
- When you need to validate assets against SimReady conformance profiles.
- When you are preparing assets for packaging and distribution in a simulation environment.
Advantages
- Provides a structured, repeatable pipeline for complex asset preparation.
- Integrates multiple specialized stages into a cohesive workflow.
- Ensures consistent validation and conformance across the asset lifecycle.
- Supports modular execution by allowing specific stages to be skipped or isolated.
Usage examples
- “Convert my CAD file at /path/to/model.step to a SimReady asset.”
- The agent will initiate the preflight check, convert the file to USD, apply material and physics properties, validate the result, and output a report.
- “Validate this existing USD file for SimReady conformance.”
- The agent will run the validation-only workflow, checking the provided USD against SimReady profiles and reporting any findings.
Install
Download the skill as a ZIP:
https://mp-staging.autogineer.com/agent-skills/nvidia/omniverse-cad-to-simready/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip omniverse-cad-to-simready.zip -d .agents/skills
Documentation by Omniverse
CAD to SimReady
When to Use
Use this workflow skill for an end-to-end pipeline from a source asset to a SimReady asset or package. It coordinates existing conversion, authoring, validation, conformance, rendering, and packaging references directly; do not replace it with a single monolithic runner command.
This skill is documentation-driven and does not ship scripts/run.py; it must
not depend on a repository checkout. Shell is declared because this workflow
invokes installed stage reference scripts directly, from each reference's
installed directory, and it still must not grow a monolithic runner.
Prerequisites
Prefer
preflightfirst for deterministic setup: it installs/verifies local upstream checkouts, writes acad-to-simready-preflight.jsonmanifest, and exportsPHYSICAL_AI_PREFLIGHT_MANIFESTplusPHYSICAL_AI_REQUIRE_PREFLIGHT=1for downstream references.Python 3.12 and
uv(per repoREADME.md).A Content Agents model provider key when local deployment will run, or explicit endpoint variables plus usage tokens for already-running endpoints; see
references/preflight/README.mdfor the full list.Docker, NVIDIA Container Toolkit, and an NVIDIA GPU for Content Agents and OVRTX stages.
Local upstream checkouts under
${OMNIVERSE_CAD_TO_SIMREADY_UPSTREAM_ROOT:-$HOME/.omniverse-cad-to-simready/upstreams}when a stage needs upstream scripts or specs.
First Action
For any broad CAD/source-asset to SimReady request, assume
property_assignment_intent=run unless the user explicitly asks for
conversion-only, validation-only, or no material/physics assignment.
For conversion-only requests, set property_assignment_intent=skip, do not
deploy Content Agents, run convert-to-usd, then run validate-usd-minimum
on the generated USD if conversion succeeds. For validation-only requests,
set property_assignment_intent=skip and validate the USD the user
provided without rerunning conversion.
Run preflight (or verify an existing PHYSICAL_AI_PREFLIGHT_MANIFEST)
before any converter, validation, Content Agents, OVRTX, packaging, or FET
step; treat it as dependency bootstrap, not workflow routing. Use
--skip-content-agents for conversion-only/validation-only requests.
When property_assignment_intent=run, verify or deploy Content Agents
services immediately after confirming the source path and resolving intent,
before asset-context inspection, converter dependency checks, conversion,
validation, conformance, rendering, packaging, or upstream source builds.
Treat explicitly provided healthy endpoints as user-owned; otherwise run deploy-content-agents,
which deploys the shared standalone OVRTX renderer, then Material, Physics,
and optional Texture service containers in order.
Instructions
Confirm the source asset path exists, resolve
output_root, and classify the request as end-to-end, conversion-only, validation-only, or packaging.Resolve
property_assignment_intentbefore running any asset inspection, converter probe, conversion, validation, conformance, rendering, or packaging step.Run
preflightfor the selected workflow targets, unless a readyPHYSICAL_AI_PREFLIGHT_MANIFESTis already configured. Source the generated env file before running downstream scripts. Treat preflight as dependency setup only: it may use a provided--source-asset,--source-format, or--conversion-toolsvalue to scope dependency checks, butconvert-to-usdand the upstream converter references still decide actual conversion support.Verify or deploy Content Agents services first when
property_assignment_intent=run; block on missing authentication or unhealthy services instead of continuing.Read
references/workflow.mdandreferences/commands.md, then run only the stage references needed for the current request.Run
identify-asset-contexton the original source asset when web search is available or property assignment will run.Route the source through
convert-to-usd, or skip conversion for existing USD input and treat the source path as the current USD path.Run
validate-usd-minimumbefore expensive downstream work. Treat this as a viability gate only: record unit/profile issues such asmetersPerUnit != 1.0, but do not runsimready-conform-profile, FET001, or any other FET repair before Content Agents assignment when property assignment will run.Run Content Agents material, physics, and optional texture assignment on the converted/minimum-valid USD when requested or required.
Run
simready-conform-profileon the latest simulation USD path after property assignment and preserve every selected FET repair report.Run validation gates in order:
omni-asset-validate,omni-asset-validate-geometry,omni-asset-validate-physics, andsimready-validate.Rerun
simready-conform-profilewhensimready-validatereports a repairable requirement, then rerun profile validation on the newest authored USD.Run
ovrtx-render-servicewhen preview, thumbnail, or inspection images are requested. When package outputs are requested, runassemble-package-sourcenext to create the cleandeliverable/package source from the final USD and thumbnail, then runnv-core-package-sampleandnv-core-package-sample-validationon that deliverable folder only.Emit the consolidated workflow report with the final USD path, all stage reports, validation findings, rerun reasons, and next work.
Output Format
Emit a consolidated workflow report in Markdown, and include JSON when the
workflow writes structured artifacts. Report overall status as passed,
blocked, failed, or needs_rerun. See references/workflow.md for the
required Markdown and JSON report fields.
Detailed References
Read only the references needed for the current request:
references/preflight/README.md: deterministic local setup, manifest/env contract, wrappers, deployment opt-out, and guardrail behavior.references/workflow.md: inputs, source routing, detailed workflow, validation policy, output report fields, and next steps.references/commands.md: concrete portable script command patterns.references/assemble-package-source/README.md: two-zone package source assembly, root USD naming, thumbnail placement, and deliverable checks.references/troubleshooting.md: symptom/cause/fix table plus FET (GSP.001/RB.MB.001) repair-routing detail.references/publishing-layout.md: frontmatter compatibility-field notes and layout rationale for this skill's own file tree.
Publishing Layout Notes
Use skills/omniverse-cad-to-simready/ as the source of truth for this
product repo's skill. The .agents/skills symlink is a compatibility alias
for local agentskills.io-style discovery, and the nested references/ tree
is intentional. See references/publishing-layout.md for the alias list,
frontmatter field placement, and flattening rules.
Limitations
This workflow coordinates existing conversion, property assignment, conformance, validation, rendering, and packaging skills; it does not replace them with a single monolithic runner command.
Troubleshooting
Read references/troubleshooting.md only when a specific stage or validation
gate is failing; it owns the symptom/cause/fix table and FET repair routing.
Hard Rules
Prefer the preflight manifest for local upstream roots, converter executables, SimReady validation runtime, OVRTX endpoint, and Content Agents service URLs. When
PHYSICAL_AI_REQUIRE_PREFLIGHT=1is set, do not bypass the manifest with direct upstream discovery.Do not run asset inspection, converter probes, local upstream builds, conversion, validation, conformance, rendering, or packaging before Content Agents readiness when property assignment will run.
Use stage-specific installed reference scripts directly. Do not add or call a single
omniverse-cad-to-simreadyrunner command.For source conversion, delegate to the
convert-to-usdreference; do not substitute another converter for CAD or mesh formats.For property assignment, use Content Agents references as separate atomic steps: material first, then physics, then texture only when requested.
When property assignment will run, do not run
simready-conform-profileor any FET helper before Content Agents. Validate minimum USD first, then run Content Agents on that converted/minimum-valid USD, then apply FET repairs to the latest service-authored USD.When property assignment will run, do not run
simready-validateor any SimReady profile validation before Content Agents. The only validation gate allowed before service calls isvalidate-usd-minimum, which is a basic USD viability check.Stop at the first failing deployment, conversion, property-assignment, or conformance authoring gate unless the user explicitly asks for best-effort continuation.
Do not stop at validation findings after a meaningful USD artifact exists. Continue remaining diagnostic gates and mark the result
needs_rerun.Do not leave a
GSP.001profile failure as an unclassified final finding. Route it to upstreamsimready-foundation-conform-fet-005-simulate-grasp-physics; if the current agent cannot inspect renders or no explicit grasp points are available, report a blocked FET005 repair with the visual evidence path or missing input reason.Preserve every stage report and pass the concrete output USD path from each report into the next stage.
Files
- ATTRIBUTION.mdAdded by AutoGineer936 B
- BENCHMARK.md5.4 KiB
- CHANGELOG.md2.0 KiB
- LICENSELicence file added by AutoGineer11.2 KiB
- SKILL.md10.7 KiB
- agents/openai.yaml427 B
- config/skillspector-baseline.yaml1.6 KiB
- evals/evals.json8.9 KiB
- evals/files/minimal_mesh.stl157 B
- references/assemble-package-source/README.md3.9 KiB
- references/assemble-package-source/scripts/check_dependencies.pyScript2.3 KiB
- references/assemble-package-source/scripts/report_schema.json1.2 KiB
- references/assemble-package-source/scripts/run.pyScript19.2 KiB
- references/commands.md5.3 KiB
- references/content-agents/README.md20.2 KiB
- references/content-agents/references/material-agent-client/README.md13.8 KiB
- references/content-agents/references/material-agent-client/scripts/check_dependencies.pyScript417 B
- references/content-agents/references/material-agent-client/scripts/report_schema.json722 B
- references/content-agents/references/material-agent-client/scripts/run.pyScript405 B
- references/content-agents/references/physics-agent-client/README.md13.7 KiB
- references/content-agents/references/physics-agent-client/scripts/check_dependencies.pyScript417 B
- references/content-agents/references/physics-agent-client/scripts/report_schema.json722 B
- references/content-agents/references/physics-agent-client/scripts/run.pyScript405 B
- references/content-agents/references/texture-agent-client/README.md6.7 KiB
- references/content-agents/references/texture-agent-client/scripts/check_dependencies.pyScript417 B
- references/content-agents/references/texture-agent-client/scripts/report_schema.json722 B
- references/content-agents/references/texture-agent-client/scripts/run.pyScript405 B
- references/content-agents/scripts/check_dependencies.pyScript1.3 KiB
- references/content-agents/scripts/content_agent_check_dependencies.pyScript4.6 KiB
- references/content-agents/scripts/content_agent_client.pyScript76.1 KiB
- references/content-agents/scripts/content_agent_material_cleanup.pyScript10.7 KiB
- references/content-agents/scripts/content_agent_report_schema.json722 B
- references/content-agents/scripts/openusd_upload_prep.pyScript12.8 KiB
- references/content-agents/scripts/report_schema.json961 B
- references/content-agents/scripts/run.pyScript9.6 KiB
- references/convert-to-usd/README.md10.1 KiB
- references/convert-to-usd/references/mujoco-usd-converter/README.md4.1 KiB
- references/convert-to-usd/references/mujoco-usd-converter/scripts/check_dependencies.pyScript1.5 KiB
- references/convert-to-usd/references/mujoco-usd-converter/scripts/report_schema.json405 B
- references/convert-to-usd/references/mujoco-usd-converter/scripts/run.pyScript9.3 KiB
- references/convert-to-usd/references/openusd-exchange-sdk-usdex/README.md4.7 KiB
- references/convert-to-usd/references/urdf-usd-converter/README.md3.8 KiB
- references/convert-to-usd/references/urdf-usd-converter/scripts/check_dependencies.pyScript1.5 KiB
- references/convert-to-usd/references/urdf-usd-converter/scripts/report_schema.json403 B
- references/convert-to-usd/references/urdf-usd-converter/scripts/run.pyScript9.4 KiB
- references/convert-to-usd/references/usd-convert-cad/README.md8.0 KiB
- references/convert-to-usd/references/usd-convert-cad/scripts/check_dependencies.pyScript3.6 KiB
- references/convert-to-usd/references/usd-convert-cad/scripts/report_schema.json476 B
- references/convert-to-usd/references/usd-convert-cad/scripts/run.pyScript22.8 KiB
- references/convert-to-usd/references/usd-convert-gsplat/README.md4.4 KiB
- references/convert-to-usd/references/usd-convert-gsplat/scripts/check_dependencies.pyScript2.1 KiB
- references/convert-to-usd/references/usd-convert-gsplat/scripts/report_schema.json413 B
- references/convert-to-usd/references/usd-convert-gsplat/scripts/run.pyScript13.6 KiB
- references/convert-to-usd/scripts/check_dependencies.pyScript1.7 KiB
- references/convert-to-usd/scripts/report_schema.json1.4 KiB
- references/convert-to-usd/scripts/run.pyScript22.6 KiB
- references/deploy-content-agents/README.md10.7 KiB
- references/deploy-content-agents/references/deploy-material-agent-docker.md423 B
- references/deploy-content-agents/references/deploy-ovrtx-docker.md405 B
- references/deploy-content-agents/references/deploy-physics-agent-docker.md421 B
- references/deploy-content-agents/references/deploy-texture-agent-docker.md421 B
- references/identify-asset-context/README.md4.7 KiB
- references/identify-asset-context/scripts/check_dependencies.pyScript1.5 KiB
- references/identify-asset-context/scripts/report_schema.json751 B
- references/identify-asset-context/scripts/run.pyScript11.1 KiB
- references/nv-core-package-sample-validation/README.md5.3 KiB
- references/nv-core-package-sample-validation/scripts/check_dependencies.pyScript419 B
- references/nv-core-package-sample-validation/scripts/report_schema.json702 B
- references/nv-core-package-sample-validation/scripts/run.pyScript400 B
- references/nv-core-package-sample/README.md6.3 KiB
- references/nv-core-package-sample/scripts/check_dependencies.pyScript419 B
- references/nv-core-package-sample/scripts/report_schema.json702 B
- references/nv-core-package-sample/scripts/run.pyScript400 B
- references/omni-asset-validate-geometry/README.md3.5 KiB
- references/omni-asset-validate-geometry/scripts/check_dependencies.pyScript1.9 KiB
- references/omni-asset-validate-geometry/scripts/report_schema.json363 B
- references/omni-asset-validate-geometry/scripts/run.pyScript2.0 KiB
- references/omni-asset-validate-physics/README.md3.4 KiB
- references/omni-asset-validate-physics/scripts/check_dependencies.pyScript1.9 KiB
- references/omni-asset-validate-physics/scripts/report_schema.json362 B
- references/omni-asset-validate-physics/scripts/run.pyScript2.0 KiB
- references/omni-asset-validate/README.md3.5 KiB
- references/omni-asset-validate/scripts/check_dependencies.pyScript2.4 KiB
- references/omni-asset-validate/scripts/report_schema.json359 B
- references/omni-asset-validate/scripts/run.pyScript13.8 KiB
- references/ovrtx-render-service/README.md14.5 KiB
- references/ovrtx-render-service/scripts/check_dependencies.pyScript3.4 KiB
- references/ovrtx-render-service/scripts/report_schema.json674 B
- references/ovrtx-render-service/scripts/run.pyScript24.3 KiB
- references/ovrtx-render-service/scripts/stage_prep.pyScript19.2 KiB
- references/ovrtx-render-service/scripts/turntable.pyScript10.8 KiB
- references/preflight/README.md15.5 KiB
- references/preflight/scripts/preflight.ps1Script460 B
- references/preflight/scripts/preflight.pyScript114.8 KiB
- references/preflight/scripts/preflight.shScript278 B
- references/publishing-layout.md1.5 KiB
- references/simready-conform-profile/README.md13.9 KiB
- references/simready-conform-profile/references/FET_000_CORE/README.md1.3 KiB
- references/simready-conform-profile/references/FET_000_CORE/scripts/check_dependencies.pyScript1.4 KiB
- references/simready-conform-profile/references/FET_000_CORE/scripts/report_schema.json418 B
- references/simready-conform-profile/references/FET_000_CORE/scripts/run.py11.6 KiB
- references/simready-conform-profile/references/FET_001_MINIMAL/README.md1.5 KiB
- references/simready-conform-profile/references/FET_001_MINIMAL/scripts/check_dependencies.py1.9 KiB
- references/simready-conform-profile/references/FET_001_MINIMAL/scripts/report_schema.json668 B
- references/simready-conform-profile/references/FET_001_MINIMAL/scripts/run.py16.3 KiB
- references/simready-conform-profile/references/FET_004_SIMULATE_MULTI_BODY_PHYSICS/README.md1.4 KiB
- references/simready-conform-profile/references/FET_004_SIMULATE_MULTI_BODY_PHYSICS/scripts/check_dependencies.py1.6 KiB
- references/simready-conform-profile/references/FET_004_SIMULATE_MULTI_BODY_PHYSICS/scripts/report_schema.json1.0 KiB
- references/simready-conform-profile/references/FET_004_SIMULATE_MULTI_BODY_PHYSICS/scripts/run.py13.3 KiB
- references/simready-conform-profile/references/FET_005_SIMULATE_GRASP_PHYSICS/README.md1.9 KiB
- references/simready-conform-profile/references/FET_005_SIMULATE_GRASP_PHYSICS/scripts/author_grasp_line.py11.2 KiB
- references/simready-conform-profile/scripts/check_dependencies.py2.3 KiB
- references/simready-conform-profile/scripts/report_schema.json466 B
- references/simready-conform-profile/scripts/run.py20.1 KiB
- references/simready-validate/README.md9.1 KiB
- references/simready-validate/scripts/check_dependencies.py4.2 KiB
- references/simready-validate/scripts/report_schema.json480 B
- references/simready-validate/scripts/run.py26.9 KiB
- references/troubleshooting.md5.0 KiB
- references/validate-usd-minimum/README.md2.5 KiB
- references/validate-usd-minimum/scripts/check_dependencies.py2.1 KiB
- references/validate-usd-minimum/scripts/report_schema.json1.3 KiB
- references/validate-usd-minimum/scripts/run.py11.9 KiB
- references/workflow.md17.2 KiB
- shared/preflight_manifest.py9.7 KiB
- shared/script_utils.py13.5 KiB
- shared/simready_package.py34.3 KiB
- shared/simready_package_check_dependencies.py2.1 KiB
- shared/simready_package_report_schema.json702 B
- shared/upstream_versions.py2.4 KiB
- skill-card.md4.7 KiB
- skill.oms.sig39.4 KiB
- upstream-versions.lock.json2.2 KiB
references/simready-conform-profile/README.md
SimReady Conform Profile
When to Use
Use this router reference after USD conversion and property assignment, before
simready-validate. It chooses the SimReady feature-level conformance skill
that should repair a failing profile requirement.
This reference ships a narrow scripts/run.py router for deterministic
workflow handoff and report generation. It should not be treated as the source of
truth for canonical FET instructions. The source of truth is the SimReady
Foundation repository:
https://github.com/NVIDIA/simready-foundation/tree/v2026.04.1Do not copy upstream FET skill instructions, requirement summaries, validators,
or repair policy into this repo. If browser or raw-file access is unavailable,
use a local checkout and read the upstream SKILL.md file directly.
Prerequisites
Python 3.12 and
uv(per repoREADME.md).A required
.usd,.usda,.usdc, or.usdzasset after conversion and property assignment.OpenUSD Python APIs (
pxr.Usd,pxr.UsdGeom) for local helper scripts when they are used.A SimReady Foundation checkout at
${SIMREADY_FOUNDATION_ROOT:-$OMNIVERSE_CAD_TO_SIMREADY_UPSTREAM_ROOT/simready-foundation}or$HOME/.omniverse-cad-to-simready/upstreams/simready-foundation, checked out to the exact ref inupstream-versions.lock.json(currentlyv2026.04.1).
Scope
This reference owns only Omniverse CAD-to-SimReady routing, report handoff, and local helper selection. Upstream SimReady Foundation owns feature-level conformance behavior.
Upstream Skills
Resolve upstream skill files from:
$SIMREADY_FOUNDATION_ROOT/skills/<skill-name>/SKILL.mdUse this mapping when routing validation failures:
| Requirement area | Upstream Foundation skill |
|---|---|
| Core metadata, sidecar JSON, asset naming, and package layout failures | simready-foundation-conform-fet-000-core |
| Minimal/base-neutral USD feature failures | simready-foundation-conform-fet-001-minimal |
| Rigid-body physics failures | simready-foundation-conform-fet-003-rigid-body-physics |
| Multibody physics failures | simready-foundation-conform-fet-004-simulate-multi-body-physics |
Prop grasp vector failures for GSP.001 | simready-foundation-conform-fet-005-simulate-grasp-physics |
| Material failures | simready-foundation-conform-fet-006-materials |
| Nonvisual material failures | simready-foundation-conform-fet-007-nonvisual-materials |
| Robot core profile failures | simready-foundation-conform-fet-021-robot-core |
| Robot material failures | simready-foundation-conform-fet-023-robot-materials |
| Base articulation failures | simready-foundation-conform-fet-024-base-articulation |
The matching branch URLs are:
https://github.com/NVIDIA/simready-foundation/blob/v2026.04.1/skills/simready-foundation-conform-fet-000-core/SKILL.md
https://github.com/NVIDIA/simready-foundation/blob/v2026.04.1/skills/simready-foundation-conform-fet-001-minimal/SKILL.md
https://github.com/NVIDIA/simready-foundation/blob/v2026.04.1/skills/simready-foundation-conform-fet-003-rigid-body-physics/SKILL.md
https://github.com/NVIDIA/simready-foundation/blob/v2026.04.1/skills/simready-foundation-conform-fet-004-simulate-multi-body-physics/SKILL.md
https://github.com/NVIDIA/simready-foundation/blob/v2026.04.1/skills/simready-foundation-conform-fet-005-simulate-grasp-physics/SKILL.md
https://github.com/NVIDIA/simready-foundation/blob/v2026.04.1/skills/simready-foundation-conform-fet-006-materials/SKILL.md
https://github.com/NVIDIA/simready-foundation/blob/v2026.04.1/skills/simready-foundation-conform-fet-007-nonvisual-materials/SKILL.md
https://github.com/NVIDIA/simready-foundation/blob/v2026.04.1/skills/simready-foundation-conform-fet-021-robot-core/SKILL.md
https://github.com/NVIDIA/simready-foundation/blob/v2026.04.1/skills/simready-foundation-conform-fet-023-robot-materials/SKILL.md
https://github.com/NVIDIA/simready-foundation/blob/v2026.04.1/skills/simready-foundation-conform-fet-024-base-articulation/SKILL.mdLocal Helper Policy
Some legacy reference-local scripts remain only as narrow report-producing helpers for the Omniverse CAD-to-SimReady workflow. They are not the FET skill source of truth. Before running one, read the matching upstream Foundation skill and make sure the helper still matches the selected profile requirement.
Do not add new copied FET docs to this repo. If a needed repair is fully covered by an upstream Foundation script, run the upstream script from the Foundation checkout instead of adding another local implementation here.
Inputs
Collect:
| Input | Requirement |
|---|---|
usd_asset | Required .usd, .usda, .usdc, or .usdz asset after conversion and property assignment. |
output_root | Required or inferred directory for conformance outputs and reports. |
simready_profile | Selected SimReady profile. Default to Prop-Robotics-Neutral for generic props unless the user names another profile. |
profile_version | Selected profile version. Default to 1.0.0 unless the user names another version. |
validation_report | Preferred JSON report from simready-validate, used to identify failing feature and requirement IDs. |
source_asset | Optional provenance path for metadata. |
grasp_target_prim | Optional prim path for grasp-vector placement. |
grasp_points | Optional explicit grasp vector points. |
For .usdz, Core metadata repair may be sidecar-only, but feature repairs that
must author USD prims cannot rewrite a sealed package. Report that limitation
and ask for or produce an unpacked USD-family asset when prim-level repair is
required.
Profile Policy
Default behavior for current profiles:
| Profile family | Conformance routing |
|---|---|
Prop-Robotics-* | Route Core failures to simready-foundation-conform-fet-000-core; route GSP.001 or FET005 failures to simready-foundation-conform-fet-005-simulate-grasp-physics; route material and physics failures to their matching upstream FET skills. |
Robot-Body-* | Route Core failures to simready-foundation-conform-fet-000-core; route robot schema, robot material, articulation, and physics failures to the matching upstream robot or physics FET skills. Do not add prop grasp vectors unless the user explicitly asks or validation identifies a matching requirement. |
| Unknown or custom profile | Run profile validation or inspect the failing feature IDs before choosing upstream FET skills. |
Prefer explicit user intent over defaults. Do not guess destructive edits or overwrite source files.
Instructions
Confirm the USD asset exists.
Select the profile and profile version.
Read the relevant upstream Foundation skill before authoring any repair.
Route Core metadata, naming, and layout failures to
simready-foundation-conform-fet-000-core.Inspect the latest staged USD metadata before final profile validation. If
metersPerUnitis present but not1.0, or validation reportsUN.007, route tosimready-foundation-conform-fet-001-minimalbefore later feature repairs.Route the next failing feature to the matching upstream FET skill. For
GSP.001, usesimready-foundation-conform-fet-005-simulate-grasp-physicsbecause it owns the visual/semantic grasp decision. ForRB.MB.001orFET004_BASE_*, usesimready-foundation-conform-fet-004-simulate-multi-body-physics; count actualUsdPhysics.RigidBodyAPIprims and inspect existing component colliders or part roots. If there are at least two reusable candidates, run the FET004 flow instead of marking the profile gate not applicable. If there is only one mesh component or oneGeomSubsetcomponent, letsimready-validatereportRB.MB.001as a non-blocking ignored issue.Preserve every JSON report and summarize each authoring step as pass, fail, skipped, or blocked.
Stop at the first failed authoring step unless the user asks for best-effort continuation.
Hand off the latest authored USD path to
simready-validate.
Command Patterns
Resolve the Foundation checkout before following any FET skill:
export OMNIVERSE_CAD_TO_SIMREADY_UPSTREAM_ROOT="${OMNIVERSE_CAD_TO_SIMREADY_UPSTREAM_ROOT:-$HOME/.omniverse-cad-to-simready/upstreams}"
export SIMREADY_FOUNDATION_ROOT="${SIMREADY_FOUNDATION_ROOT:-$OMNIVERSE_CAD_TO_SIMREADY_UPSTREAM_ROOT/simready-foundation}"
git -C "$SIMREADY_FOUNDATION_ROOT" checkout mainRead the upstream skill selected by this router:
sed -n '1,220p' "$SIMREADY_FOUNDATION_ROOT/skills/simready-foundation-conform-fet-005-simulate-grasp-physics/SKILL.md"Run the local router when you already have a validation report, or before final validation to apply deterministic Core and unit repairs:
python3 /path/to/skills/omniverse-cad-to-simready/references/simready-conform-profile/scripts/run.py \
/path/to/output_dir/physics/output_physics.usd \
--output-dir /path/to/output_dir/conform/profile \
--validation-report /path/to/output_dir/validation/simready-profile.json \
--profile Prop-Robotics-Neutral \
--profile-version 1.0.0 \
--source-asset /path/to/source.step \
--pipeline-step usd-convert-cad \
--pipeline-step material-agent-client \
--pipeline-step physics-agent-client \
--report /path/to/output_dir/conform/profile/simready-conform-profile.jsonFor GSP.001, pass at least two explicit --grasp-point x,y,z values selected
from visual evidence. Without explicit points, the router records FET005 as
blocked instead of authoring a placeholder grasp line.
Run upstream scripts from the Foundation checkout when the upstream skill provides them. For example, after visual review has selected explicit grasp points:
uv run --python 3.12 python "$SIMREADY_FOUNDATION_ROOT/skills/simready-foundation-conform-fet-005-simulate-grasp-physics/scripts/author_grasp_line.py" \
/path/to/output_dir/conform/metadata/asset.usda \
--output /path/to/output_dir/conform/grasp/asset.usda \
--name grasp_identifier_01 \
--point=-0.05,0.0,0.0 \
--point=0.05,0.0,0.0 \
--rationale "vision-reviewed graspable region" \
--report /path/to/output_dir/conform/grasp/author-grasp-line.jsonThen validate:
python3 /path/to/skills/omniverse-cad-to-simready/references/simready-validate/scripts/run.py /path/to/output_dir/conform/grasp/asset.usda \
--profile Prop-Robotics-Neutral \
--profile-version 1.0.0 \
--foundation-root "$SIMREADY_FOUNDATION_ROOT" \
--report /path/to/output_dir/validation/simready-profile.jsonOutput Format
The workflow summary should include:
| Field | Meaning |
|---|---|
input_usd_path | USD path received by this workflow. |
output_usd_path | Latest authored USD path after conformance. |
simready_profile | Selected profile name. |
profile_version | Selected profile version. |
upstream_skill | Upstream Foundation skill name and URL used for each repair. |
steps | Ordered FET conformance step results. |
reports | Paths to each selected feature repair JSON report. |
passed | Whether all required conformance steps passed. |
next_step | Usually simready-validate. |
Limitations
This reference does not predict material, physics, or texture properties.
This reference does not perform final validation; run
simready-validateafter conformance authoring.For
.usdz, Core metadata repair may be sidecar-only, but feature repairs that must author USD prims cannot rewrite a sealed package.Do not guess destructive edits or overwrite source files.
Do not copy upstream SimReady Foundation FET skill docs into this repo.
Troubleshooting
| Symptom | Cause | Fix |
|---|---|---|
| Foundation skill file is missing | SIMREADY_FOUNDATION_ROOT points to the wrong checkout or revision | Check out https://github.com/NVIDIA/simready-foundation at the exact ref in upstream-versions.lock.json. |
Sealed .usdz cannot be repaired in place | Feature repairs that author USD prims cannot rewrite a sealed package | Produce or request an unpacked USD-family asset before running prim-level repair. Core metadata repair may still proceed sidecar-only. |
GSP.001 failure reported as final without classification | Vision-capable inspection or explicit grasp points were not available | Route to upstream simready-foundation-conform-fet-005-simulate-grasp-physics. If neither vision nor explicit points are available, report the FET005 step as blocked. |
RB.MB.001 failure reported after Physics Agent | The USD has fewer than two UsdPhysics.RigidBodyAPI prims, even if it has many visual or collider prims | Route to upstream simready-foundation-conform-fet-004-simulate-multi-body-physics when there are at least two existing component colliders or part roots that represent source parts. If the asset has only one mesh component or one GeomSubset component, simready-validate treats RB.MB.001 as non-blocking and preserves it under ignored_issues; do not invent geometry. |
Pass/Fail Policy
Fail when:
the input USD asset does not exist
the selected upstream Foundation skill cannot be found
the selected feature repair fails
a required conformance step cannot run because the asset format is unsupported
the output path would overwrite without explicit
--force
Skip when:
a profile family does not require a conformance action, such as prop grasp vectors on a robot body profile
the user explicitly asks to defer a feature repair such as grasp vectors or metadata
Warn when:
the Foundation checkout is not pinned to
mainprofile-specific requirements are unknown and only Core metadata repair was authored
a grasp placement needs visual evidence or user-approved explicit points
.usdzinput prevents in-package grasp vector authoring
Next Steps
After conformance authoring passes, run simready-validate with the selected
profile and the same Foundation checkout. If validation still fails, use the failed
requirement IDs to decide whether to rerun the upstream FET skill with better
parameters or add a new upstream SimReady Foundation skill.
Requirements and compatibility
Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta
“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.
Needs: Declares allowed tools, Needs Python
The author says: Orchestrator skill. Managed Content Agents deployment requires a configured model provider key matching the selected backend, such as NVIDIA_API_KEY, OPENAI_API_KEY, ANTHROPIC_API_KEY, GOOGLE_API_KEY, or GEMINI_API_KEY, Docker + NVIDIA Container Toolkit + GPU, Python 3.12, and an upstream checkout of nvidia-omniverse/content-agents at the ref pinned in upstream-versions.lock.json. Reused/provided endpoints may instead use explicit endpoint and usage-token environment variables. Linux/macOS only.
Security
What our scanner noticed· Medium risk
- Large base64-encoded blobs
- Instructions that use the network
- Downloads piped into a shell
- Scripts that your agent may run
This skill includes scripts that your agent may run. Read them before you use it.
A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.
Attribution and licence
- Created by
- Omniverse
- Publisher
- NVIDIA (Official)
- Distributed by
- NVIDIA
- Source
- NVIDIA/skills · skills/omniverse-cad-to-simready · commit fce3cca
- Licence
- Apache License 2.0 (redistribution allowed)
- LICENSE (added by AutoGineer from LICENSE-APACHE)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
AutoGineer is not affiliated with or endorsed by Omniverse or NVIDIA.
Related skills
Setup TS Deep Modules
Matt Pocock· Community
Configures dependency-cruiser to enforce deep module boundaries in TypeScript repositories.
Software developmentClaude CodeClaude appsOpenAI Codex+14 moreMITLow riskHas scriptsGitHub stars of the source repository317.5k
To Spec
Matt Pocock· Community
Synthesizes conversation context into a structured technical specification and publishes it to a project issue tracker.
Software developmentClaude CodeClaude appsOpenAI Codex+14 moreMITGitHub stars of the source repository317.5k
Improve Codebase Architecture
Matt Pocock· Community
A systematic process to identify, visualize, and refine architectural deepening opportunities in a codebase.
Software developmentClaude CodeClaude appsOpenAI Codex+14 moreMITGitHub stars of the source repository317.5k
Domain Modeling
Matt Pocock· Community
An expert assistant for defining project terminology, maintaining a glossary, and documenting architectural decisions.
Software developmentClaude CodeClaude appsOpenAI Codex+14 moreMITGitHub stars of the source repository317.5k
Codebase Design
Matt Pocock· Community
A shared vocabulary and set of principles for designing deep, testable, and maintainable software modules.
Software developmentClaude CodeClaude appsOpenAI Codex+14 moreMITGitHub stars of the source repository317.5k
Prototype
Matt Pocock· Community
Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.
Software developmentClaude CodeClaude appsOpenAI Codex+14 moreMITGitHub stars of the source repository317.5k
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download omniverse-cad-to-simready.zip