simready-foundation-conform-fet-000-isaac
Skill156 starsChanged 54 days agoApache-2.0View on GitHub
Use for repairing exact FET_000_ISAAC SimReady conformance: Isaac packaging Core (clean folder, thumbnail, physics attribute/schema source layer). Use when a profile, validation report, or user request names FET_000_ISAAC; default to version `0.1.0`.
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-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-newtonSkill
- 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
8 rules. About 0 are common, 4 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 18
Use this exact feature skill when the selected profile, validation report, or user request names FET_000_ISAAC.
- Very specific: line 22
Default to FET_000_ISAAC@0.1.0 when the user asks for this feature without a version.
- Distinctive: line 26
Before changing an asset or package, read:
- Distinctive: line 37
Treat the selected JSON manifest as authoritative for dependencies and requirement IDs.
- Very specific: line 48
Ensure the neutral Core gate (FET_000_STANDARD@0.1.0) is in shape first.
- Distinctive: line 50
Create or use a staged output location unless the user explicitly asks for in-place edits.
- Distinctive: line 57
Keep only the interface asset and required subfolders at the package root.
- Very specific: line 58
Place the thumbnail at .thumbs/256x256/<asset-filename>.png next to the validated root asset.
≈ “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_000_ISAAC
Purpose
Use this exact feature skill when the selected profile, validation report, or user request names FET_000_ISAAC. It repairs or stages Isaac packaging Core on top of neutral Core, without drifting into robot identity or another runtime contract.
FET_000_ISAAC adds Isaac package cleanliness, thumbnail, and physics-layer placement expectations to an asset that already satisfies neutral Core (FET_000_STANDARD@0.1.0). Robot naming, schema, type, and root-joint policy belong to FET_021_ISAAC.
Default to FET_000_ISAAC@0.1.0 when the user asks for this feature without a version. If the report names a different FET_000_<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_000_ISAAC-0.1.0.jsonnv_core/tiers/simready_foundation_tier_core/simready/foundation/tier_core/features/FET_000_ISAAC.mdnv_core/tiers/simready_foundation_tier_core/simready/foundation/tier_core/features/FET_000_STANDARD-0.1.0.json(dependency)- Requirement docs under
nv_core/tiers/simready_foundation_tier_core/simready/foundation/tier_core/capabilities/isaac_sim/robot_core/requirements/:clean-folder.md(RC.001)thumbnail-exist.md(RC.004)verify-robot-physics-attribute-source-layer.md(RC.005)verify-robot-physics-schema-source-layer.md(RC.006)
Treat the selected JSON manifest as authoritative for dependencies and requirement IDs.
Feature Versions
| Version | Dependencies | Requirements |
0.1.0 | FET_000_STANDARD@0.1.0 | RC.001, RC.004, RC.005, RC.006 |
Workflow
- Confirm the input exists and identify the exact selected feature/version.
- Ensure the neutral Core gate (
FET_000_STANDARD@0.1.0) is in shape first; if Core fails, hand off tosimready-foundation-conform-fet-000-standardbefore this skill. - Load the
FET_000_ISAACmanifest, the feature markdown, and the RC.001/004/005/006 requirement docs. - Create or use a staged output location unless the user explicitly asks for in-place edits.
- Repair only
RC.001,RC.004,RC.005, andRC.006. Do not rewrite robot identity (RC.003,RC.007-RC.009). - Rerun the same profile gate or the narrowest available feature/capability validation gate.
- Summarize the selected version, changed files, validation evidence, and the first remaining blocker or next exact feature gate.
Feature Guidance
- Keep only the interface asset and required subfolders at the package root; remove stray sibling files.
- Place the thumbnail at
.thumbs/256x256/<asset-filename>.pngnext to the validated root asset. - Author
physics:attributes and Physics/PhysX schemas in the physics source layer, not the base layer. - For robot identity failures, hand off to
simready-foundation-conform-fet-021-isaac.
Report Fields
| Field | Meaning |
feature | Exact feature ID and version, for example FET_000_ISAAC@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.

