Nx Generate
nomcopter/react-mosaic
Generate code using nx generators. An agent skill from nomcopter/react-mosaic.
Create a minimal blank Workflow scaffold with a Scene containing ground and light plus an idle run mode.
Install I4h Workflow Create
$ npx skills add NVIDIA/skills --skill i4h-workflow-create -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install NVIDIA/skills i4h-workflow-create --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/NVIDIA/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/i4h-workflow-create .claude/skills/i4h-workflow-create && rm -rf skills-srcUse ~/.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/
Install the "i4h-workflow-create" agent skill from https://github.com/NVIDIA/skills/tree/main/skills/i4h-workflow-create into .claude/skills/i4h-workflow-create/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "i4h-workflow-create", 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 install https://github.com/NVIDIA/skills/tree/main/skills/i4h-workflow-createType 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.
$ npx skills add NVIDIA/skills --skill i4h-workflow-create -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install NVIDIA/skills i4h-workflow-create --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/NVIDIA/skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/i4h-workflow-create .agents/skills/i4h-workflow-create && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "i4h-workflow-create" agent skill from https://github.com/NVIDIA/skills/tree/main/skills/i4h-workflow-create into .agents/skills/i4h-workflow-create/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "i4h-workflow-create", 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.
$ npx skills add NVIDIA/skills --skill i4h-workflow-create -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install NVIDIA/skills i4h-workflow-create --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/NVIDIA/skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/i4h-workflow-create .cursor/skills/i4h-workflow-create && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "i4h-workflow-create" agent skill from https://github.com/NVIDIA/skills/tree/main/skills/i4h-workflow-create into .cursor/skills/i4h-workflow-create/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "i4h-workflow-create", 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 https://github.com/NVIDIA/skills.git --path skills/i4h-workflow-create--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add NVIDIA/skills --skill i4h-workflow-create -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install NVIDIA/skills i4h-workflow-create --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/NVIDIA/skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/i4h-workflow-create .gemini/skills/i4h-workflow-create && rm -rf skills-srcUse ~/.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/
Install the "i4h-workflow-create" agent skill from https://github.com/NVIDIA/skills/tree/main/skills/i4h-workflow-create into .gemini/skills/i4h-workflow-create/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "i4h-workflow-create", 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.
$ gh skill install NVIDIA/skills i4h-workflow-createInstalls 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).
$ npx skills add NVIDIA/skills --skill i4h-workflow-create -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/NVIDIA/skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/i4h-workflow-create .github/skills/i4h-workflow-create && rm -rf skills-srcUse ~/.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/
Install the "i4h-workflow-create" agent skill from https://github.com/NVIDIA/skills/tree/main/skills/i4h-workflow-create into .github/skills/i4h-workflow-create/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "i4h-workflow-create", 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.
$ npx skills add NVIDIA/skills --skill i4h-workflow-create -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install NVIDIA/skills i4h-workflow-create --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/NVIDIA/skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/i4h-workflow-create .opencode/skills/i4h-workflow-create && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "i4h-workflow-create" agent skill from https://github.com/NVIDIA/skills/tree/main/skills/i4h-workflow-create into .opencode/skills/i4h-workflow-create/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "i4h-workflow-create", 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-create- GitHub stars
- 3.5k
- Used in
- 1 other repo
- Token cost
- ~1.5k tokens
- SKILL.md length
- 686 words
- Files
- 5
- Skills in repo
- 380
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Create a minimal blank Workflow scaffold with a Scene containing ground and light plus an idle run mode.
- Works in 4 steps: Resolve the checkout using I4H_WORKFLOWS… → Choose a lowercase snake_case Workflow id. → Select exactly one approved product… → …
- Fast new Workflow scaffolding
- SKILL.md covers Purpose, Instructions, Utility and Validate, plus 6 more sections
- Calls python, git and make
What it does
I4h Workflow Create is an agent skill from NVIDIA/skills, published by the product's own GitHub organization. Create a minimal blank Workflow scaffold with a Scene containing ground and light plus an idle run mode. Use for fast new Workflow scaffolding.
Its SKILL.md is about 1.5k 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 Development, covering Project scaffolding. 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
- Fast new Workflow scaffolding
- Tasks that involve Project scaffolding
Example prompts
- “/i4h-workflow-create”
Requirements
- Python 3
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Resolve the checkout using I4H_WORKFLOWS when set; otherwise use the current git root. If neither contains workflows/i4h_workflows, use…
- Choose a lowercase snake_case Workflow id.
- Select exactly one approved product specialty: laparoscopic-robotics, ultrasound-robotics, endoluminal-robotics, or…
- Generate the blank Workflow and run the static validation below.
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:
pythongitmake
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
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 Create loads about 1.5k tokens when it runs. Until then it costs about 41 tokens; SKILL.md has 686 words of instructions outside code blocks.
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). 686 words, ~1,531 tokens.
Download SKILL.mdSave it as
.claude/skills/i4h-workflow-create/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- i4h-workflow-create
- description
- Create a minimal blank Workflow scaffold with a Scene containing ground and light plus an idle run mode. Use for fast new Workflow scaffolding.
- 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, isaac-sim, workflow-authoring
Create a Blank i4h Workflow
Purpose
Create a complete runnable blank Workflow without searching for an existing Workflow or booting Isaac Sim.
Instructions
- Resolve the checkout using
I4H_WORKFLOWSwhen set; otherwise use the current git root. If neither containsworkflows/i4h_workflows, use the checkout resolver from the repositoryAGENTS.md. - Choose a lowercase snake_case Workflow id.
- Select exactly one approved product specialty:
laparoscopic-robotics,ultrasound-robotics,endoluminal-robotics, orhospital-automation-robotics. - Generate the blank Workflow and run the static validation below.
If the request does not identify a specialty, ask the user to choose one; do not infer a product category from the workflow name alone.
Run:
./scripts/create_blank_environment.py <workflow_id> --specialty <specialty>This is the only authoring utility that generates workflow-specific source. It rejects an existing public workflow id in any specialty before dry-run output or file creation. It writes the fixed empty templates that establish the design boundary; later scene and task code is written by the coding agent. Use --dry-run to preview its output, --description TEXT to customize the scene-manifest description, and --validate to run the focused static checks after creation. Do not combine --dry-run and --validate.
The script refuses to overwrite files and creates only:
./
├── arena/i4h_arena/assets/<workflow_id>.py
├── arena/i4h_arena/scenes/<workflow_id>.py
├── arena/i4h_arena/scenes/manifest/<workflow_id>.yaml
├── workflows/i4h_workflows/<specialty>/<workflow_id>.py
└── workflows/tests/test_<workflow_id>_contract.pyThe result contains a ground plane, dome light, no embodiment or declared robots, no task-specific objects or cameras, and one idle mode. Its contract test verifies durable Workflow and manifest invariants rather than asserting that the Scene stays blank, so later Scene, Task, and run-mode authoring does not require rewriting the test. Do not inspect robot assets, choose a policy, create Task manifests, load upstream Isaac Sim skills, or launch the simulator during blank creation.
Utility
| Command | Purpose | Arguments |
|---|---|---|
./scripts/create_blank_environment.py | Create the complete overwrite-safe blank Workflow | <workflow_id> --specialty <specialty> [--description TEXT] [--dry-run] [--validate] |
Validate
Run only fast static checks:
./scripts/create_blank_environment.py <workflow_id> --specialty <specialty> --validateWhen the Workflow already exists because it was created without --validate, run the equivalent checks directly:
cd "$(git rev-parse --show-toplevel)"
./run.sh show <workflow_id> --mode idle
./run.sh lint <workflow_id> --mode idle
./run.sh lint --all
workflows/.venv/bin/python -m pytest workflows/tests/test_<workflow_id>_contract.py -q
arena/.venv/bin/python -m pytest arena/tests/test_scene.py -q--validate requires the workflow and Arena environments; run ./setup.sh first if either is missing. It verifies the generated contract and the shared zero-DOF blank-scene runtime adapter without launching Isaac Sim. If a component virtual environment is elsewhere, use that component's Python for its direct test command. Do not run visible or dynamic validation unless the user explicitly requests it.
Troubleshooting
- If the checkout cannot be resolved, set
I4H_WORKFLOWSto the existing repository root or use the resolver inAGENTS.md. - If generation reports that the workflow id already exists, report its specialty source and ask whether to edit it or use a different id; never overwrite, relocate, or duplicate it.
- If
--validatereports a missing component environment, run./setup.shand repeat the same validation.
Show full SKILL.md (257 more words)Show less
Prerequisites
Require a writable root-level i4h-workflows checkout and Python 3.11 or newer. Static --validate also requires the workflow and Arena component environments.
Limitations
This skill creates only the five-file idle scaffold. It does not add an embodiment, task behavior, policy, cameras, or task-specific assets, and it does not visibly validate the Scene.
Continue
Treat creation as the first stage of an incremental workflow:
- Create the blank Workflow scaffold with this skill: blank Scene, scene manifest, and idle-only Workflow.
- Use
i4h-workflow-scene-editto add and visibly verify assets, robots, cameras, layout, and physics, then bake the confirmed Scene. - Define behavior only after the user provides a concrete goal and success condition. Reuse compatible Tasks; create a focused Task only when the behavior is new. Do not create an empty placeholder Task.
- Add rule-based, teleop, replay, or policy modes only when requested and only when their Task and action contracts are runnable.
- Validate every newly enabled mode with the owning stage skill.
The blank Workflow is intentionally useful before behavior exists: its shared idle Task opens the Scene for authoring, so a blank task manifest or implementation would add no capability.
Examples
Create a blank hospital-automation-robotics workflow named my_workflow.→ generatemy_workflowin the hospital automation specialty and run static validation.Make a new laparoscopic-robotics workflow called training_sandbox as fast as possible. Start blank.→ generate the same five-file idle-only scaffold undertraining_sandboxin the laparoscopic specialty.
Completion gate
Report the created id, five files, idle-only status, and static validation results. Do not commit unless explicitly asked.
© 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-workflow-create 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.
Compare with similar skills
I4h Workflow Create 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| I4h Workflow Create this skillNVIDIA/skills | 3.5k | 1 repos | ~1.5k | Automated safety check: Pass | Apache-2.0 | |
| Nx Generatenomcopter/react-mosaic | 4.8k | 6 repos | ~1.9k | Automated safety check: Pass | Custom licence | |
| PonytailDavidObando/gsharp | 564 | 8 repos | ~1.7k | Automated safety check: Pass | MIT | |
| Run Nx Generatornrwl/nx | 29k | 2 repos | ~592 | Automated safety check: Notes | MIT | |
| Conductor Setupgemini-cli-extensions/conductor | 3.8k | — | ~4.2k | Automated safety check: Pass | Apache-2.0 | |
| Mirage VFS Adapter Authoringstrukto-ai/mirage | 3.7k | — | ~2.4k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Ponytail
DavidObando/gsharp
Forces the laziest solution that actually works, simplest, shortest, most minimal.
Run Nx Generator
nrwl/nx
Run Nx generators with prioritization for workspace-plugin generators.
Conductor Setup
gemini-cli-extensions/conductor
Scaffolds the project and sets up the Conductor environment.
Mirage VFS Adapter Authoring
strukto-ai/mirage
Builds or extends a custom Mirage virtual filesystem adapter for an API, database, object store or app data, with a working mount configuration and filesystem tests.
Siteboon Backend Module Standards
siteboon/claudecodeui
Enforces this repository's TypeScript backend module architecture under server/: feature folders, barrel exports, and where shared types and utilities belong.
More from NVIDIA/skills
All 380 skills in this repo- Official
Vss Deploy Detection Tracking 2D
NVIDIA/skills
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.
- Official
HSB IP Def File Tool
NVIDIA/skills
Generates, validates, compares and explains HOLOLINK_def.svh macro files for the HSB IP, using bundled Python scripts and asking before it writes anything.
- Official
Isaac Sim Mission Control Showcase
NVIDIA/skills
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.
- Official
Defect Image Generation with Cosmos AnomalyGen
NVIDIA/skills
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.
- Official
Physical AI Video Augmentation on OSMO
NVIDIA/skills
Orchestrates video data augmentation and auto-labeling workflows on OSMO, from flow selection and preflight checks to submission, monitoring and output download.
- Official
TAO Detection KPI Analysis
NVIDIA/skills
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.
Related
Categories
Questions about I4h Workflow Create
What does I4h Workflow Create do?
Create a minimal blank Workflow scaffold with a Scene containing ground and light plus an idle run mode. I4h Workflow Create is an agent skill from NVIDIA/skills, published by the product's own GitHub organization. Create a minimal blank Workflow scaffold with a Scene containing ground and light plus an idle run mode.
When should I use I4h Workflow Create?
I4h Workflow Create fits situations like: fast new Workflow scaffolding; tasks that involve Project scaffolding.
How do I install I4h Workflow Create in Claude Code?
Run `npx skills add NVIDIA/skills --skill i4h-workflow-create -a claude-code`. Or copy the skill folder (skills/i4h-workflow-create in NVIDIA/skills) into .claude/skills/i4h-workflow-create in your project. Claude Code loads it when a task matches its description.
How do I install I4h Workflow Create in Codex?
Run `npx skills add NVIDIA/skills --skill i4h-workflow-create -a codex`. Or copy the skill folder (skills/i4h-workflow-create in NVIDIA/skills) into .agents/skills/i4h-workflow-create in your project. Codex loads it when a task matches its description.
Can I use I4h Workflow Create 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-create -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-create, .gemini/skills/i4h-workflow-create, .github/skills/i4h-workflow-create and .opencode/skills/i4h-workflow-create in your project.
What does I4h Workflow Create need to run?
Going by SKILL.md and its folder, I4h Workflow Create needs the command-line tools its instructions call (python, git and make). Our summary lists: Python 3.
Does I4h Workflow Create access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is I4h Workflow Create 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 Create use?
I4h Workflow Create 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 Create use?
About 1.5k tokens (SKILL.md is roughly 6.1k 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 Create?
Skills that share tags, products or a category with I4h Workflow Create: Nx Generate (nomcopter/react-mosaic, 4.8k stars), Ponytail (DavidObando/gsharp, 564 stars), Run Nx Generator (nrwl/nx, 29k stars) and Conductor Setup (gemini-cli-extensions/conductor, 3.8k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains I4h Workflow Create?
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.