simready-foundation-conform-fet-004-newton
Skill156 starsChanged 54 days agoApache-2.0View on GitHub
Use for repairing exact FET_004_NEWTON SimReady conformance for simulate multi-body physics (newton) conformance. Use when a profile, validation report, or user request names FET_004_NEWTON. FET_004_NEWTON has a single published version, 1.
In this repository241 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- simready-foundation-add-capabilitySkill
- simready-foundation-add-feature-adapterSkill
- simready-foundation-add-featureSkill
- simready-foundation-add-profileSkill
- simready-foundation-add-requirementSkill
- simready-foundation-add-runtime-testSkill
- simready-foundation-add-validatorSkill
- simready-foundation-conform-fet-000-isaacSkill
- simready-foundation-conform-fet-000-mujocoSkill
- simready-foundation-conform-fet-000-newtonSkill
- simready-foundation-conform-fet-000-physxSkill
- simready-foundation-conform-fet-000-standardSkill
- simready-foundation-conform-fet-001-standardSkill
- simready-foundation-conform-fet-002-standardSkill
- simready-foundation-conform-fet-003-mujocoSkill
- simready-foundation-conform-fet-003-newtonSkill
- simready-foundation-conform-fet-003-physxSkill
- simready-foundation-conform-fet-003-standardSkill
- simready-foundation-conform-fet-004-mujocoSkill
- simready-foundation-conform-fet-004-physxSkill
- simready-foundation-conform-fet-004-robot-mujocoSkill
- simready-foundation-conform-fet-004-robot-newtonSkill
- simready-foundation-conform-fet-004-robot-physxSkill
- simready-foundation-conform-fet-004-standardSkill
- simready-foundation-conform-fet-005-standardSkill
- simready-foundation-conform-fet-006-mdlSkill
- simready-foundation-conform-fet-006-openpbrSkill
- simready-foundation-conform-fet-006-standardSkill
- simready-foundation-conform-fet-007-standardSkill
- simready-foundation-conform-fet-010-standardSkill
- simready-foundation-conform-fet-011-standardSkill
- simready-foundation-conform-fet-021-isaacSkill
- simready-foundation-conform-fet-022-isaacSkill
- simready-foundation-conform-fet-022-mujocoSkill
- simready-foundation-conform-fet-022-newtonSkill
- simready-foundation-conform-fet-022-physxSkill
- simready-foundation-conform-fet-022-standardSkill
- simready-foundation-conform-fet-023-isaacSkill
- simready-foundation-conform-fet-024-mujocoSkill
- simready-foundation-conform-fet-024-newtonSkill
- simready-foundation-conform-fet-024-physxSkill
- simready-foundation-conform-fet-024-standardSkill
- simready-foundation-conform-fet-025-rosSkill
- simready-foundation-conform-fet-028-isaacSkill
- simready-foundation-conform-fet-028-mujocoSkill
- simready-foundation-conform-fet-028-standardSkill
- simready-foundation-conform-fet-030-standardSkill
- simready-foundation-conform-fet-031-standardSkill
- simready-foundation-conform-fet-032-standardSkill
- simready-foundation-conform-fet-033-standardSkill
- simready-foundation-conform-fet-100-isaacSkill
- simready-foundation-create-packageSkill
- simready-foundation-update-capabilitySkill
- simready-foundation-update-feature-adapterSkill
- simready-foundation-update-featureSkill
- simready-foundation-update-profileSkill
- simready-foundation-update-requirementSkill
- simready-foundation-update-validatorSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 3 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 17
Use this exact feature skill when the selected profile, validation report, or user request names FET_004_NEWTON.
- Distinctive: line 23
Before changing an asset or package, read:
- Distinctive: line 28
Treat the selected JSON manifest as authoritative for dependencies and requirement IDs.
- Very specific: line 40
When the input already conforms to the neutral base feature, prefer the deterministic feature adapter to author the runtime-specific data …
- Distinctive: line 54
Create or use a staged output location unless the user explicitly asks for in-place edits.
- Very specific: line 63
Do not use robot-specific collider exemptions unless the selected feature is FET_004_ROBOT_NEWTON.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
SimReady Conform FET_004_NEWTON
Purpose
Use this exact feature skill when the selected profile, validation report, or user request names FET_004_NEWTON. It repairs or stages simulate multi-body physics (newton) conformance without drifting into another runtime contract.
FET_004_NEWTON has a single published version, 0.1.0; use FET_004_NEWTON@0.1.0. If the report names a different FET_###_RUNTIME feature, switch to that feature's matching skill before editing.
Source of Truth
Before changing an asset or package, read:
nv_core/tiers/simready_foundation_tier_core/simready/foundation/tier_core/features/FET_004_NEWTON-0.1.0.jsonnv_core/tiers/simready_foundation_tier_core/simready/foundation/tier_core/features/FET_004_NEWTON.md
Treat 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.
Feature Versions
| Version | Dependencies | Requirements |
0.1.0 | FET_003_NEWTON@0.1.0 | JT.001, JT.002, JT.003, JT.ART.002, JT.ART.003, JT.ART.004, RB.MB.001, RB.011, RB.012 |
Newton collider requirements (NEWTON.COL.001, NEWTON.COL.002) and the Newton rigid-body base come from the FET_003_NEWTON@0.1.0 dependency.
Feature Adapter
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_newton | collider_neutral_to_prop_newton | FET_004_STANDARD@0.1.0 -> FET_004_NEWTON@0.1.0 | NewtonCollisionAPI + NewtonMeshCollisionAPI and newton:contactGap = 0 on existing colliders. |
- The adapter runs on a staged output stage and never creates geometry, joints, or articulation topology; it only annotates existing colliders.
FET_004_NEWTON@0.1.0is the multibody contract, so the adapter only covers the Newton collision annotation. The multibody requirements (JT.*,RB.MB.001,RB.011,RB.012) require existing joint/articulation topology and must be repaired manually per the Workflow below. Strict Newton isolation: noMjc*/Physx*data orphysics:approximation = "sdf".
Workflow
- Confirm the input exists and identify the exact selected feature/version from the profile TOML, validation report, or user request.
- Load the selected
FET_004_NEWTONmanifest and the feature markdown before editing. - Load requirement docs linked from the feature markdown for every reported failing requirement.
- Create or use a staged output location unless the user explicitly asks for in-place edits.
- Repair only the requirements listed by the selected
FET_004_NEWTONmanifest and its dependencies. - Rerun the same profile gate or the narrowest available feature/capability validation gate. If runtime evidence is required and unavailable, report that limitation instead of claiming a pass.
- Summarize the selected
FET_004_NEWTONversion, changed files, validation evidence, and the first remaining blocker or next exact feature gate.
Feature Guidance
- Repair Newton multibody joint and articulation requirements on existing rigid bodies, joints, and articulations. Do not create geometry.
- Newton collider conformance (
NEWTON.COL.001/NEWTON.COL.002, choosing NewtonMeshCollisionAPI or NewtonSDFCollisionAPI per collider without applying both on the same prim) is owned by theFET_003_NEWTON@0.1.0dependency; repair it there. - Do not use robot-specific collider exemptions unless the selected feature is FET_004_ROBOT_NEWTON.
- Runtime-variant packaging. For an asset that exposes physics through variant sets (
FET_000_NEWTONscaffolding), the Newton collider annotations (NewtonCollisionAPI/NewtonMeshCollisionAPI+newton:contactGap) andNewtonMaterialAPImaterial tuning belong in therunnables/physics/newton.usdpayload asovers on every collider and bound material — not on the neutral base. This skill repairs the joint/articulation topology on the neutral base (rigid bodies,UsdPhysicsjoints, exactly onePhysicsArticulationRootAPI, and no localphysics:approximationon any collider); author the per-runtime collider/material deltas viaFET_000_NEWTON.
Report Fields
| Field | Meaning |
feature | Exact feature ID and version, for example FET_004_NEWTON@0.1.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. |
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

