Agent skill · NVIDIA

i4h-workflow-dataset-convert

Convert workflow HDF5 recordings to LeRobot datasets for training or browser inspection. Use for conversion; do not use for replay, augmentation, or raw-data repair.

What it needs

About 3k tokens when loaded.

What this skill does

Convert Workflow HDF5 to LeRobot Purpose Preserve recorded actions, state, cameras, task text, and embodiment labels in a local LeRobot dataset. Instructions 1. Run the checkout resolver and select the source HDF5. 2. Read the workflow, Scene, embodiment, and instruction. 3. Run conversion for the selected successful episodes. 4. Inspect metadata, parquet, videos, and feature widths. Resolve and inspect Treat the resolver above as part of the skill contract: a hosted copy may run outside the base repository, so never assume the current checkout contains workflows/i4hworkflows. I4HWORKFLOWSREPOURL selects the clone source. When I4HWORKFLOWS is unset, derive the fallback directory from that URL; set I4HWORKFLOWS only to reuse or choose a specific destination. Never replace an existing checkout. Use the explicit/current-chain recording. Resolve its workflow and Scene from recording metadata/context, then read the Scene manifest for the embodiment and instruction. Use the embodiment manifest for labels. Do not assume state width equals action width; the converter derives both from the recording. Convert Use --fps or --skip-frames only when the user requests it or source metadata justifies it. Keep the default H.264 video codec for compatibility with GR00T's fast decord loader; select another --video-codec only when the target consumer requires it. Conversion writes aggregate meta/stats.json for downstream policy loaders. Native G1 rule-based WBC recordings already contain 43-D state and 50-D action; the converter recognizes that contract and writes GR00T's required semantic meta/modality.json automatically. For a G1 recording made through the legacy 23-D Pink/keyboard contract and destined for a 50-D G1 WBC policy Task, add --g1-wbc-policy-actions. That explicit mapping combines the measured 43-joint state with the recorded navigation, base-height, and torso commands; require source action width 23 and state width 43. …

How to use it

Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:

@skills NVIDIA/i4h-workflow-dataset-convert

View the source on GitHub

Browse the @skills marketplace