OverviewHistoryStatsSecurity
npx skills add ...
Documentation
SKILL.md
npx skills add nvidia/simready-foundation --skill simready-foundation-conform-fet-004-robot-physx
Use for compatibility repair of deprecated FET_004_ROBOT_PHYSX SimReady conformance. Use only when a historical or external profile, validation report, asset stamp, or user request explicitly names FET_004_ROBOT_PHYSX; never select it for a new profile version.
npx skills add nvidia/simready-foundation --skill simready-foundation-conform-fet-004-robot-physx
Use this exact feature skill when the selected profile, validation report, or user request names FET_004_ROBOT_PHYSX. It repairs or stages simulate multi-body physics (robot physx) conformance without drifting into another runtime contract.
FET_004_ROBOT_PHYSX is deprecated. This skill exists only to preserve
compatibility with historical or external contracts and assets that explicitly
name the feature. Never select or recommend it for a new profile version; use
FET_003_PHYSX@0.4.0 and FET_004_PHYSX@0.4.0 instead.
Default to FET_004_ROBOT_PHYSX@0.4.0 when the user asks for this feature without a version. Use an older integer version only when the profile, validation report, or user explicitly pins it. If the report names a different FET_###_RUNTIME feature, switch to that feature's matching skill before editing.
Before changing an asset or package, read:
nv_core/tiers/simready_foundation_tier_core/simready/foundation/tier_core/features/FET_004_ROBOT_PHYSX-0.1.0.jsonnv_core/tiers/simready_foundation_tier_core/simready/foundation/tier_core/features/FET_004_ROBOT_PHYSX-0.2.0.jsonnv_core/tiers/simready_foundation_tier_core/simready/foundation/tier_core/features/FET_004_ROBOT_PHYSX-0.3.0.jsonnv_core/tiers/simready_foundation_tier_core/simready/foundation/tier_core/features/FET_004_ROBOT_PHYSX-0.4.0.jsonnv_core/tiers/simready_foundation_tier_core/simready/foundation/tier_core/features/FET_004_ROBOT_PHYSX.mdTreat the selected JSON manifest as authoritative for dependencies and requirement IDs. Use the feature markdown for human-readable contract details, requirement links, samples, benchmarks, and adapters.
| Version | Dependencies | Requirements |
|---|---|---|
0.1.0 | None | RB.COL.002, RB.COL.003, RB.COL.004, RB.001, RB.003, RB.005, RB.006, RB.007, RB.009, RB.010, JT.001, JT.002, JT.003, JT.ART.002, JT.ART.003, JT.ART.004, RB.MB.001, RB.011, RB.012 |
0.2.0 | None | RB.COL.003, RB.COL.004, RB.001, RB.003, RB.005, RB.006, RB.007, RB.009, RB.010, JT.001, JT.002, JT.003, JT.ART.002, JT.ART.003, JT.ART.004, RB.MB.001, PHYSX.COL.001, PHYSX.COL.002, RB.011, RB.012 |
0.3.0 | None | RB.COL.003, RB.COL.004, RB.001, RB.003, RB.005, RB.007, RB.009, RB.010, JT.001, JT.002, JT.003, JT.ART.002, JT.ART.003, JT.ART.004, RB.MB.001, PHYSX.COL.001, PHYSX.COL.002, RB.011, RB.012 |
0.4.0 | None | RB.COL.003, RB.COL.004, RB.001, RB.003, RB.005, RB.007, RB.009, RB.010, JT.001, JT.002, JT.003, JT.ART.002, JT.ART.003, JT.ART.004, RB.MB.001, PHYSX.COL.001, PHYSX.COL.002, RB.011, RB.012 |
When the input already conforms to the neutral base feature, prefer the deterministic feature adapter to author the runtime-specific data first (via the workspace upgrade command; see nv_core/sr_specs/docs/guides/feature_adapters/feature_adapters.md), then repair only the residual requirements below.
| Adapter module | Adapter | Transition | Authors |
|---|---|---|---|
nv_core/cip_specs/asset_handler_modules/neutral_to_physx | rigid_body_neutral_to_robot_physx | FET_003_STANDARD@0.1.0 -> FET_004_ROBOT_PHYSX@0.2.0 | Mesh extents on all meshes. |
@2). The robot RB.*, JT.*, RB.MB.001, and PHYSX.COL.* requirements — and the @4 default — must be repaired manually per the Workflow below on existing robot link/joint topology.FET_004_ROBOT_PHYSX manifest and the feature markdown before editing.FET_004_ROBOT_PHYSX manifest and its dependencies.FET_004_ROBOT_PHYSX version, changed files, validation evidence, and the first remaining blocker or next exact feature gate.| Field | Meaning |
|---|---|
feature | Exact feature ID and version, for example FET_004_ROBOT_PHYSX@0.4.0. |
input | Source asset, package root, or package definition inspected. |
output | Staged output path, or in-place only when explicitly requested. |
requirements_repaired | Requirement IDs repaired in this pass. |
validation | Command or inspection used to verify this exact feature. |
status | passed, failed, skipped, or blocked. |
next_step | The next exact feature skill or user/runtime evidence needed. |