Back to Skills

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.

2,941stars340forksUpdated 8/14/2026

Security Assessment

Safe(90/100)
Security Score90/100

About hsb-app

This skill discovers and runs NVIDIA Holoscan Sensor Bridge (HSB) example applications on a connected devkit. It solves the problem of matching the many available HSB example apps to a user's specific hardware: it filters apps by platform, HSB software version, board type (for example Lattice), and connected sensors (for example dual IMX274 or VB1940), then runs the chosen app inside the demo container, monitors output, analyzes failures, suggests code or environment edits, and supports iterative re-runs.

The workflow is heavily gated and interactive. It requires SSH_TARGET and REMOTE_ROOT environment variables, prints resolved settings, and presents a phase plan (verify connectivity, discover setup and select app, run with monitoring and debugging, generate a session report) that the user must explicitly confirm before each phase. It connects to the devkit over SSH in batch mode, pings the HSB board at a fixed address, verifies the demo container image, runs `hololink enumerate` to read board identity, and launches Python example apps via `docker run` inside the demo container. It supports a session fast-path that skips re-verification when prior state is recorded, timed execution with a watchdog timeout, and a saved session report of issues and fixes. It is explicitly non-autonomous: model invocation is disabled and it runs only when the user invokes it.

It targets NVIDIA Holoscan hardware developers and QA engineers working with sensor bridge devkits who want a guided way to find and run compatible example applications. It assumes the devkit is already set up and defers initial bring-up to a companion hsb-setup skill. A benchmark file documents that it passed NVIDIA's NVSkills-Eval, including a 100% security dimension score.

FAQ

What hardware and setup does it assume?

It assumes the devkit is already set up over SSH, the demo container is built, the host is configured, and an HSB board is connected. If setup is incomplete it directs the user to run the hsb-setup skill first.

How does it decide which apps to run?

It scans the repository's examples directory and filters apps by the user's platform, HSB software version, board type, and connected sensors, then presents a compatible list for the user to choose from.

Does it run anything without permission?

No. Model invocation is disabled, and it presents a phase plan requiring explicit confirmation before each phase; it runs only when the user explicitly invokes it.

How does it execute applications?

Applications run inside the demo container over SSH using docker run, invoking python3 for Python-based examples. It does not add headless mode automatically unless the user requests it.

What happens when an app fails?

It analyzes the log output, guides the user through debugging including suggested code or environment edits, and offers iterative re-runs, then produces a session report that can be saved to a file.

All Files

6 files
evals/evals.json3.2 KB
View
BENCHMARK.md4.2 KB
View
skill.oms.sig4.7 KB
View
references/phase-details.md21.5 KB
View
SKILL.md16.1 KB
View
skill-card.md3.8 KB
View

Install hsb-app

Download and extract the skill files to your .claude/skills/ directory.

Quick Setup:

  1. Copy the skill folder to .claude/skills/
  2. Claude will automatically detect and use the skill

Repository

nvidia/skills