Overview of `workflows/agentic/` (IsaacLab-Arena + GR00T/openpi). Use when the user asks what i4h workflow is, what's supported, or where to start.
npx skills add https://github.com/NVIDIA/skills --skill i4h-workflow
Orient on the agentic workflow before touching a specific stage: which envs/robots/policies are supported, how the workflows/agentic/ subprojects fit together, and which per-stage skill to invoke next. This skill routes — it runs no pipeline stage itself.
These steps drive the i4h-workflows base code (the workflows/agentic/ tree). To reuse an existing checkout, set I4H_WORKFLOWS to its path (no clone happens). Otherwise this resolves the current repo, or clones to ~/i4h-workflows — pick that default without prompting. Run every command below from the resolved root:
# Resolve the i4h-workflows base code (provides workflows/agentic/).
ROOT="${I4H_WORKFLOWS:-$(git rev-parse --show-toplevel 2>/dev/null)}"
if [ ! -d "$ROOT/workflows/agentic" ]; then
ROOT="${I4H_WORKFLOWS:-$HOME/i4h-workflows}"
[ -d "$ROOT/workflows/agentic" ] || git clone https://github.com/isaac-for-healthcare/i4h-workflows "$ROOT"
fi
export I4H_WORKFLOWS="$ROOT"; cd "$ROOT"
workflows/agentic/config/environments/<env>.yaml are the source of truth.skills/i4h-workflow/references/repo-map.md before generating code.Fallback when --list-envs fails (setup incomplete):
| Env | Robot | Policy |
|---|---|---|
| scissor_pick_and_place | SO-ARM 101 | GR00T N1.5 (N1.7 alternative) |
| locomanip_tray_pick_and_place | Unitree G1 | GR00T N1.6 (shared policy.locomanip.*) |
| locomanip_push_cart | Unitree G1 | GR00T N1.6 (shared policy.locomanip.*) |
| assemble_trocar | Unitree G1 + Dex hands | GR00T N1.5 (inference-only) |
| ultrasound_liver_scan | Franka-style arm | openpi PI0 |
| surgical_reach_psm | dVRK PSM | GR00T N1.5 or scripted state machine |
| surgical_reach_dual_psm | dVRK dual PSM | GR00T N1.5 or scripted state machine |
| surgical_reach_star | STAR | GR00T N1.5 or scripted state machine |
| surgical_lift_block | dVRK PSM | GR00T N1.5 or scripted state machine |
| surgical_lift_needle | dVRK PSM | GR00T N1.5 or scripted state machine |
| surgical_lift_needle_organs | dVRK PSM | GR00T N1.5 or scripted state machine |
Run the step below before answering. Each step is a separate bash call; variables persist in the local agent's tmux session.
REPO_ROOT="${I4H_WORKFLOWS:-$(git rev-parse --show-toplevel 2>/dev/null)}"; [ -d "$REPO_ROOT/workflows/agentic" ] || REPO_ROOT="$HOME/i4h-workflows"
"${REPO_ROOT}/workflows/agentic/policy/run.sh" --list-envs
If the command fails, use the Supported Envs fallback table above.
| Directory | Purpose |
|---|---|
| workflows/agentic/arena/ | IsaacLab-Arena envs, scenes, tasks, teleop, record, replay |
| workflows/agentic/policy/ | Policy daemons and train dispatchers |
| workflows/agentic/dataset/ | HDF5 → LeRobot conversion and visualization |
| workflows/agentic/mimic/ | HDF5 trajectory expansion |
| workflows/agentic/annotator/ | VLM success labels and filtering |
| workflows/agentic/cosmos/ | Optional Cosmos Transfer video augmentation |
| workflows/agentic/common/ | Shared config, messaging, robot constants |
| Skill | Purpose |
|---|---|
| i4h-workflow-setup | Install / sync / check third-party deps |
| i4h-workflow-create | Add a new env |
| i4h-workflow-scene-edit | Edit an existing scene / task / camera |
| i4h-workflow-dataset-teleop | Record human demos |
| i4h-workflow-dataset-replay | Replay HDF5 episodes |
| i4h-workflow-dataset-mimic | Expand HDF5 demos with noise |
| i4h-workflow-dataset-annotate | VLM label / filter episodes |
| i4h-workflow-dataset-convert | Convert HDF5 to LeRobot |
| i4h-workflow-finetune | Train supported envs |
| i4h-workflow-validate | Roll out / evaluate policy checkpoints |
| i4h-workflow-e2e | Run the full pipeline |
| i4h-lerobot-viz | Open the LeRobot HTML viewer |
workflows/agentic/config/environments/<env>.yaml are the source of truth.workflows/agentic/policy/run.sh --list-envs; if that fails, run [[i4h-workflow-setup]] first; otherwise check the Supported Envs table.The response is incomplete unless it includes all three parts below, each separated by a blank line. Do not reply with prose only or run sections together without spacing.
--list-envs output: env, stack, description) or the Supported Envs fallback table.Then (after another blank line) recommend [[i4h-workflow-setup]] if setup is not done, and name one next stage skill matched to the user's goal.
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
Intelligently organizes your files and folders across your computer by understanding context, finding duplicates, suggesting better structures, and automating cleanup tasks. Reduces cognitive load and keeps your digital workspace tidy without manual effort.
Generates creative domain name ideas for your project and checks availability across multiple TLDs (.com, .io, .dev, .ai, etc.). Saves hours of brainstorming and manual checking.
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Implements Manus-style file-based planning for complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when starting complex multi-step tasks, research projects, or any task requiring >5 tool calls.
Creative research ideation and exploration. Use for open-ended brainstorming sessions, exploring interdisciplinary connections, challenging assumptions, or identifying research gaps. Best for early-stage research planning when you do not have specific observations yet. For formulating testable hypotheses from data use hypothesis-generation.
Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
Take nvidia/i4h-workflow from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.