i4h-workflow-create

Create new Isaac for Healthcare agentic environments by forking existing env patterns.

3.2k|370|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/NVIDIA/skills --skill i4h-workflow-create
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: i4h-workflow-create
Source: https://github.com/NVIDIA/skills/tree/main/skills/i4h-workflow-create
Command: npx skills add https://github.com/NVIDIA/skills --skill i4h-workflow-create

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Scaffolding a new agentic simulation environment in the Isaac for Healthcare (i4h) workflows repository requires coordinating five separate files (env YAML, assets, task, env class, runtime) with strict conventions, and mistakes only surface at Isaac Sim build time. This Skill guides an agent through forking the closest existing env and producing a runnable first version without inventing new architecture.

Core Features & Use Cases

  • Contract-driven scaffolding: Produces exactly the five required env surfaces (YAML config, assets, task, environment class, runtime) under workflows/agentic/ with repo-root-relative paths.
  • Pattern forking and hybrid rules: Selects the closest source env (e.g., scissor_pick_and_place, locomanip_tray_pick_and_place), resolves robot owner, policy stack (GR00T N1.5/N1.6, openpi), cameras, and success rules, including G1 hybrid layout and footprint-clearance rules.
  • Mandatory validation gate: Runs static checks (py_compile, --list-envs, dry-runs) plus a real Isaac Sim bridge build with geometry probes and viewport capture inspection before reporting the env ready.
  • Use Case: Ask the agent to create a G1 surgical tool sorting env from scissor_pick_and_place; it loads the recipe, writes the five files with seed layout values, then validates the scene in the bridge.

Quick Start

Ask your agent to create a new i4h environment for surgical tool sorting using the G1 robot based on scissor_pick_and_place.

Frequently Asked Questions about i4h-workflow-create

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a new Isaac for Healthcare agentic environment?

Fork the closest existing env by creating five files: the env YAML in config/environments, plus assets, task, environment class, and runtime modules under workflows/agentic/arena/arena. Then run static checks and a real bridge build with viewport validation before reporting the env ready.

How do I build a G1 surgical tool sorting env from scissor_pick_and_place?

Load the g1-surgical-tool-sort recipe, which resolves the env id, GR00T N1.6 policy stack, HumanoidEnvironmentBase robot owner, and seed layout values. Write the five contract files from the fast-path source reads, then validate through the bridge.

Does this skill handle scene edits or adding cameras to an existing env?

No. Scene edits, optional props, extra cameras, live bridge edits, and baking changes into source are handled by the separate i4h-workflow-scene-edit skill. This skill only creates the first runnable env shell.

Why does my new env fail even though dry-run and py_compile pass?

Static checks are shallow: they never import the asset/task modules or call get_env, so build-time errors like bad cfg kwargs or helpers defined below config classes slip through. A real bridge build via arena/run.sh ensure-bridge plus visual inspection is the mandatory gate.

What are the limitations of the i4h env creation workflow?

It creates one env per invocation, forks existing patterns rather than inventing new policy stacks, and requires a GPU host that can launch Isaac Sim for validation. If Isaac Sim cannot launch, the blocker must be reported explicitly rather than treating static checks as success.