Agent skill · NVIDIA
i4h-workflow-dataset-teleop
Record demonstrations through a workflow's teleop Task into workflow HDF5. Use for keyboard, leader, VR, or bus input; do not use for policy evaluation or autonomous rule-based Tasks.
What it needs
About 2k tokens when loaded.
What this skill does
Record Teleop Demonstrations Purpose Run the workflow's declared teleop graph through the shared SimulationRunner so actions, state, cameras, segments, attempts, and outcomes use the normal HDF5 contract. Instructions 1. Resolve the base checkout and live teleop device contract. 2. Choose a supported human-input device. 3. Record in the foreground through run.sh. 4. Inspect visible motion and HDF5 content. Resolve support 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. Require teleop in the live mode list. Read the workflow builder, its scene manifest teleop override, and the embodiment manifest's teleopdevices. Do not maintain a static support table in the skill. Choose input Use the named device when supported. Otherwise use the workflow builder's default device. Keep interactive keyboard/leader/VR/bus sessions visible and in the foreground. Surface the device controls and require the human operator to complete the task. Never pretend to provide human input in an unattended shell. Record Omit <device> to use the workflow default. Bare --record writes demos.hdf5 inside the launcher's automatic run directory. Read the absolute directory from the ==> run dir ... line or run.json; do not recreate its timestamp in the shell. When a larger pipeline requires a caller-selected shared directory, pass --run-dir "$RUNDIR" --record demos.hdf5; the launcher creates the directory and anchors the relative recording name inside it. An absolute --record path remains supported. Verify Require the final N/N episodes succeeded summary. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills NVIDIA/i4h-workflow-dataset-teleop