
If you're working with NVIDIA's Holoscan Sensor Bridge hardware on a devkit, this helps you discover, filter, and run example applications that match your specific setup. It checks your platform, HSB version, board type, and connected sensors, then shows you which examples will actually work. When something breaks, it analyzes the failure and suggests fixes or code edits so you can iterate without starting from scratch. The skill assumes your devkit is already configured and runs everything inside the demo container. Particularly useful if you're cycling through sensor demos and want the tooling to remember your hardware context between runs instead of re-verifying connectivity every time.
$ npx -y skills add nvidia/skills --skill hsb-app --agent claude-codeInstalls into .claude/skills of the current project.
Use this skill when the user wants to discover, select, and run Holoscan Sensor Bridge example applications on a devkit with a connected HSB board.
This skill assumes the devkit is already set up (SSH, demo container built, host configured, board connected). If setup is not complete, instruct the user to run /hsb-setup first.
This workflow runs applications inside the demo container. Only run it when the user explicitly invokes it.
Gate 1 — Read environment variables. Before doing anything else, check these variables and print their resolved values to the user:
SSH_TARGET Remote devkit login (e.g. nvidia@192.168.1.50). Ask the user if not set.
REMOTE_ROOT Remote working directory (e.g. /home/nvidia). Ask the user if not set.
REMOTE_SUDO sudo / sudo -n / "" — default to "sudo" if not set.
REMOTE_SSH_OPTS Additional SSH options (optional).
HSB_PLATFORM Platform hint (optional).
SSH_TARGET and REMOTE_ROOT are required. Stop and ask the user for them if either is missing.
Gate 2 — Present the phase plan and get confirmation. Before taking any action:
Sponsors