New to Claude Skills? Learn how to install them →

nvidia on GitHub

i4h Agentic Workflow

OfficialFree

Navigate the i4h workflows for robotics and AI tasks.

by nvidia2.8k stars on nvidia/skills
Updated Aug 7, 2026
Get this skill

Free · Opens the source repo

What i4h Agentic Workflow does

The i4h Agentic Workflow skill serves as a navigation tool for users engaging with the i4h workflows, particularly in the context of robotics and AI. This skill provides an overview of the various environments, robots, and policies supported within the workflows/agentic/ subprojects. It is essential for users to understand how these components fit together and which specific skills to invoke at each stage of their workflow. The skill does not execute any pipeline stages itself but rather directs users to the appropriate skills needed for their tasks.

Users can leverage this skill to orient themselves before diving into specific stages of their projects. For instance, it helps in identifying the correct environment YAMLs located at workflows/agentic/config/environments/, which serve as the source of truth for the various setups. Additionally, it provides insights into the subprojects available within the i4h workflows, such as policy daemons, dataset management, and scene editing. This foundational understanding is crucial for efficient workflow management in robotics applications.

The i4h Agentic Workflow skill is particularly beneficial for developers and researchers working with the i4h robotics framework. It streamlines the process of setting up and executing complex workflows by ensuring that users have the right information at their fingertips. By guiding users through the available environments and associated skills, it minimizes the risk of errors and enhances productivity in robotics development.

Overall, this skill is an indispensable starting point for anyone looking to utilize the i4h workflows effectively, ensuring that they can navigate the complexities of robotics and AI with confidence.

When to use it

Use this skill when you need to understand the available environments and how to proceed with the i4h workflows.

When not to use it

This skill is not suitable for executing tasks or stages in the workflow; it is purely for orientation and routing.

What you can build with it

Setting Up a New Robotics Project

When starting a new project, use this skill to identify which environments and policies are available for your specific robotics application.

Navigating Complex Workflows

If you're unsure about the next steps in your workflow, this skill provides the necessary orientation to guide you through the available options.

Troubleshooting Environment Issues

Use this skill to quickly check supported environments and resolve any issues related to environment setup.

How to install i4h Agentic Workflow

View source

1. Install with the skills CLI

npx skills add nvidia/skills/i4h-workflow --agent claude-code

2. Or install it manually

Download the skill folder and drop it into ~/.claude/skills/ for all projects, or .claude/skills/ to scope it to one repo. Restart Claude Code so it picks up the new skill.

Anthropic's agentic coding CLI, and the reference implementation of Agent Skills. Drop a skill folder into ~/.claude/skills and Claude Code loads it automatically whenever a task matches the skill's description. Claude Code docs

Inside SKILL.md

Written by nvidia

i4h Agentic Workflow

Purpose

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.

Base Code

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"

Basics

  • Env YAMLs at workflows/agentic/config/environments/<env>.yaml are the source of truth.
  • Each pipeline stage has its own skill. Compose them or use [[i4h-workflow-e2e]] for full runs.
  • For env authoring or scene-edit source changes, load skills/i4h-workflow/references/repo-map.md before generating code.

Supported Envs

Fallback when --list-envs fails (setup incomplete):

EnvRobotPolicy
scissor_pick_and_placeSO-ARM 101GR00T N1.5 (N1.7 alternative)
locomanip_tray_pick_and_placeUnitree G1GR00T N1.6 (shared policy.locomanip.*)
locomanip_push_cartUnitree G1GR00T N1.6 (shared policy.locomanip.*)
assemble_trocarUnitree G1 + Dex handsGR00T N1.5 (inference-only)
ultrasound_liver_scanFranka-style armopenpi PI0
surgical_reach_psmdVRK PSMGR00T N1.5 or scripted state machine
surgical_reach_dual_psmdVRK dual PSMGR00T N1.5 or scripted state machine
surgical_reach_starSTARGR00T N1.5 or scripted state machine
surgical_lift_blockdVRK PSMGR00T N1.5 or scripted state machine
surgical_lift_needledVRK PSMGR00T N1.5 or scripted state machine
surgical_lift_needle_organsdVRK PSMGR00T N1.5 or scripted state machine

Run

Run the step below before answering. Each step is a separate bash call; variables persist in the local agent's tmux session.

Step 1 — list supported envs

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.

Subprojects

DirectoryPurpose
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 Index

SkillPurpose
i4h-workflow-setupInstall / sync / check third-party deps
i4h-workflow-createAdd a new env
i4h-workflow-scene-editEdit an existing scene / task / camera
i4h-workflow-dataset-teleopRecord human demos
i4h-workflow-dataset-replayReplay HDF5 episodes
i4h-workflow-dataset-mimicExpand HDF5 demos with noise
i4h-workflow-dataset-annotateVLM label / filter episodes
i4h-workflow-dataset-convertConvert HDF5 to LeRobot
i4h-workflow-finetuneTrain supported envs
i4h-workflow-validateRoll out / evaluate policy checkpoints
i4h-workflow-e2eRun the full pipeline
i4h-lerobot-vizOpen the LeRobot HTML viewer

Prerequisites

  • For any hands-on stage, set up the workflow first — see [[i4h-workflow-setup]] (component venvs and third-party checkouts present).
  • Env YAMLs at workflows/agentic/config/environments/<env>.yaml are the source of truth.

Limitations

  • Overview/routing only — each pipeline stage has its own skill; this one performs no recording, training, or rollout.

Troubleshooting

  • Error: env not found / unsupported — Cause: typo, unregistered env, or setup incomplete. Fix: run workflows/agentic/policy/run.sh --list-envs; if that fails, run [[i4h-workflow-setup]] first; otherwise check the Supported Envs table.

Final Response

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.

  1. Orientation — one short paragraph: env YAMLs, subprojects, sim-to-policy pipeline.

  2. Supported envs — heading plus markdown table from Step 1 (--list-envs output: env, stack, description) or the Supported Envs fallback table.

  3. Available skills — heading plus the full Skill Index table copied into the response.

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.

Frequently asked questions about i4h Agentic Workflow

Similar skills