Index of every page on this site: llms.txt
All skills
nvidia avatar

/i4h-workflow

@6b75e9e
by NVIDIA Corporationnvidia/skills4.1k stars
547
Run it yourself

Orient users to the i4h workflow runtime and route them to the correct stage skill. Use for architecture, support, or where-to-start questions; do not execute a known stage.

Use this Skill: https://skilld.dev/gh/nvidia/skills/i4h-workflow

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈47 tokens for metadata: the name and description. ≈1.2k when used: this file. ≈4.1k more on demand in 4 files.

Description uses 2.4% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈188 characters, or 2.4%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

i4h Workflows

Purpose

Orient the user from live repository facts, then hand execution to the narrowest stage skill.

Instructions

  1. Run the base-checkout resolver.
  2. Read live support and DESIGN.md.
  3. Use only current architecture facts in the answer.
  4. Use the narrowest stage skill for execution.

Resolve the checkout

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"

Treat this resolver 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.

Inspect before answering

Read ./DESIGN.md for architecture and skills/i4h-workflow/references/repo-map.md for ownership. Discover current support instead of copying a static table:

./run.sh list

If discovery fails because setup is incomplete, report that limitation and route to i4h-workflow-setup.

Explain the design

Keep the summary precise:

  • A Scene owns the simulated world, assets, embodiment, cameras, randomization, adapters, and reset hooks.
  • A Task owns one reusable capability. It reads ctx.scene, writes ctx.act, and never advances the simulator.
  • A Workflow selects one Scene, exposes run-mode-specific TaskGraph builders, and owns goal semantics. A run mode answers how that workflow should run; code and CLI use the shorter term mode.
  • The Engine schedules graph nodes; the shared SimulationRunner alone resets, steps, renders, records, retries whole episodes, and prints run summaries.
  • Online RL is a separate training lifecycle: its trainer owns vectorized stepping and returns a checkpoint to the normal policy Task and SimulationRunner validation path.
  • Simulator-compatible exported RSL-RL actors may run as in-process Tasks; incompatible foundation-model policy stacks remain remote.
  • Remote policy stacks run out of process and communicate over Zenoh; offline dataset tools remain independent of the simulator.
  • Python owns behavior. Manifests carry facts across dependency boundaries.

Do not describe retired environment YAMLs, per-mode runners, or separate policy/Arena launchers.

Route the next action

Goal Skill
Install, sync, or repair dependencies i4h-workflow-setup
Create a new workflow/environment i4h-workflow-create
Edit an existing scene, camera, task, or success rule i4h-workflow-scene-edit
Record demonstrations i4h-workflow-dataset-teleop
Replay HDF5 i4h-workflow-dataset-replay
Augment HDF5 i4h-workflow-dataset-mimic
Grade/filter HDF5 with a VLM i4h-workflow-dataset-annotate
Convert HDF5 to LeRobot i4h-workflow-dataset-convert
Inspect LeRobot in a browser i4h-lerobot-viz
Fine-tune a manifest-backed policy task i4h-workflow-finetune
RL post-train a supported policy in simulation i4h-workflow-train-rl
Run policy or rule-based rollouts i4h-workflow-validate
Run the maintained complete pipeline i4h-workflow-e2e

For Stop all, do not load a stage skill. Run ./stop.sh all from the repository root and report the stopped process count.

Troubleshooting

If discovery fails, verify the resolved checkout and run setup. If a mode is absent, report it as unsupported.

Prerequisites

Require a readable base checkout or network access to clone it.

Limitations

This router does not install, author, simulate, process data, train, or evaluate.

Examples

  • What does the i4h workflow include, and where should I start? → inspect live support, summarize DESIGN.md, and recommend one stage skill.

Completion gate

Answer with the live workflow/mode list, a short architecture summary, and one concrete next skill. If the requested workflow or mode is absent from run.sh list, say it is unsupported instead of inventing a command.

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts1mo3 checks · Risk SAFE
  • Gen Agent Trust Hub1mo

    The skill manages orientation and routing for the Isaac for Healthcare (i4h) workflow. It downloads the project's repository and executes scripts for workflow discovery and cleanup. While these are standard developer tools, the process involves executing code from an external repository and ingesting data that could be used for indirect prompt injection.

  • Socket1mo

    No alerts

  • Snyk1mo

    Risk: LOW · No issues

Signed by skilld at 6b75e9e. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 2 months ago
Other metadata
metadata
{
  "author": "Isaac for Healthcare Team <isaac-for-healthcare-support@nvidia.com>",
  "version": "0.8.0",
  "verification-request": "2026-09-15",
  "tags": [
    "isaac-for-healthcare",
    "i4h",
    "robotics",
    "onboarding"
  ]
}

README badge

README badge for nvidia/skills/i4h-workflow