isaac-sim
Skill93 starsChanged 3 months agoMITView on GitHub
Build GPU-accelerated robot simulations and synthetic-data pipelines with NVIDIA Isaac Sim.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- jewel-nath/agentic-roboticstheir own version, first seen Nov 1, 2026
- Kayn-43/agent-configtheir own version, first seen Sep 15, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- jewel-nath/agentic-robotics★ 3same name
- Kayn-43/agent-config★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository32 other files it gives its agents.
- AGENTS.mdAGENTS.md
- learnings/AGENTS.mdAGENTS.md
- skills/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- learnings/CLAUDE.mdCLAUDE.md
- skills/CLAUDE.mdCLAUDE.md
- app-publishingSkill
- architectSkill
- cloud-runSkill
- dataSkill
- environmentsSkill
- foxgloveSkill
- gazeboSkill
- gemini-roboticsSkill
- huggingfaceSkill
- integrationSkill
- isaac-labSkill
- learning-loopSkill
- lerobotSkill
- live-demoSkill
- miningSkill
- mujocoSkill
- navigationSkill
- rerunSkill
- ros2Skill
- runpodSkill
- rviz2Skill
- simulationSkill
- skill-authorSkill
- test-assetsSkill
- testingSkill
- visualizationSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 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.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 13
Check the current NVIDIA requirements for GPU architecture, VRAM, driver, operating system, RAM, and storage.
- Distinctive: line 18
Prefer an official, pinned container when local/remote parity matters.
- Distinctive: line 36
Before installing or provisioning, read references/setup-and-requirements.md and re-check its dated values against current NVIDIA …
- Distinctive: line 45
When launch, rendering, streaming, or bridge behavior fails, start with FAILURES.md.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
Isaac Sim
Isaac Sim is a gated simulation stack. Prove the target hardware and release-compatible runtime before designing the robot application around it.
Pass the gate
- Check the current NVIDIA requirements for GPU architecture, VRAM, driver, operating system, RAM, and storage. An NVIDIA compute GPU without the required ray-tracing support is not interchangeable with a supported RTX GPU.
- Isaac Sim does not run on macOS. Use a qualifying remote host or choose a different simulator; do not search for a local workaround.
- Prefer an official, pinned container when local/remote parity matters. Verify the matching NGC tag, EULA requirements, host driver, and GPU passthrough at the time of use.
Build outward from a running simulation
- Runtime: the chosen Isaac Sim release starts cleanly on the target host.
- Scene: the USD stage, physics, units, and robot articulation match the intended application.
- Sensors: frames, rates, ranges, noise, and rendering modes match the real interfaces or the stated synthetic-data purpose.
- Integration: ROS 2 bridge version, distro, graph nodes, clock, and topic contracts agree with the external system.
- Operation: batch jobs run headless; an interactive viewport uses a supported streaming path rather than display forwarding assumptions.
Go deeper only when needed
- Before installing or provisioning, read references/setup-and-requirements.md and re-check its dated values against current NVIDIA documentation.
- For USD, robot import, sensors, or Replicator, read references/scenes-and-sensors.md.
- For the ROS boundary, read references/ros2-integration.md.
- For a remote interactive viewport, read references/webrtc-livestream.md.
- When launch, rendering, streaming, or bridge behavior fails, start with FAILURES.md.
- Isaac Lab owns policy training. Data owns source strategy; Isaac Sim owns the mechanics of generating synthetic data.
Done
- The pinned runtime passes a small headless scene, the required sensor or ROS output is measured, and any remote viewer works through the same deployment path the application will use.
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.