Official agent skill

I4h Lerobot Viz

by NVIDIA in NVIDIA/skills

Serve and visually inspect a converted LeRobot dataset in the browser.

OfficialApache-2.0Auto-check passedProductivity & Automation

Install I4h Lerobot Viz

skills CLI
$ npx skills add NVIDIA/skills --skill i4h-lerobot-viz -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install NVIDIA/skills i4h-lerobot-viz --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/NVIDIA/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/i4h-lerobot-viz .claude/skills/i4h-lerobot-viz && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
i4h-lerobot-viz
GitHub stars
3.6k
Used in
1 other repo
Token cost
~976 tokens
SKILL.md length
327 words
Files
5
Skills in repo
390
Repo updated
First seen
Licence
Apache-2.0

At a glance

Serve and visually inspect a converted LeRobot dataset in the browser.

  • Works in 4 steps: Resolve the base checkout and one… → Launch its managed local server. → Open the printed URL. → …
  • Videos and state/action timelines
  • SKILL.md covers Purpose, Instructions, Resolve the dataset and Serve, plus 6 more sections
  • Calls git; reaches github.com

What it does

I4h Lerobot Viz is an agent skill from NVIDIA/skills, published by the product's own GitHub organization. Serve and visually inspect a converted LeRobot dataset in the browser. Use for videos and state/action timelines; do not use for raw workflow HDF5 or incomplete conversion output.

Its SKILL.md is about 980 tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files (for example `BENCHMARK.md`, `evals/evals.json` and `skill-card.md`).

It sits in Productivity & Automation, covering Browser automation. The repository describes itself as: Agent Skills for NVIDIA products — install into Claude Code, Codex, and other coding agents to run Physical AI, robotics, simulation, CUDA, and RAG workflows end to end. The licence is Apache-2.0.

When your agent uses it

  • Videos and state/action timelines
  • Do not use for raw workflow HDF5
  • Incomplete conversion output

Example prompts

  • “/i4h-lerobot-viz”

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Resolve the base checkout and one completed LeRobot dataset.
  2. Launch its managed local server.
  3. Open the printed URL.
  4. Inspect videos, timelines, episode count, and cleanup state.

What it can do on your machine

Read from SKILL.md and the folder at commit 14a98ae. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • github.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

I4h Lerobot Viz loads about 976 tokens when it runs. Until then it costs about 49 tokens; SKILL.md has 327 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~49
When it runs · the whole SKILL.md, loaded when a task matches
~976

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from NVIDIA/skills at commit 14a98ae, republished under its Apache-2.0 licence (© NVIDIA). 327 words, ~976 tokens.

Download SKILL.mdSave it as .claude/skills/i4h-lerobot-viz/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.
name
i4h-lerobot-viz
description
Serve and visually inspect a converted LeRobot dataset in the browser. Use for videos and state/action timelines; do not use for raw workflow HDF5 or incomplete conversion output.
license
Apache-2.0
metadata.author
Isaac for Healthcare Team <isaac-for-healthcare-support@nvidia.com>
metadata.version
0.8.0
metadata.verification-request
2026-09-15
metadata.tags
isaac-for-healthcare, i4h, dataset, lerobot, visualization

Visualize a LeRobot Dataset

Purpose

Serve one completed local dataset and verify its episode videos and timelines in a browser.

Instructions

  1. Resolve the base checkout and one completed LeRobot dataset.
  2. Launch its managed local server.
  3. Open the printed URL.
  4. Inspect videos, timelines, episode count, and cleanup state.

Resolve the dataset

bash
export I4H_WORKFLOWS_REPO_URL="${I4H_WORKFLOWS_REPO_URL:-https://github.com/isaac-for-healthcare/i4h-workflows}"
I4H_REPO_DIR_NAME="${I4H_WORKFLOWS_REPO_URL%/}"
I4H_REPO_DIR_NAME="${I4H_REPO_DIR_NAME##*/}"
I4H_REPO_DIR_NAME="${I4H_REPO_DIR_NAME##*:}"
I4H_REPO_DIR_NAME="${I4H_REPO_DIR_NAME%.git}"
[ -n "$I4H_REPO_DIR_NAME" ] || { echo "Cannot derive a checkout name from I4H_WORKFLOWS_REPO_URL" >&2; exit 2; }
ROOT="${I4H_WORKFLOWS:-$(git rev-parse --show-toplevel 2>/dev/null)}"
if [ ! -d "$ROOT/workflows/i4h_workflows" ]; then
  ROOT="${I4H_WORKFLOWS:-$HOME/$I4H_REPO_DIR_NAME}"
  [ -d "$ROOT/workflows/i4h_workflows" ] || git clone "$I4H_WORKFLOWS_REPO_URL" "$ROOT"
fi
export I4H_WORKFLOWS="$ROOT"
cd "$ROOT"
find runs "${HF_LEROBOT_HOME:-$HOME/.cache/huggingface/lerobot}" \
  -name info.json -path '*/meta/*' -printf '%T@ %h\n' 2>/dev/null \
  | sort -nr | head

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/i4h_workflows. I4H_WORKFLOWS_REPO_URL selects the clone source. When I4H_WORKFLOWS is unset, derive the fallback directory from that URL; set I4H_WORKFLOWS only to reuse or choose a specific destination. Never replace an existing checkout.

Use the explicit/current-chain converted directory. Otherwise select the newest candidate and state the choice. Require <dataset>/meta/info.json; route raw HDF5 to i4h-workflow-dataset-convert.

Serve

Pass an absolute local path:

bash
DATASET_DIR=/absolute/path/to/lerobot/dataset
STATE_DIR=/absolute/path/to/run/viz-state
tools/dataset/scripts/viz.sh "$DATASET_DIR" --state-dir "$STATE_DIR"

The script selects a free local port, waits for HTTP readiness, and prints the URL, PID, state files, log, and exact stop command. Keep it running only while the user wants access.

Verify visually

Open the printed URL. Confirm:

  • the requested episode list loads
  • every expected camera video renders
  • state and action timelines render with plausible dimensions and motion
  • episode count and task text match meta/info.json
  • no blank page, missing video, or wrong dataset is being served

Reuse a live server only when its target dataset matches. Otherwise stop it using its printed state directory and port, then start the requested dataset.

Troubleshooting

If startup or the page fails, inspect meta/info.json, videos, the printed server log, and port ownership before restarting.

Prerequisites

Require the dataset tool environment and a completed LeRobot dataset with meta/info.json.

Limitations

The visualizer does not accept raw workflow HDF5 or repair incomplete metadata/videos.

Examples

  • Open the latest converted LeRobot dataset for inspection. → choose the newest verified dataset, serve it, and report the observed videos/timelines plus cleanup command.

Completion gate

Report dataset path, repo id, local URL, episode/camera/timeline observations, PID/state directory, and exact cleanup command.

© NVIDIA, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 4 other files in skills/i4h-lerobot-viz of NVIDIA/skills.

  • SKILL.md
  • BENCHMARK.md
  • evals/evals.json
  • skill-card.md
  • skill.oms.sig

Open the folder on GitHubat commit 14a98ae

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in NVIDIA/skills, which our catalogue first saw on October 7, 2026.

Compare with similar skills

I4h Lerobot Viz next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

I4h Lerobot Viz compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
I4h Lerobot Viz this skillNVIDIA/skills3.6k1 repos~976Automated safety check: PassApache-2.0
Agent Browserquran/quran.com-frontend-next1.9k40 repos~3.3kAutomated safety check: PassNone
Dev-Browser CLI AutomationSawyerHood/dev-browser6.7k1 repos~455Automated safety check: PassMIT
Browser Automationopenclaw/openclaw392k—~2.9kAutomated safety check: PassMIT
Camoufox CLIBin-Huang/camoufox-cli3501 repos~4.5kAutomated safety check: PassMIT
BrowserVibiumDev/vibium2.9k—~4.8kAutomated safety check: PassApache-2.0

Similar skills

  • Agent Browser

    quran/quran.com-frontend-next

    Automates browser interactions for web testing, form filling, screenshots, and data extraction.

    1.9k GitHub starsUsed in 40 repos~3.3k tokens
    Productivity & AutomationAuto-check passed
  • Dev-Browser CLI Automation

    SawyerHood/dev-browser

    Browser automation with persistent named pages via the dev-browser CLI. Use when users ask to navigate websites, fill forms, take screenshots, extract web…

    6.7k GitHub starsUsed in 1 repo~455 tokens
    Productivity & AutomationAuto-check passed
  • Browser Automation

    openclaw/openclaw

    A skill your agent uses when controlling web pages with the OpenClaw browser tool, especially multi-step flows, login checks, tab management, or recovery from stale refs/timeouts.

    392k GitHub stars~2.9k tokensUpdated today
    Productivity & AutomationAuto-check passed
  • Camoufox CLI

    Bin-Huang/camoufox-cli

    Anti-detect browser automation CLI & Skills for AI agents. An agent skill from Bin-Huang/camoufox-cli.

    350 GitHub starsUsed in 1 repo~4.5k tokens
    Productivity & AutomationAuto-check passed
  • Browser

    VibiumDev/vibium

    Automate browsers with the Vibium CLI. An agent skill from VibiumDev/vibium.

    2.9k GitHub stars~4.8k tokensUpdated yesterday
    Productivity & AutomationAuto-check passed
  • Test AIRI display-model imports with agent-browser across stage-tamagotchi Electron, stage-web, and stage-pocket mobile web layouts.

    50k GitHub stars~1.1k tokensUpdated today
    Productivity & AutomationAuto-check passed

More from NVIDIA/skills

All 390 skills in this repo
  • Official

    A skill your agent uses when the user wants to deploy, run, debug, tear down, or call the REST API of the RTVI-CV 2D detection / tracking microservice.

    3.6k GitHub starsUsed in 1 repo~4.5k tokens
    Auto-check passed
  • Official

    Generates, validates, compares and explains HOLOLINK_def.svh macro files for the HSB IP, using bundled Python scripts and asking before it writes anything.

    3.6k GitHub stars~2.9k tokensUpdated yesterday
    Auto-check passed
  • Official

    Runs and validates an end-to-end Mission Control demo in a locally installed Isaac Sim, with a Nova Carter robot driven through a Python server.

    3.6k GitHub stars~4.8k tokensUpdated yesterday
    Auto-check passed
  • Orchestrates defect image generation for PCBA, metal surface and glass inspection with NVIDIA Cosmos AnomalyGen on OSMO, from cold-start Day 0 to real-photo Day 1 labeling.

    3.6k GitHub stars~5k tokensUpdated yesterday
    Auto-check: notes
  • Orchestrates video data augmentation and auto-labeling workflows on OSMO, from flow selection and preflight checks to submission, monitoring and output download.

    3.6k GitHub stars~4.7k tokensUpdated yesterday
    Auto-check: notes
  • Official

    Runs NVIDIA TAO Data Services KPI analysis on object detection results, comparing predictions to ground truth and writing per-class precision, recall and AP to a CSV.

    3.6k GitHub stars~2.7k tokensUpdated yesterday
    Auto-check: notes

Questions about I4h Lerobot Viz

What does I4h Lerobot Viz do?

Serve and visually inspect a converted LeRobot dataset in the browser. I4h Lerobot Viz is an agent skill from NVIDIA/skills, published by the product's own GitHub organization. Serve and visually inspect a converted LeRobot dataset in the browser.

When should I use I4h Lerobot Viz?

I4h Lerobot Viz fits situations like: videos and state/action timelines; do not use for raw workflow HDF5; incomplete conversion output.

How do I install I4h Lerobot Viz in Claude Code?

Run `npx skills add NVIDIA/skills --skill i4h-lerobot-viz -a claude-code`. Or copy the skill folder (skills/i4h-lerobot-viz in NVIDIA/skills) into .claude/skills/i4h-lerobot-viz in your project. Claude Code loads it when a task matches its description.

How do I install I4h Lerobot Viz in Codex?

Run `npx skills add NVIDIA/skills --skill i4h-lerobot-viz -a codex`. Or copy the skill folder (skills/i4h-lerobot-viz in NVIDIA/skills) into .agents/skills/i4h-lerobot-viz in your project. Codex loads it when a task matches its description.

Can I use I4h Lerobot Viz in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add NVIDIA/skills --skill i4h-lerobot-viz -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/i4h-lerobot-viz, .gemini/skills/i4h-lerobot-viz, .github/skills/i4h-lerobot-viz and .opencode/skills/i4h-lerobot-viz in your project.

What does I4h Lerobot Viz need to run?

Going by SKILL.md and its folder, I4h Lerobot Viz needs the command-line tools its instructions call (git).

Does I4h Lerobot Viz access the network?

SKILL.md names 1 domain. In commands or code: github.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is I4h Lerobot Viz safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does I4h Lerobot Viz use?

I4h Lerobot Viz is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does I4h Lerobot Viz use?

About 976 tokens (SKILL.md is roughly 3.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to I4h Lerobot Viz?

Skills that share tags, products or a category with I4h Lerobot Viz: Agent Browser (quran/quran.com-frontend-next, 1.9k stars), Dev-Browser CLI Automation (SawyerHood/dev-browser, 6.7k stars), Browser Automation (openclaw/openclaw, 392k stars) and Camoufox CLI (Bin-Huang/camoufox-cli, 350 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains I4h Lerobot Viz?

NVIDIA (a GitHub organization, an official publisher) maintains it in NVIDIA/skills, which has 3,555 GitHub stars. The repository holds 390 skills in this directory. The repository was last updated on October 9, 2026.

Source: NVIDIA/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.