Agent skill · NVIDIA
i4h-workflow-scene-edit
Edit an existing workflow Scene or task contract. Use for assets, layout, cameras, randomization, task text, or success rules; do not use to create a new workflow.
What it needs
About 9k tokens when loaded.
What this skill does
Edit an i4h Workflow Scene Purpose Iterate on an existing Scene in one live simulator session, and persist the confirmed state only when explicitly asked to bake, save, or persist. Instructions 1. Run the checkout resolver and inspect target ownership. 2. Start or reuse one bridge-backed live-authoring session by default and capture a visible baseline. 3. Read the minimal upstream guidance and apply each requested edit as its own observable live-stage transaction without changing source. 4. On an explicit bake/save/persist instruction, export the accumulated live state, inspect its resolved authoring facts, and have the coding agent edit the smallest owning sources. 5. Keep the session running for further prompts until the user explicitly says stop or exit. 6. Run static, persisted-visible, and affected dynamic validation when baking. Resolve and inspect Treat the resolver above as part of the skill contract: a hosted copy may run outside the base repository, so never assume the current checkout contains workflows/i4hworkflows. I4HWORKFLOWSREPOURL selects the clone source. When I4HWORKFLOWS is unset, derive the fallback directory from that URL; set I4HWORKFLOWS only to reuse or choose a specific destination. Never replace an existing checkout. Read DESIGN.md, the target workflow, Scene Python, scene manifest, embodiment manifest, and relevant task manifests. Use $ROOT/skills/i4h-workflow/references/repo-map.md to resolve ownership. For a G1 face, walk, reach, or collision-sensitive success contract, read references/g1-reach-and-contact.md. Reuse its Tasks and Scene-owned footprint interface; do not generate workflow-specific locomotion helpers or hardcode object extents in the Workflow. An open/run request without an edit means ./run.sh <workflow> --idle; do not invent source changes. An edit-scene request always means start or reuse ./run.sh <workflow> --live unless the user explicitly requests offline/no-live operation. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills NVIDIA/i4h-workflow-scene-edit