Holoscan Sensor Bridge App Runner
Find, run, and debug HSB examples on a connected development kit.
The skill requires explicit invocation, phase confirmations, confirmation before code edits, and describes SSH, Docker, device mappings, and cleanup. However, it permits Bash, configurable sudo, privileged containers, host networking, /dev mounts, xhost, and remote writes; it also prints resolved environment variables. Least privilege, sensitive-value protection, complete data-flow disclosure, and robust rollback are incomplete, so points are deducted.
The phased workflow, watchdog, log summaries, failure taxonomy, re-verification, and container cleanup are useful. However, this is a static review with no committed tests covering key paths, and heredoc handling, variable interpolation, remote paths, and container prerequisites remain unverified assumptions. The score stays within the static-review ceiling.
The audience, hardware variants, sensor filtering, explicit invocation, and platform constraints are clearly described. Chinese interaction and mainland-China reachability are not documented, and the workflow depends on a preconfigured remote devkit, SSH, Docker, GPU runtime, and physical hardware; boundary evidence is therefore limited.
The skill has frontmatter, an Apache-2.0 declaration, version 1.0.0, author information, linked phase documentation, help text, and invocation examples. It lacks dedicated Instructions, Examples, and Purpose sections; the benchmark also identifies missing prerequisite documentation. There is no changelog, and maintenance ownership and update path are only indirectly supported by repository-level material.
The workflow covers discovery, filtering, execution, failure analysis, iteration, and reporting, and the attached benchmark reports practical evaluation results. Static review cannot verify actual outputs, hardware compatibility, or repair success, and results still depend on the user's environment and choices, so the score remains within the static ceiling.
The fixed revision, concrete commands, evaluation tasks, benchmark metrics, and phase procedures provide some auditability. However, there is no verifiable CI or committed key-path test suite, and the benchmark is an attached report rather than independently corroborated execution evidence; cross-source verification is limited.
- Execution involves remote SSH, privileged Docker, host networking, /dev mounts, GPU access, and display permissions; manually verify the target host, image, devices, and command scope before running.
- Resolved environment values may contain sensitive SSH options or path information and should not be displayed or copied into reports without filtering.
- Container stopping and session teardown use broad name filters and remote rm -rf; confirm that targets are limited to resources created by this workflow and retain an external recovery path.
- Core functionality depends on a configured NVIDIA/HSB devkit, physical hardware, Docker runtime, and local networking; Chinese-language interaction and mainland-China availability are not demonstrated.
What does this skill do, and when should you use it?
hsb-app is for a Holoscan Sensor Bridge development kit that has already been configured. It discovers example applications and filters them by platform, HSB software version, board type, and connected sensors. Selected applications run inside the demo Docker container, with timed execution, failure analysis, edit suggestions, and iterative reruns. The workflow requires explicit invocation and begins by verifying the remote kit, board, FPGA identity, and container readiness over SSH.
Reads and displays SSH_TARGET, REMOTE_ROOT, REMOTE_SUDO, REMOTE_SSH_OPTS, and HSB_PLATFORM; uses SSH to check cached session state, kit reachability, HSB board responsiveness, FPGA version, board identity, and demo-container readiness; reads the user guide and examples/ to filter applications for the user's platform, HSB version, board, and sensors; runs the selected application in the Docker demo container, using python3 for Python examples; monitors output, analyzes failures, suggests code or environment edits, and supports reruns; generates a session report and offers to save it.
- An HSB developer with a connected board needs to select an example compatible with the current platform and sensors.
- A hardware engineer wants to verify remote-kit connectivity, board identity, FPGA version, and demo-container readiness before running an application.
- An application developer wants log-based failure analysis, suggested edits, and a retry workflow after an HSB example fails.
- A test engineer needs to run an example for a defined number of seconds and receive a report of issues, fixes, and outcome.
What are this skill's strengths and limitations?
- Covers remote verification, hardware identification, application selection, execution, debugging, cleanup, and reporting.
- Filters examples by platform, HSB version, board type, and sensors before selection.
- Supports watchdog timeouts, failure summaries, edit suggestions, and iterative reruns.
- Its metadata names both Claude Code and Codex and uses broadly available shell, filesystem, and text-search tools.
- Requires a preconfigured devkit, connected HSB board, SSH access, Docker demo container, and host setup.
- Depends on remote SSH, Docker, and specific hardware, so it is not a standalone local example runner.
- It uses Claude Code-oriented invocation controls, slash-command arguments, and session-state paths; other clients need adaptation.
- The supplied material provides no test-coverage or standalone benchmark evidence for this skill.
How do you install this skill?
Install only this skill through the Skills CLI documented in the repository README:
npx skills add nvidia/skills --skill hsb-app --yes
To target Codex explicitly:
npx skills add nvidia/skills --skill hsb-app --agent codex
The supplied material does not specify a manual-copy destination. The skill declares Apache-2.0. The repository README states that the repository is dual-licensed under Apache 2.0 and CC BY 4.0, while the supplied repository metadata says NOASSERTION.
How do you use this skill?
Prepare the devkit with SSH, the demo container, host configuration, and a connected HSB board. Set SSH_TARGET and REMOTE_ROOT; if setup is incomplete, run /hsb-setup first. Then invoke the skill explicitly:
/hsb-app
Supported options include /hsb-app --timeout 60, /hsb-app --verbose, /hsb-app --full, and /hsb-app --help. The first run requires confirmation of Phase 0, and the normal workflow asks for confirmation between phases. If SSH_TARGET or REMOTE_ROOT is missing, the skill asks the user to provide it.