| name | omniverse-cad-to-simready |
| description | Coordinate the end-to-end CAD/source-asset to SimReady workflow. Use for broad requests such as CAD to SimReady, source asset to simulation-ready USD, or prop packaging that require conversion, material/physics assignment, SimReady conformance, validation, and optional package creation; deploy or verify Content Agents services first when property assignment is enabled; route single-stage work through nested references. |
| version | 0.2.0 |
| license | Apache-2.0 |
| tools | ["Read","Shell"] |
| compatibility | 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.
|
| metadata | {"author":"Omniverse","tags":["physical-ai","simready","workflow","cad","conversion"],"domain":"ai-ml","languages":["python"]} |
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
preflight first for deterministic setup: it installs/verifies
local upstream checkouts, writes a cad-to-simready-preflight.json
manifest, and exports PHYSICAL_AI_PREFLIGHT_MANIFEST plus
PHYSICAL_AI_REQUIRE_PREFLIGHT=1 for downstream references.
- Python 3.12 and
uv (per repo README.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.md for 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 ,
which deploys the shared standalone OVRTX renderer, then Material, Physics,
and optional Texture service containers in order.
