i4h-workflow-setup
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.
Install / Use
npx skills add NVIDIA/skills --skill i4h-workflow-setupInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
AutomationSupported Platforms
Tags
Our assessment of i4h-workflow-setup
i4h-workflow-setup scores 91/100 on our quality scale, 1014th of 2,790 Automation skills we index (top 37%).
Its SKILL.md is 3.9 KB long, well organised into 12 sections with 5 code examples: a solid amount of guidance for an agent.
With 3,421 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so i4h-workflow-setup is actively maintained.
- Our last check on 2026-10-29 found the source still online.
- It is released under the Apache-2.0 license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-09-29. Automated pattern scan on 2026-09-29. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
i4h-workflow-setup compared with similar skills
All 4 of these similar skills score higher than i4h-workflow-setup; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| i4h-workflow-setup (this skill)by NVIDIA | 91 | 3.4k | 54d ago | SKILL.md |
| Agent-Reachby Panniantong | 100 | 112.3k | 8d ago | CLAUDE.md |
| rufloby ruvnet | 100 | 81.9k | today | CLAUDE.md |
| Claude-Code-Game-Studiosby Donchitos | 100 | 39.7k | 7d ago | CLAUDE.md |
| Scraplingby D4Vinci | 100 | 103.6k | 2d ago | MCP Server |
Frequently asked questions
- How do I install i4h-workflow-setup?
- Run
npx skills add NVIDIA/skills --skill i4h-workflow-setup. The install tabs above show the steps for each supported agent. - Which AI agents does i4h-workflow-setup work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is i4h-workflow-setup safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is Apache-2.0-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is i4h-workflow-setup still maintained?
- The repository was last updated about 2 months ago, so i4h-workflow-setup is actively maintained.
Skill content
View source on GitHubname: 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" version: "0.8.0" 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
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
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:
./setup.sh
The explicit equivalent is:
./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/.
Verify
./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 andlint --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.
Related Skills
Agent-Reach
112.3kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
ruflo
81.9k🌊 The original agent harness. Deploy intelligent multi-player swarms, coordinate autonomous workflows, and build conversational AI systems. Features adaptive memory, self-learning intelligence, federation, vector RAG integration, and native Claude Code / Codex / Hermes and many more Integrated
Claude-Code-Game-Studios
39.7kTurn Claude Code into a full game dev studio — 49 AI agents, 72 workflow skills, and a complete coordination system mirroring real studio hierarchy.
Scrapling
103.6k🕷️ The BEST Web Scraping framework that handles everything from a single request to a full-scale crawl! Don't be shy, join here: https://discord.gg/EMgGbDceNQ and follow here for daily tips and tricks: https://x.com/Scrapling_dev
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
