Skip to content
Agentmart
Submit a tool

omniverse-cad-to-simready

Coordinate the end-to-end CAD/source-asset to SimReady workflow.

Skill by Omniverse

IndexedApache-2.0
Write a review

Chalk Labs

Need help deploying omniverse-cad-to-simready?

Chalk Labs sets up agents like this inside real teams: connected to your tools, tested on your data, with a human in the loop where it matters.

Book a call

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/sayalinvidia-omniverse-cad-to-simready

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

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.

Use cases: devops, writing, productivity

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found
Runs as
Python package

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/omniverse-cad-to-simready

What's inside

Skill 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.
License
Apache-2.0
Compatibility
Orchestrator skill. Managed Content Agents deployment requires NVIDIA_API_KEY (build.nvidia.com), Docker + NVIDIA Container Toolkit + GPU, Python 3.12, and an upstream checkout of nvidia-omniverse/content-agents on branch main. Reused/provided endpoints may instead use explicit endpoint and usage-token environment variables. Linux/macOS only.
Metadata
author: Omniverse · domain: ai-ml
Instructions
265 lines in SKILL.md · view on GitHub

Before installing

  • Ships executable scripts

Agent Skills spec issues

  • files: referenced but missing: scripts/run.py

Files (126)

  • BENCHMARK.md
  • SKILL.md
  • openai.yaml · agents/
  • evals.json · evals/
  • minimal_mesh.stl · evals/files/
  • README.md · references/assemble-package-source/
  • check_dependencies.py · references/assemble-package-source/scripts/
  • report_schema.json · references/assemble-package-source/scripts/
  • run.py · references/assemble-package-source/scripts/
  • commands.md · references/
  • README.md · references/content-agents/
  • README.md · references/content-agents/references/material-agent-client/
  • check_dependencies.py · references/content-agents/references/material-agent-client/scripts/
  • report_schema.json · references/content-agents/references/material-agent-client/scripts/
  • run.py · references/content-agents/references/material-agent-client/scripts/
  • README.md · references/content-agents/references/physics-agent-client/
  • check_dependencies.py · references/content-agents/references/physics-agent-client/scripts/
  • report_schema.json · references/content-agents/references/physics-agent-client/scripts/
  • run.py · references/content-agents/references/physics-agent-client/scripts/
  • README.md · references/content-agents/references/texture-agent-client/
  • check_dependencies.py · references/content-agents/references/texture-agent-client/scripts/
  • report_schema.json · references/content-agents/references/texture-agent-client/scripts/
  • run.py · references/content-agents/references/texture-agent-client/scripts/
  • check_dependencies.py · references/content-agents/scripts/
  • content_agent_check_dependencies.py · references/content-agents/scripts/
  • content_agent_client.py · references/content-agents/scripts/
  • content_agent_material_cleanup.py · references/content-agents/scripts/
  • content_agent_report_schema.json · references/content-agents/scripts/
  • report_schema.json · references/content-agents/scripts/
  • run.py · references/content-agents/scripts/
  • README.md · references/convert-to-usd/
  • README.md · references/convert-to-usd/references/mujoco-usd-converter/
  • check_dependencies.py · references/convert-to-usd/references/mujoco-usd-converter/scripts/
  • report_schema.json · references/convert-to-usd/references/mujoco-usd-converter/scripts/
  • run.py · references/convert-to-usd/references/mujoco-usd-converter/scripts/
  • README.md · references/convert-to-usd/references/openusd-exchange-sdk-usdex/
  • README.md · references/convert-to-usd/references/urdf-usd-converter/
  • check_dependencies.py · references/convert-to-usd/references/urdf-usd-converter/scripts/
  • report_schema.json · references/convert-to-usd/references/urdf-usd-converter/scripts/
  • run.py · references/convert-to-usd/references/urdf-usd-converter/scripts/
  • README.md · references/convert-to-usd/references/usd-convert-cad/
  • check_dependencies.py · references/convert-to-usd/references/usd-convert-cad/scripts/
  • kit_app_template_cad.py · references/convert-to-usd/references/usd-convert-cad/scripts/
  • report_schema.json · references/convert-to-usd/references/usd-convert-cad/scripts/
  • run.py · references/convert-to-usd/references/usd-convert-cad/scripts/
  • README.md · references/convert-to-usd/references/usd-convert-gsplat/
  • check_dependencies.py · references/convert-to-usd/references/usd-convert-gsplat/scripts/
  • report_schema.json · references/convert-to-usd/references/usd-convert-gsplat/scripts/
  • run.py · references/convert-to-usd/references/usd-convert-gsplat/scripts/
  • check_dependencies.py · references/convert-to-usd/scripts/
  • report_schema.json · references/convert-to-usd/scripts/
  • run.py · references/convert-to-usd/scripts/
  • README.md · references/deploy-content-agents/
  • deploy-material-agent-docker.md · references/deploy-content-agents/references/
  • deploy-ovrtx-docker.md · references/deploy-content-agents/references/
  • deploy-physics-agent-docker.md · references/deploy-content-agents/references/
  • deploy-texture-agent-docker.md · references/deploy-content-agents/references/
  • README.md · references/identify-asset-context/
  • check_dependencies.py · references/identify-asset-context/scripts/
  • report_schema.json · references/identify-asset-context/scripts/
  • …and 66 more

SKILL.md (first lines)

# 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

From sayalinvidia/sayali-skills-test, Apache-2.0.

More from sayalinvidia/sayali-skills-test

Signals

Stars
0
Forks
0
Open issues
43
Last commit (this folder)
May 29, 2026 (5 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License
Apache-2.0
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

Done for you

Rather not set it up yourself?

Chalk Labs scopes, builds and runs agents for your team: the task audit, the eval harness, the integrations and the weekly ops report. Fixed scope, priced before we start.

See how we build AI agents →Read the case studies

Chalk Labs is a two-founder AI and growth studio. We build AI agents, CRMs and MVPs for Web3 and AI companies, and have shipped 50+ product and token launches.

launches shipped
50+
launches shipped
media placements
500+
media placements
founders on every account
2
founders on every account

Press we've placed: Forbes · CoinDesk · Decrypt · Cointelegraph · The Block

Rahil Jain, Co-founder, Chalk Labs. Ex-Goldman Sachs engineer. You talk to the person who builds it.

Get omniverse-cad-to-simready running in your business

Tell us what you want to automate. A founder replies within one working day with a plan, not a pitch deck.

Goes to the Chalk Labs founders, not the newsletter. Privacy

Need help deploying omniverse-cad-to-simready?

CallGet help
Cite this page

omniverse-cad-to-simready skill. Agent Mart. https://agentmart.dev/skills/sayalinvidia-omniverse-cad-to-simready (last updated 2026-10-24)