Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →nvidia/hsb-app
Discover and run Holoscan Sensor Bridge example applications on a connected devkit. Filters available apps by the user's platform, HSB software version, board type, and sensors. Supports timed execution, failure analysis, code-edit suggestions, and iterative re-runs.
Passed 20 of 23 test cases with the skill, and 4 of 23 without it.
and 15 more in the full report
17 fixed3 passed either way2 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 17 test cases the skill fixed. Same model, same prompt, with and without the skill.
If `HSB_REPO_DIR` is not set by the user before running the application workflow, what default directory name under `REMOTE_ROOT` will be used for scanning repository examples?
| Checked | Without skill | With skill |
|---|---|---|
| Fall back to holoscan-sensor-bridge as the default repository directory name. | Missed | Passed |
The instructions your model reads when the skill loads.
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. [email protected]). 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:
If the user's request already includes platform, board type, and sensors, also state upfront:
examples/ and filter apps by the user's sensor type and platform--headless automatically — only if the user explicitly requests itdocker run, using python3 for Python-based examplesShow the phase plan:
HSB App — Phase Plan
Phase 0: Verify board connectivity and demo container readiness
Phase 1: Discover user setup and select application to run
Phase 2: Run application with monitoring, failure analysis, and iterative debugging
Phase 3: Generate session report (with option to save)
test cases passed, vs 4 / 23 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.