i4h-workflow-finetune

Fine-tune GR00T or openpi PI0 robotic policies on LeRobot datasets.

3.2k|370|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/NVIDIA/skills --skill i4h-workflow-finetune
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: i4h-workflow-finetune
Source: https://github.com/NVIDIA/skills/tree/main/skills/i4h-workflow-finetune
Command: npx skills add https://github.com/NVIDIA/skills --skill i4h-workflow-finetune

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Training a GR00T or openpi PI0 robot policy on recorded demonstrations requires knowing the correct stack, CLI, environment configuration, and flags for each Isaac for Healthcare workflow. This Skill guides an agent through the exact fine-tuning procedure, from dataset validation to checkpoint verification, avoiding misconfigured runs.

Core Features & Use Cases

  • Stack and CLI mapping: Maps each environment (e.g., scissor_pick_and_place, ultrasound_liver_scan) to its correct training stack (gr00t_n15, gr00t_n16, openpi_pi0) and training CLI.
  • Guided training run: Provides preflight checks, dataset resolution, and a step-by-step training command with flags like --max-steps, --batch-size, and --no-tune-visual.
  • Verification and troubleshooting: Defines how to confirm checkpoints contain the expected safetensors and config files, and how to fix common errors such as invalid dataset paths or inference-only environments.
  • Use Case: A robotics engineer asks the agent to fine-tune a policy for the scissor pick-and-place task on a converted LeRobot dataset for a short smoke run; the Skill drives the correct gr00t_n15 training CLI and reports the checkpoint path and train_loss summary.

Quick Start

Ask your agent to fine-tune a policy for the scissor pick-and-place task on your converted LeRobot dataset for a short smoke run.

Frequently Asked Questions about i4h-workflow-finetune

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fine-tune a GR00T policy on a LeRobot dataset?

Point DATASET_PATH at a LeRobot directory containing meta/info.json, then run the environment's training CLI (e.g., i4h-agentic-gr00t-n15-train) with --dataset-path, --output-dir, and --max-steps. The Skill maps each environment to the correct stack and CLI automatically.

How to train an openpi PI0 policy for ultrasound liver scan?

The ultrasound_liver_scan environment maps to the openpi_pi0 stack and the i4h-agentic-openpi-pi0-train CLI. Run it with your converted LeRobot dataset path, output directory, and desired step count from the i4h-workflows repository root.

Which i4h environments support policy fine-tuning?

Train support is determined by policy.train_module in the environment's YAML config; a null value means inference-only. The assemble_trocar environment is inference-only, while scissor_pick_and_place, locomanip envs, and ultrasound_liver_scan support training.

Why does my fine-tuning run fail with an unrecognized flag error?

The training CLIs use Tyro, which requires kebab-case flags such as --max-steps rather than --max_steps. Rewrite any snake_case flags to kebab case and rerun the command.

What does the --no-tune-visual flag do during training?

The --no-tune-visual flag freezes the vision backbone so only the action head and projector are trained. This runs roughly twice as fast with half the memory and is a good default for small datasets.

Can I fine-tune without a GPU or with multiple GPUs?

At least one visible GPU is required, and --num-gpus must not exceed the count reported by nvidia-smi. Multi-GPU training is supported by setting --num-gpus to the desired number within that limit.