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

92%

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

85%Weight 40%Scale 1-3

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-structured orchestrator skill with strong actionability, sequencing, and validation checkpoints, plus an intentional one-level-deep reference tree that exists on disk. Its main weakness is redundant restatement of the same guardrails across sections, which slightly hurts token efficiency.

Suggestions

Consolidate the repeated 'do not run asset inspection/conversion/validation/conformance before Content Agents readiness' guardrail into a single canonical statement in Hard Rules, then reference it from First Action and Instructions instead of restating it.

The 'RB.MB.001' / FET004 routing guidance appears in both Instructions and the Troubleshooting table; keep the detailed version in one place and cross-reference from the other.

Consider moving the lengthy preflight env-var contract details into references/preflight/README.md and summarizing the contract in the body, since preflight already has its own README.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and densely domain-specific, but several policies repeat verbatim across First Action, Instructions, and Hard Rules (e.g., 'do not run asset inspection... before Content Agents readiness'), so it could be tightened. It does not earn a 3 because of this redundancy, nor a 1 since it does not explain concepts Claude already knows.	2 / 3
Actionability	It gives a concrete 14-step workflow, names exact stage references (convert-to-usd, validate-usd-minimum, simready-conform-profile), and supplies specific commands and remediation (e.g., 'docker exec --user root content-material-agent-service chmod -R a+rX ...'), which is copy-paste ready for an instruction-only orchestrator.	3 / 3
Workflow Clarity	The 14 steps are explicitly sequenced with validation gates ('Run validate-usd-minimum before expensive downstream work', ordered omni-asset-validate gates), stop/continue rules, and a feedback loop (rerun simready-conform-profile when simready-validate reports a repairable requirement).	3 / 3
Progressive Disclosure	SKILL.md is a clear overview that signals one-level-deep references (references/workflow.md, references/commands.md, and per-stage README.md files), all verified to exist as real bundle files, with explicit guidance to 'Read only the references needed for the current request.'	3 / 3
	Total	11 / 12 Passed

Description

100%Weight 40%Scale 1-3

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 is specific, complete, and distinctive, naming concrete pipeline actions and explicit use-when triggers for a well-scoped domain. It is somewhat long but every clause carries signal rather than fluff.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions such as 'conversion, material/physics assignment, SimReady conformance, validation, and optional package creation', matching the anchor for listing several specific concrete actions.	3 / 3
Completeness	It clearly states what it does ('Coordinate the end-to-end...') and when to use it via an explicit 'Use for broad requests such as...' clause, answering both what and when.	3 / 3
Trigger Term Quality	Natural trigger terms a user would say are present ('CAD to SimReady', 'source asset to simulation-ready USD', 'prop packaging'), giving good coverage rather than jargon.	3 / 3
Distinctiveness Conflict Risk	'CAD/source-asset to SimReady' is a clear, narrow niche with distinct triggers, making it unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 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: 11c74d6

Reviewed: 17 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.