Use for Claude Code reviews that need robotics, simulation, GPU-routing, sim-to-real, or BDD100K pipeline domain context.
Scanned 9/8/2026
Install to Claude Code
Skills Directorynpx -y skills add nebius/nebius-physical-ai --skill physical-ai-context --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Physical Ai Context?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/nebius-physical-ai-context)More formats (shields.io, HTML) on the badges page.
---
name: physical-ai-context
description: Use for Claude Code reviews that need robotics, simulation, GPU-routing, sim-to-real, or BDD100K pipeline domain context.
---
# Physical AI Context
Sim-to-real pipeline:
1. RL teacher policy in Genesis.
2. Visual demos.
3. SimToLeRobot adapter.
4. Student policy in LeRobot.
5. Evaluation in Genesis.
Isaac Lab requires RT cores: L40S or RTX Pro 6000. H100 and H200 do not have RT cores.
Genesis serverless RL teacher training works. Visual demo generation is blocked on EGL/DRI device access in containers.
LeRobot is Tier 1 validated on B300. SONIC, GR00T, Isaac Lab, and Cosmos are vendor-paced on NVIDIA CUDA 13 alignment.
Route SONIC to H100; L40S on-demand capacity is effectively zero for the required preset.
The BDD100K demo pipeline is the reference end-to-end workflow. `workflows/testing/bdd100k-pipeline.yaml` is the canonical YAML.
Key claim: one YAML file describes a full Physical AI pipeline; SkyPilot orchestrates it on Nebius; results complete in about 30 minutes on a single H100.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Build reusable Terraform modules for AWS, Azure, and GCP infrastructure following infrastructure-as-code best practices. Use when creating infrastructure modules, standardizing cloud provisioning, or implementing reusable IaC components.
