isaac-mission-control-showcase

Files (27)

• BENCHMARK.md
• SKILL.md
• carter_warehouse_navigation.png · assets/
• carter_warehouse_navigation.yaml · assets/
• skillspector-baseline.yaml · config/
• evals.json · evals/
• README.md · references/bring-up-cloud-stack/
• run.py · references/bring-up-cloud-stack/scripts/
• README.md · references/change-fleet-composition/
• run.py · references/change-fleet-composition/scripts/
• README.md · references/change-map/
• run.py · references/change-map/scripts/
• README.md · references/isaac-sim-installation/
• README.md · references/isaac-sim-remote/
• run.py · references/isaac-sim-remote/scripts/
• publishing-layout.md · references/
• troubleshooting.md · references/
• workflow.md · references/
• doctor.py · scripts/
• restore_isaac_scene.py · scripts/
• run.sh · scripts/
• run_state.py · scripts/
• showcase.py · scripts/
• dependency_manifest.py · shared/
• skill-card.md
• skill.oms.sig
• upstream-versions.lock.json

SKILL.md (first lines)

# Mission Control Showcase

Use the bundled runner for the default small-warehouse Nova Carter showcase.
It owns the integration and coordinates five upstream skills that it resolves
at runtime rather than vendoring. Resolve those dependencies once with
`python3 "$SKILL_DIR/scripts/doctor.py" dependencies --prepare` before the first run.

## Host swap safety

Never create, resize, enable, or remove host swap without the user's explicit
approval of the specific operation, device or file path, and size. For example,
"Create an 8 GB swap file at /swapfile" identifies all three. A general request
to run the showcase, make preflight pass, or fix a memory shortfall does not
authorize any swap change. If memory preflight fails, report the shortfall and
suggest freeing memory or using a larger host. Ask for the specific swap
approval only if the user wants that option; do not provide swap-changing
commands or perform the change before approval. Swap changes can persist after
the showcase.

## Locate bundled resources

Before running any command, set `SKILL_DIR` to the absolute path of the
directory containing this loaded `SKILL.md`, using the skill location supplied
by the skill loader. Preserve that value in each shell invocation. Do not
derive it from the current working directory or assume a source repository
layout or a fixed installation directory.

All bundled paths in this document and its references, including `scripts/`,
`references/`, `shared/`, `assets/`, `config/`, and
`upstream-versions.lock.json`, are relative to `SKILL_DIR`. Read them beneath
that directory and prefix bundled script paths with `"$SKILL_DIR/"` when
following command examples in the references. Runtime output paths and
upstream skill paths reported by the dependency manifest retain their own
locations. Commands below can run from any working directory.

## Runtime selection

Always launch Isaac Sim from a local installation through this showcase
runner, with its GUI window on the host display. Watch the robot in that
window. Drive every stage operation through the `isaac-sim-remote` Python
server on `ISAAC_PYTHON_PORT`. There is no WebRTC, browser viewer, or
containerised Isaac Sim in this workflow.

Before preflight, inspect existing state read-only. Determine the installation
path and version, whether `isaac-sim.sh` and the bundled ROS 2 bridge
libraries are present, whether a display is
available, and whether an Isaac Sim is already running. Do not launch or
import Isaac Sim, start or stop a container, run an installer, or alter files.

Treat the installed version, warehouse URI, Nova Carter asset and sensor
graphs, and readiness probes as one compatibility set. Mere presence of Isaac
Sim is not proof of compatibility.

Apply this selection policy:

- If a 6.1.0 installation is present at `ISAAC_SIM_DIR`, report the detected
  version and continue without an unnecessary prompt.
- If a different version is detected and the launcher, ROS 2 bridge, and a
  verified warehouse URI are all present, use it automatically — no prompt —
  and report the choice:

  > Isaac Sim `<version>` detected at `<path>` and is usable (launcher
  > `<ready/status>`, ROS 2 bridge `<ready/status>`). Using this installation.

  Attempt the normal preflight and readiness contract; stop and report a
  mismatch rather than modifying that installation.
- Prompt before preflight only when the version cannot be determined, or none
  of launcher, ROS 2 bridge, or a verified warehouse URI can be confirmed —
  this is the sole runtime-selection case that requires user input, because no
  automatic choice can be verified safe:

  > Isaac Sim `<version>` was detected at `<path>`. Launcher:
  > `<ready/status>`. ROS 2 bridge: `<ready/status>`. Choose whether to use
  > the detected version or select or install another version.
- Docker is still required for the Mission Control cloud stack and Nova Carter
  SIL, but never for Isaac Sim itself.
- If nothing is installed, route to the resolved `isaac-sim-installation`
  skill rather than guessing a path. Resolve it through
  `python3 "$SKILL_DIR/scripts/doctor.py" dependencies`;
  never search for it and never vendor a copy.

Never upgrade, downgrade, overwrite, delete, repair, relabel, refresh, or
otherwise modify an existing Isaac Sim installation as showcase recovery.
Obtain explicit user direction before stopping an already-running Isaac Sim.

If the user asks to install, upgrade, downgrade, or otherwise obtain a
different Isaac Sim version, stop the showcase workflow and hand off to the
resolved `isaac-sim-installation` skill. Read its runtime `SKILL.md` at the path
the dependency manifest reports, and follow its own gates without bypassing any
of them. Do not reproduce or restate its installation logic here. The runner
requires a local standalone installation, so preselect that method. Stop after
the installed path is reported; do not launch Isaac Sim. Resume runtime
selection only after that handoff has completed and the user asks to continue.
When that skill runs a compatibility check, prefer a generous
`--timeout-seconds` such as `3600`; its 600-second default often expires on a
first run that is still populating shader and asset caches.

## Default workflow

1. Check whether the user already specified a different map, robot platform,
   simulator, or mission objective in the conversation; if not, use the
   canonical default without asking. Before preflight, tell the user the exact
   warehouse URI, robot ID `carter01`, all five waypoint coordinates in order,
   route-only mission type, and mission timeout `900` seconds from
   [Canonical default](#canonical-default) and
   [Deterministic route](#deterministic-route). State that the default demo
   command `bash "$SKILL_DIR/scripts/run.sh" --demo` uses those values without
   scenario overrides. This announcement is required even if preflight later
   blocks the run.
2. Apply [Runtime selection](#runtime-selection) without changing any detected
   installation. Resolve any user choice or installation handoff, then run the
   read-only preflight:

   ```bash
   bash "$SKILL_DIR/scripts/run.sh" --preflight
   ```

3. Ask the user to stop or relocate every reported running container that is
   not explicitly permitted. Allow unrelated workloads by exact container name

From NVIDIA/skills, CC-BY-4.0 AND Apache-2.0.

More from NVIDIA/skills