Official agent skill

I4h Workflow Setup

Preflight and set up the root-level workflow runtime. An agent skill from NVIDIA/skills.

OfficialApache-2.0Auto-check passed

Install I4h Workflow Setup

skills CLI

$ npx skills add NVIDIA/skills --skill i4h-workflow-setup -a claude-code

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

GitHub CLI

$ gh skill install NVIDIA/skills i4h-workflow-setup --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-workflow-setup .claude/skills/i4h-workflow-setup && 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/

Paste into Claude Code

Install the "i4h-workflow-setup" agent skill from https://github.com/NVIDIA/skills/tree/main/skills/i4h-workflow-setup into .claude/skills/i4h-workflow-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "i4h-workflow-setup", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/NVIDIA/skills/tree/main/skills/i4h-workflow-setup

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add NVIDIA/skills --skill i4h-workflow-setup -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install NVIDIA/skills i4h-workflow-setup --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/NVIDIA/skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/i4h-workflow-setup .agents/skills/i4h-workflow-setup && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "i4h-workflow-setup" agent skill from https://github.com/NVIDIA/skills/tree/main/skills/i4h-workflow-setup into .agents/skills/i4h-workflow-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "i4h-workflow-setup", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add NVIDIA/skills --skill i4h-workflow-setup -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install NVIDIA/skills i4h-workflow-setup --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/NVIDIA/skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/i4h-workflow-setup .cursor/skills/i4h-workflow-setup && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "i4h-workflow-setup" agent skill from https://github.com/NVIDIA/skills/tree/main/skills/i4h-workflow-setup into .cursor/skills/i4h-workflow-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "i4h-workflow-setup", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/NVIDIA/skills.git --path skills/i4h-workflow-setup

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add NVIDIA/skills --skill i4h-workflow-setup -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install NVIDIA/skills i4h-workflow-setup --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/NVIDIA/skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/i4h-workflow-setup .gemini/skills/i4h-workflow-setup && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "i4h-workflow-setup" agent skill from https://github.com/NVIDIA/skills/tree/main/skills/i4h-workflow-setup into .gemini/skills/i4h-workflow-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "i4h-workflow-setup", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install NVIDIA/skills i4h-workflow-setup

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add NVIDIA/skills --skill i4h-workflow-setup -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/NVIDIA/skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/i4h-workflow-setup .github/skills/i4h-workflow-setup && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "i4h-workflow-setup" agent skill from https://github.com/NVIDIA/skills/tree/main/skills/i4h-workflow-setup into .github/skills/i4h-workflow-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "i4h-workflow-setup", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add NVIDIA/skills --skill i4h-workflow-setup -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install NVIDIA/skills i4h-workflow-setup --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/NVIDIA/skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/i4h-workflow-setup .opencode/skills/i4h-workflow-setup && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "i4h-workflow-setup" agent skill from https://github.com/NVIDIA/skills/tree/main/skills/i4h-workflow-setup into .opencode/skills/i4h-workflow-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "i4h-workflow-setup", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: i4h-workflow-setup
GitHub stars: 3.5k
Used in: 1 other repo
Token cost: ~1k tokens
SKILL.md length: 370 words
Files: 5
Skills in repo: 380
Repo updated: Oct 7, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

Preflight and set up the root-level workflow runtime. An agent skill from NVIDIA/skills.

Works in 4 steps: Resolve the base checkout. → Run every host preflight check. → Run default full setup. → …
Missing component environments
SKILL.md covers Purpose, Instructions, Resolve the checkout and Preflight, plus 7 more sections
Calls git; reaches github.com

What it does

I4h Workflow Setup is an agent skill from NVIDIA/skills, published by the product's own GitHub organization. Preflight and set up the root-level workflow runtime. Use for installation, missing component environments, or third-party failures; do not use for rollout validation.

Its SKILL.md is about 1k 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 works with NVIDIA AI Platform. 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

Missing component environments
Third-party failures
Do not use for rollout validation

Example prompts

“/i4h-workflow-setup”

Requirements

Docker

Workflow steps

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

Resolve the base checkout.
Run every host preflight check.
Run default full setup.
Verify discovery and lint --all.

What it can do on your machine

Read from SKILL.md and the folder at commit 0e0d506. 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 Workflow Setup loads about 1k tokens when it runs. Until then it costs about 47 tokens; SKILL.md has 370 words of instructions outside code blocks.

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

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 0e0d506, republished under its Apache-2.0 licence (© NVIDIA). 370 words, ~1,008 tokens.

Download SKILL.mdSave it as .claude/skills/i4h-workflow-setup/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.

name: i4h-workflow-setup
description: Preflight and set up the root-level workflow runtime. Use for installation, missing component environments, or third-party failures; do not use for rollout validation.
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, setup, dependencies

i4h Workflow Setup

Purpose

Prepare the complete runtime, then prove dependency-light workflow discovery works.

Instructions

Resolve the base checkout.
Run every host preflight check.
Run default full setup.
Verify discovery and lint --all.

Resolve the checkout

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"

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.

Preflight

bash

uname -srm
command -v uv
command -v git
nvidia-smi
df -h .
./setup.sh --help

Require supported Linux on x86_64 or aarch64, uv, Git, network access for missing packages/assets, sufficient disk and model-cache space, and an NVIDIA driver compatible with the repository's Isaac Sim version. Read the exact current requirements from ./README.md; do not rely on remembered version numbers. Require Docker only when the requested local VLM or Cosmos service needs it.

Sync

Run the default full setup:

bash

./setup.sh

The explicit equivalent is:

bash

./setup.sh all

Use ./setup.sh clean only when the user explicitly requests a full rebuild or cleanup because it deletes generated caches, component environments, and third-party checkouts. Setup is idempotent; do not clean as a generic repair. The setup script restores pinned third-party sources and the upstream Isaac Sim skill catalog; do not copy that catalog into skills/.

Show full SKILL.md (150 more words)Show less

Verify

bash

./run.sh list
./run.sh lint --all
test -f ./third_party/IsaacSim-045ca8b/skills/SKILLS.md

Use run.sh show <workflow> --mode <mode> when the user named a workflow. These checks prove discovery and contracts without importing Isaac Sim. Use i4h-workflow-validate for an actual rollout.

Troubleshooting

On failure, report the first host, network, checkout, or uv-sync error and rerun full setup only after correcting that cause.

Prerequisites

Require supported Linux, network access, uv, Git, disk space, and a compatible NVIDIA GPU/driver for simulator use.

Limitations

Setup does not download every optional checkpoint or prove any rollout succeeds. clean is destructive to generated environments and third-party checkouts.

Examples

Set up the i4h workflow on this machine and tell me if any host requirements are missing. → preflight, run default full setup, then run discovery and lint --all.

Completion gate

Report every host check, synced target, first failing component if any, discovery/lint results, and the smallest next smoke command. Do not claim simulator or policy success from setup alone.

Files

SKILL.md and 4 other files in skills/i4h-workflow-setup of NVIDIA/skills.

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

Open the folder on GitHubat commit 0e0d506

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.

isaac-for-healthcare/i4h-workflowsskills/i4h-workflow-setup

Compare with similar skills

I4h Workflow Setup 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 Workflow Setup compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
I4h Workflow Setup this skillNVIDIA/skills	3.5k	1 repos	~1k	Automated safety check: Pass	Apache-2.0	today
LLM Torch Profiler Analysissgl-project/sglang	37k	2 repos	~6.4k	Automated safety check: Pass	Apache-2.0	today
Skill InspectorNVIDIA/SkillSpector	20k	—	~1.8k	Automated safety check: Pass	Apache-2.0	today
Embeddings via 9Routerdecolua/9router	30k	—	~604	Automated safety check: Pass	MIT	6 days ago
NEAR AI Cloud Private Inferenceinternet-court/internet-court-skill	6.4k	2 repos	~1.3k	Automated safety check: Pass	Custom licence	1 mo ago
Nemoclaw Maintainer Normalize Title TagsNVIDIA/NemoClaw	23k	—	~693	Automated safety check: Pass	Apache-2.0	today

Similar skills

LLM Torch Profiler Analysis
sgl-project/sglang
Unified LLM torch-profiler triage skill for sglang, vllm, TensorRT-LLM, and TokenSpeed.
37k GitHub starsUsed in 2 repos~6.4k tokens
DevelopmentAuto-check passed
Skill Inspector
NVIDIA/SkillSpector
Official
Decides whether an agent skill is safe to install by combining a SkillSpector static scan with the agent's own source review, ending in APPROVE, CAUTION or REJECT.
20k GitHub stars~1.8k tokensUpdated today
SecurityAuto-check passed
Embeddings via 9Router
decolua/9router
Generates vector embeddings through the 9Router /v1/embeddings endpoint, using models from providers such as OpenAI, Gemini, Mistral and Voyage for RAG and semantic search.
30k GitHub stars~604 tokensUpdated 6 days ago
AI & LLM EngineeringAuto-check passed
NEAR AI Cloud Private Inference
internet-court/internet-court-skill
Shows how to call NEAR AI Cloud through an OpenAI-compatible API and verify that inference ran in a TEE, using attestation checks and signed chat responses.
6.4k GitHub starsUsed in 2 repos~1.3k tokens
AI & LLM EngineeringAuto-check passed
Nemoclaw Maintainer Normalize Title Tags
NVIDIA/NemoClaw
Official
Remove bracketed NemoClaw tags from GitHub issue and PR titles.
23k GitHub stars~693 tokensUpdated today
Marketing & SEOAuto-check passed
Megatron-LM Container and Dependency Setup
NVIDIA/Megatron-LM
Official
Walks an agent through working inside the Megatron-LM CI container and changing dependencies with uv, so lock files resolve the same locally and in CI.
18k GitHub stars~2.6k tokensUpdated today
DevelopmentAuto-check passed

More from NVIDIA/skills

All 380 skills in this repo

Vss Deploy Detection Tracking 2D
NVIDIA/skills
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.5k GitHub starsUsed in 1 repo~4.5k tokens
Auto-check passed
HSB IP Def File Tool
NVIDIA/skills
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.5k GitHub stars~2.9k tokensUpdated today
Auto-check passed
Isaac Sim Mission Control Showcase
NVIDIA/skills
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.5k GitHub stars~4.8k tokensUpdated today
Auto-check passed
Defect Image Generation with Cosmos AnomalyGen
NVIDIA/skills
Official
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.5k GitHub stars~5k tokensUpdated today
Auto-check: notes
Physical AI Video Augmentation on OSMO
NVIDIA/skills
Official
Orchestrates video data augmentation and auto-labeling workflows on OSMO, from flow selection and preflight checks to submission, monitoring and output download.
3.5k GitHub stars~4.7k tokensUpdated today
Auto-check: notes
TAO Detection KPI Analysis
NVIDIA/skills
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.5k GitHub stars~2.7k tokensUpdated today
Auto-check: notes

Works with

NVIDIA AI Platform

Questions about I4h Workflow Setup

What does I4h Workflow Setup do?

Preflight and set up the root-level workflow runtime. An agent skill from NVIDIA/skills. I4h Workflow Setup is an agent skill from NVIDIA/skills, published by the product's own GitHub organization. Preflight and set up the root-level workflow runtime.

When should I use I4h Workflow Setup?

I4h Workflow Setup fits situations like: missing component environments; third-party failures; do not use for rollout validation.

How do I install I4h Workflow Setup in Claude Code?

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

How do I install I4h Workflow Setup in Codex?

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

Can I use I4h Workflow Setup 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-workflow-setup -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-workflow-setup, .gemini/skills/i4h-workflow-setup, .github/skills/i4h-workflow-setup and .opencode/skills/i4h-workflow-setup in your project.

What does I4h Workflow Setup need to run?

Going by SKILL.md and its folder, I4h Workflow Setup needs the command-line tools its instructions call (git). Our summary lists: Docker.

Does I4h Workflow Setup 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 Workflow Setup 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 Workflow Setup use?

I4h Workflow Setup 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 Workflow Setup use?

About 1k tokens (SKILL.md is roughly 4k 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 Workflow Setup?

Skills that share tags, products or a category with I4h Workflow Setup: LLM Torch Profiler Analysis (sgl-project/sglang, 37k stars), Skill Inspector (NVIDIA/SkillSpector, 20k stars), Embeddings via 9Router (decolua/9router, 30k stars) and NEAR AI Cloud Private Inference (internet-court/internet-court-skill, 6.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains I4h Workflow Setup?

NVIDIA (a GitHub organization, an official publisher) maintains it in NVIDIA/skills, which has 3,534 GitHub stars. The repository holds 380 skills in this directory. The repository was last updated on October 7, 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.

Install I4h Workflow Setup

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

i4h Workflow Setup

Purpose

Instructions

Resolve the checkout

Preflight

Sync

Verify

Troubleshooting

Prerequisites

Limitations

Examples

Completion gate

Files

Used in 1 other repository

Compare with similar skills

Similar skills

More from NVIDIA/skills

Related

Questions about I4h Workflow Setup