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://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/nv-core-package-sample/README.md
SimReady Package Asset
When to Use
Use this reference when the user wants to turn a clean, self-contained folder of
USD files into a SimReady package. For CAD-to-SimReady workflow outputs, create
that folder first with assemble-package-source and pass
{output_root}/deliverable here. This is a packaging workflow skill, not a CAD
conversion workflow. It runs the SimReady package phases explicitly:
source folder
-> pre-validation
-> create package definition and metadata
-> post-validation
-> report package resultThe installed reference entrypoint is scripts/run.py. It creates com.nvidia.simready.packaging.json, .metadata/com.nvidia.simready.packaging.bom.json, .metadata/com.nvidia.simready.root_usds.json, and a package report for the local backend.
Upstream Reference
The team reference workflow is NVIDIA's SimReady Foundation create-package skill:
https://github.com/NVIDIA/simready-foundation/blob/v2026.04.1/skills/simready-foundation-create-package/SKILL.mdAccess note: Browser or raw-file fetches of the upstream skill URL can fail in restricted environments. If that happens, use a local clone of https://github.com/NVIDIA/simready-foundation checked out to the exact ref in upstream-versions.lock.json (currently v2026.04.1) and read skills/simready-foundation-create-package/SKILL.md from that checkout. Prefer $OMNIVERSE_CAD_TO_SIMREADY_UPSTREAM_ROOT/simready-foundation or $HOME/.omniverse-cad-to-simready/upstreams/simready-foundation.
Use that upstream skill as the source of truth for the packaging flow. It drives assets/scripts/create_simready_package.py, which performs pre-validation, package creation, and post-validation in one command. Do not duplicate or reinterpret the upstream package workflow inside this reference; point to the upstream skill and run the upstream sample when formal packaging is required. In an installed reference, use scripts/run.py --backend wrapp --upstream-scripts-dir /path/to/simready-foundation/skills/simready-foundation-create-package/assets/scripts when the user has a local checkout and WRAPP runtime.
Dependencies
Require:
| Backend | Runtime |
|---|---|
local | this reference's portable scripts/run.py, OpenUSD Python APIs through pxr.Usd and pxr.Sdf |
wrapp | local checkout of skills/simready-foundation-create-package/assets/scripts, simready-validate, omni-wrapp-minimal[local], and the upstream create_simready_package.py workflow |
Do not silently fall back from wrapp to local. If the user asked for WRAPP publishing and the upstream sample or WRAPP dependencies are missing, report the blocked dependency and the exact missing input.
Inputs
Collect:
| Input | Requirement |
|---|---|
source | Required clean package source folder. For CAD-to-SimReady outputs, use {output_root}/deliverable, not the workflow output root or pipeline/. For the local backend, this folder becomes the package root. |
name | Required package name, such as apple_a01 or minimal_package. |
version | Required package version; default to 1.0.0 only when the user has not specified one. |
license | Required SPDX license identifier or LicenseRef-*; do not invent a license for a user's asset. |
root_usd | Required root USD path relative to source; repeat when the package has multiple entry points. |
repo | Required only for --backend wrapp. |
upstream_scripts_dir | Required only for --backend wrapp; must point at skills/simready-foundation-create-package/assets/scripts. The legacy --upstream-sample-dir flag is still accepted for older local checkouts. |
Ask before overwriting an existing package definition unless the user explicitly requested overwrite.
Instructions
Confirm the source folder exists.
Confirm at least one root USD entry point is known.
Run pre-validation against the source folder: root USD metadata, root USD openability, anchored asset paths, package self-containment, and referenced file types.
For the local backend, write package metadata and
com.nvidia.simready.packaging.json.For the WRAPP backend, call the upstream
create_simready_package.pythrough this reference'sscripts/run.py --backend wrapp.Run post-validation with
nv-core-package-sample-validationunless the user explicitly asks to skip it.Preserve the JSON report and summarize every phase as pass, fail, or blocked.
CLI Pattern
Local package creation:
python3 /path/to/skills/omniverse-cad-to-simready/references/nv-core-package-sample/scripts/run.py /path/to/source \
--name minimal_package \
--version 1.0.0 \
--license MIT \
--root-usd simready_usd/sm_minimal_package_01.usda \
--report /path/to/package-report.jsonWRAPP-backed publishing through the upstream sample:
python3 /path/to/skills/omniverse-cad-to-simready/references/nv-core-package-sample/scripts/run.py /path/to/source \
--backend wrapp \
--upstream-scripts-dir "$HOME/.omniverse-cad-to-simready/upstreams/simready-foundation/skills/simready-foundation-create-package/assets/scripts" \
--repo /path/to/repo \
--name apple_a01 \
--version 1.0.0 \
--license Apache-2.0 \
--root-usd sm_apple_a01_01.usd \
--report /path/to/package-report.jsonDo not use this command to convert CAD, URDF, MuJoCo, OBJ, DAE, or STL inputs. Convert to USD first with convert-to-usd.
Output Format
The report includes:
package_rootpackage_definition_pathskilltooloperationbackendprofilepassedstatuschecksphasesmetadatawarningserrorsnext_step
Pass/Fail Policy
Fail when:
the source folder is missing
root USD entries are missing, malformed, duplicated, missing on disk, or cannot be opened
asset references are absolute, search-path based, escape the package root, or point to missing files
package definition required fields are invalid
metadata entries, BOM entries, content hashes, package hashes, or root-USD metadata are invalid
the upstream WRAPP workflow fails
Warn when package content includes files outside the current MVP supported type set but those files are not referenced by USD layers.
Next Steps
Use nv-core-package-sample-validation to re-check a finished package definition. Use future publishing or repository upload skills after the package has passed post-validation.
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