omniverse-cad-to-simready

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.

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Critical

Do not install without reviewing

The canonical home for this skill is omniverse-cad-to-simready in NVIDIA/skills

Quality

Content

73%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a well-sequenced orchestration overview with strong workflow clarity and validation feedback loops, delegating executable detail to one-level references. Its main weakness is redundancy of the same guardrails across multiple sections, which inflates length without adding clarity.

Suggestions

Consolidate the 'do not run stages before Content Agents readiness' guardrail into one authoritative location (e.g., Hard Rules) and reference it from First Action/Instructions/Troubleshooting instead of restating it verbatim each time.

Move the 'Publishing Layout Notes' repo-structure explanation into a separate CONTRIBUTING or publishing reference so the SKILL.md body stays focused on execution.

Confirm the deeply nested stage references (2+ levels) are each reachable through a clearly signaled one-level entry from the relevant stage README, so the nesting never becomes an opaque chain from the top-level skill.

Dimension	Reasoning	Score
Conciseness	Content is domain-dense with no basic-concept fluff, but the same guardrail (do not run stages before Content Agents readiness) is repeated across First Action, Instructions, Hard Rules, and Troubleshooting, and the Publishing Layout Notes add repo mechanics that could be trimmed.	3 / 5
Actionability	Concrete stage reference names, an explicit 14-step order, and specific env vars/report fields are given, with executable command patterns delegated to references/commands.md one level deep.	4 / 5
Workflow Clarity	A clearly sequenced 14-step workflow with explicit validation gates (validate-usd-minimum as a viability gate, ordered validation gates) and feedback loops (rerun simready-conform-profile on repairable requirements).	5 / 5
Progressive Disclosure	The body is a clean overview with well-signaled one-level references (preflight/README.md, workflow.md, commands.md, assemble-package-source/README.md), but the actual bundle is deeply nested (2+ levels under convert-to-usd, content-agents, simready-conform-profile), a minor organization gap though intentionally justified.	4 / 5
	Total	16 / 20 Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description clearly communicates a specialized orchestration niche with both a concrete what and an explicit when clause. It is comprehensive and distinct, with only minor gaps in trigger-term file extensions and action concreteness.

Dimension	Reasoning	Score
Specificity	Lists several concrete stages ("conversion, material/physics assignment, SimReady conformance, validation, and optional package creation" plus "deploy or verify Content Agents services"), though they read as stage names rather than fully concrete operations.	4 / 5
Completeness	Explicitly answers both what ("Coordinate the end-to-end CAD/source-asset to SimReady workflow") and when ("Use for broad requests such as...") with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural phrasings users would say are present ("CAD to SimReady", "source asset to simulation-ready USD", "prop packaging") with synonym variation, but no file extensions like .usd are included.	4 / 5
Distinctiveness Conflict Risk	A clear specialized niche (CAD/source-asset to SimReady orchestration) with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	18 / 20 Passed

Validation

75%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 12 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
referenced_paths_exist	Referenced path issues: 1 missing, 2 deeper-than-1-level	Warning

	Total	12 / 16 Passed

Repository: openai/plugins
Path: plugins/nvidia/skills/omniverse-cad-to-simready/SKILL.md
Commit: 1e28582

Reviewed: 9 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.