agentleFS
NVIDIAKnown publisherNVIDIA/simready-foundation/.agents/skills/simready-foundation-conform-fet-025-ros/SKILL.md

simready-foundation-conform-fet-025-ros

Skill156 starsChanged 54 days agoApache-2.0View on GitHub

Use for repairing exact FET_025_ROS SimReady conformance for Isaac ROS-Ready bridge-node presence. Use when a profile, validation report, or user request names FET_025_ROS; default to version `0.1.0`.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use this exact feature skill when the selected profile, validation report, or user request names FET_025_ROS.

    line 18
  2. Distinctive:

    If missing, prefer repairing in Isaac Sim by authoring an Action Graph with at least one ROS 2 bridge node, then saving the USD.

    line 38
  3. Distinctive:

    Do not invent arbitrary bridge nodes with placeholder topics in headless USD-only repair unless the user provides the intended ROS graph …

    line 39

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

SimReady Conform FET_025_ROS

Purpose

Use this exact feature skill when the selected profile, validation report, or user request names FET_025_ROS. It stages or reports Isaac ROS-Ready conformance for OmniGraph ROS 2 bridge nodes.

Default to FET_025_ROS@0.1.0.

Source of Truth

  • nv_core/tiers/simready_foundation_tier_core/simready/foundation/tier_core/features/FET_025_ROS-0.1.0.json
  • nv_core/tiers/simready_foundation_tier_core/simready/foundation/tier_core/features/FET_025_ROS.md
  • nv_core/tiers/simready_foundation_tier_core/simready/foundation/tier_core/capabilities/isaac_sim/ros_bridge/requirements/ros2-bridge-nodes-present.md

Feature Versions

VersionDependenciesRequirements
0.1.0NoneROS.001

Workflow

  1. Confirm the input stage/asset exists and the selected feature is FET_025_ROS@0.1.0.
  2. Validate for ROS.001 (at least one OmniGraph node:type starting with isaacsim.ros2.bridge.).
  3. If missing, prefer repairing in Isaac Sim by authoring an Action Graph with at least one ROS 2 bridge node, then saving the USD.
  4. Do not invent arbitrary bridge nodes with placeholder topics in headless USD-only repair unless the user provides the intended ROS graph contract.
  5. Re-validate and summarize.

Feature Guidance

  • Passing ROS.001 means bridge wiring is authored, not that topics/TF/QoS are correct.
  • Auto-authoring a full ROS graph without user intent is blocked; report blocked and ask for the intended publishers/subscribers.

Report Fields

FieldMeaning
featureExact feature ID and version, for example FET_025_ROS@0.1.0.
inputSource asset or stage inspected.
outputStaged output path, or in-place only when explicitly requested.
requirements_repairedRequirement IDs repaired in this pass.
validationCommand or inspection used to verify this exact feature.
statuspassed, failed, skipped, or blocked.
next_stepNext exact feature skill or user/runtime evidence needed.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.