omniverse-cad-to-simready

What this skill does

# CAD to SimReady

## When to Use

Use this workflow skill when the user wants an end-to-end pipeline from a
source asset to a SimReady asset or package. This skill coordinates existing
conversion, authoring, validation, conformance, rendering, and packaging
references directly. Do not replace the workflow with a single monolithic
runner command.

This skill is documentation-driven and does not ship `scripts/run.py`. It
should not depend on a repository checkout. When a stage needs deterministic
execution, run the portable script from that stage reference's installed
directory. `Shell` is declared because this workflow invokes installed stage
reference scripts directly; it still must not grow a monolithic runner.

## Prerequisites

- Prefer running the `preflight` reference first for deterministic setup. It
  installs or 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`).
- NVIDIA_API_KEY from `https://build.nvidia.com` when local Content Agents
  deployment will run. Already-running endpoints may instead use explicit
  endpoint variables plus usage tokens such as `NGC_API_KEY`, `NVCF_API_KEY`,
  or `CONTENT_AGENTS_*_TOKEN`.
- Docker, NVIDIA Container Toolkit, and an NVIDIA GPU for Content Agents and
  OVRTX stages.
- Local upstream checkouts under
  `${PHYSICAL_AI_SKILL_HUB_UPSTREAM_ROOT:-$HOME/.physical-ai-skill-hub/upstreams}`
  when a downstream stage needs upstream scripts or specs.

## Minimum Viable Scope

Conversion-only is a valid workflow request. When the user asks only to convert
or smoke-test source asset conversion, 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.

Do not imply that `uv sync` installs every source converter runtime. URDF,
MuJoCo/MJCF, and the repo Python dependencies are handled by the project
environment, but NVIDIA-backed source conversion requires an installed and
validated `NVIDIA-Omniverse/usd-convert-cad` checkout. If that runtime is
missing or does not support the source, preserve the blocked conversion report
and its `install_hint` instead of attempting an unrequested local build or
substituting another converter.

## 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.

Before invoking converter, validation, Content Agents, OVRTX, packaging, or FET
helper scripts, run the `preflight` reference or verify an existing
`PHYSICAL_AI_PREFLIGHT_MANIFEST`. Treat preflight as the mandatory dependency
bootstrap step, not as workflow routing. If the user explicitly asks not to
deploy services or asks for conversion-only/validation-only, use
`--skip-content-agents`.
When `PHYSICAL_AI_REQUIRE_PREFLIGHT=1` is set and a required component is not
ready in the manifest, downstream references must block with the preflight
guardrail instead of rediscovering upstreams or services directly.

When `property_assignment_intent=run`, the first operational action after
confirming the source path and resolving intent is to verify or deploy Content
Agents services. Do this before asset-context inspection, converter dependency
checks, conversion, validation, conformance, rendering, packaging, or upstream
source builds.

Use healthy existing endpoints when available. If OVRTX, Material, or Physics
endpoints are missing or unhealthy, run `deploy-content-agents`
first and do not continue until the shared standalone OVRTX renderer plus
independent Material and Physics service containers are healthy and exported
through `CONTENT_AGENTS_*_BASE_URL`. Deploy the Texture Agent too when texture
generation is requested.

If required deployment authentication is missing, ask the user for
`NVIDIA_API_KEY` and wait. If a provided endpoint requires usage auth, ask for
the appropriate usage token instead. If deployment cannot produce healthy
services, report Content Agents readiness as blocked instead of proceeding to
conversion.

## Instructions

1. Confirm the source asset path exists, resolve `output_root`, and classify
   the request as end-to-end, conversion-only, validation-only, or packaging.
2. Resolve `property_assignment_intent` before running any asset inspection,
   converter probe, conversion, validation, conformance, rendering, or
   packaging step.
3. Run `preflight` for the selected workflow targets, unless a ready
   `PHYSICAL_AI_PREFLIGHT_MANIFEST` is 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-tools` value to scope dependency checks, but `convert-to-usd`
   and the upstream converter references still decide actual conversion support.
4. Verify or deploy Content Agents services first when
   `property_assignment_intent=run`; block on missing authentication or
   unhealthy services instead of continuing.
5. Read `references/workflow.md` and `references/commands.md`, then run only
   the stage references needed for the current request.
6. Run `identify-asset-context` on the original source asset when web search is
   available or property assignment will run.
7. Route the source through `convert-to-usd`, or skip conversion for existing
   USD input and treat the source path as the current USD path.
8. Run `validate-usd-minimum` before expensive downstream work. Treat this as a
   viability gate only: record unit/profile issues such as `metersPerUnit !=
   1.0`, but do not run `simready-conform-profile`, FET001, or any other FET
   repair before Content Agents assignment when property assignment will run.
9. Run Content Agents material, physics, and optional texture assignment on the
   converted/minimum-valid USD when requested or required.
10. Run `simready-conform-profile` on the latest simulation USD path after
   property assignment and preserve every selected FET repair report.
11. Run validation gates in order: `omni-asset-validate`,
   `omni-asset-validate-geometry`, `omni-asset-validate-physics`, and
   `simready-validate`.
12. Rerun `simready-conform-profile` when `simready-validate` reports a
    repairable requirement, then rerun profile validation on the newest authored
    USD.
13. Run `ovrtx-render-service` when preview, thumbnail, or inspection images
    are requested. When package outputs are requested, run
    `assemble-package-source` next to create the clean `deliverable/` package
    source from the final USD and thumbnail, then run `nv-core-package-sample`
    and `nv-core-package-sample-validation` on that deliverable folder only.
14. Emit the consolidated workflow report with the final USD path, all stage
    reports, validation findings, rerun reasons, and next work.

Use the `simready-conform-profile` reference only after property assignment
when `property_assignment_intent=run`. It routes feature repair to upstream
SimReady Foundation FET skills such
as `simready-foundation-conform-fet-000-core`,
`simready-foundation-conform-fet-001-minimal`,
`simready-foundation-conform-fet-004-simulate-multi-body-physics`, and
`simready-foundation-conform-fet-005-simulate-grasp-physics` from branch
`main`.

If `simready-validate` reports a repairable requirement after the first
conformance pass, feed the structured requirement IDs back into
the `simready-conform-profile` reference before writing the final result. In
particular, `GSP.001` is owned by upstream
`simready-foundation-conform-fet-005-simulate-grasp-physics`; run that skill when a
vision-capable agent can inspect visual evidence or explicit grasp points were
provided, otherwise record the FET005 step as blocked by missing vision/poin