SkillAgentSearch skills...

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-setup

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

91/100

Category

Automation

Supported Platforms

Universal

Tags

Our assessment of i4h-workflow-setup

i4h-workflow-setup scores 91/100 on our quality scale, 782nd of 2,125 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.

Substance
26/30
Structure
20/20
Description
15/15
Adoption
15/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated 5 days ago, so i4h-workflow-setup is actively maintained.
  • 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.

i4h-workflow-setup compared with similar skills

All 4 of these similar skills score higher than i4h-workflow-setup; compare them before choosing.

SkillScoreStarsUpdatedFormat
i4h-workflow-setup (this skill)by NVIDIA913.4k5d agoSKILL.md
Agent-Reachby Panniantong10086.0k13d agoCLAUDE.md
rufloby ruvnet10073.4ktodayCLAUDE.md
Scraplingby D4Vinci10084.4ktodayMCP Server
algorithmic-artby anthropics100177.9k6d agoSKILL.md

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?
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 5 days ago, so i4h-workflow-setup is actively maintained.

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" 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

  1. Resolve the base checkout.
  2. Run every host preflight check.
  3. Run default full setup.
  4. 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 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.

Related Skills

View on GitHub
GitHub Stars3.4k
CategoryAutomation
Updated5d ago
Forks412

Languages

Python

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions