Menu

Individual skill

i4h-workflow-create

0upvotes

Create a minimal blank Workflow scaffold with a Scene containing ground and light plus an idle run mode. Use for fast new Workflow scaffolding.

skills/i4h-workflow-create/SKILL.md

Read pinned source

Source commit fce3cca4170be75e82c64920654d56ee2811b005

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
3,913
Repository last updated
Nov 6, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Create a Blank i4h Workflow

## Purpose

Create a complete runnable blank Workflow without searching for an existing Workflow or booting Isaac Sim.

## Instructions

1. Resolve the checkout using `I4H_WORKFLOWS` when set; otherwise use the current git root. If neither contains `workflows/i4h_workflows`, use the checkout resolver from the repository `AGENTS.md`.
2. Choose a lowercase snake_case Workflow id.
3. Select exactly one approved product specialty: `laparoscopic-robotics`, `ultrasound-robotics`, `endoluminal-robotics`, or `hospital-automation-robotics`.
4. 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.
Back to top