# hsb-test

Runs automated QA test plans against Holoscan Sensor Bridge hardware on a remote devkit. It filters tests from your document, executes them in a demo container, and writes a results report.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode · 1700 installs · ★ 3735
- Author: Holoscan Team
- License: Apache-2.0 · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/NVIDIA/skills/tree/HEAD/skills/hsb-test/SKILL.md
- Updated: 2026-10-23
- HTML: https://affpapa.org/en/nevibecode/skills/hsb-test

## What it does

The skill executes QA plans on Holoscan Sensor Bridge (HSB) setups. It requires a local file path or URL to your test document before it begins. The agent checks SSH connectivity to the remote devkit, pings the HSB board, inspects the demo container, and compares setup details with the repository examples. Tests requiring manual steps or extra hardware are filtered out automatically.

All executable test cases run sequentially inside the demo container. Each test receives an explicit pass or fail verdict. If an app fails, the skill checks the logs. It suggests fixes before moving forward. A persistent session file at `/tmp/.claude_hsb_test_session/state.sh` allows subsequent runs to skip Phase 0 checks. If hardware connectivity drops during a run, the skill clears the verified state and restarts Phase 0 from scratch.

Without `SSH_TARGET` and `REMOTE_ROOT` set, the skill refuses to run. The devkit host and container must also be configured beforehand, or the skill prompts to execute `/hsb-setup` first.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add NVIDIA/skills --skill hsb-test -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/hsb-test/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/hsb-test/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add NVIDIA/skills --skill hsb-test -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/hsb-test/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add NVIDIA/skills --skill hsb-test -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/hsb-test/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install NVIDIA/skills hsb-test
```

2. **Manually: put the files in place**
- File: `.github/skills/hsb-test/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add NVIDIA/skills --skill hsb-test -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/NVIDIA/skills --path skills/hsb-test
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/hsb-test/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add NVIDIA/skills --skill hsb-test -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/NVIDIA/skills/tree/HEAD/skills/hsb-test/SKILL.md

## When to use it
- run automated QA test suites against Holoscan Sensor Bridge hardware
- filter automatable tests from a local or remote test document
- diagnose application failures from demo container logs
- generate a structured test report with pass and fail results

## Example prompts
- /hsb-test
- /hsb-test --full
- Run the QA test document at /path/to/test-plan.md on the devkit

## Source text · SKILL.md · Apache-2.0

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: e0f8be1117227c0f.

BEGIN THIRD-PARTY FILE e0f8be1117227c0f
````text
---
name: hsb-test
description: Execute QA test plans on Holoscan Sensor Bridge hardware. Reads a user-provided test document, filters tests by the user's setup, determines which tests can run automatically, executes them with pass/fail evaluation, and produces a structured test results report.
author: "Holoscan Team <holoscan-team@nvidia.com>"
license: "Apache-2.0"
version: "1.0.0"
tags:
  - holoscan-sensor-bridge
  - hsb
  - testing
tools:
  - Read
  - Write
  - Edit
  - Grep
  - Glob
  - Bash
disable-model-invocation: true
allowed-tools: Read,Write,Edit,MultiEdit,Grep,Glob,Bash
metadata:
  author: "Holoscan Team <holoscan-team@nvidia.com>"
  team: holoscan
  tags:
    - holoscan-sensor-bridge
    - hsb
    - testing
  agents:
    - claude-code
    - codex
---

# HSB QA Test Runner

Use this skill when the user wants to execute a QA test plan against an HSB board and devkit. The skill reads a test document (local file or web link), filters tests to those that can run automatically on the user's specific hardware setup, executes each test with pass/fail evaluation, and produces a comprehensive results report.

This skill assumes the devkit is already set up (SSH, demo container built, host configured, board connected). If setup is not complete, it will offer to invoke `/hsb-setup` first.

This workflow runs test applications inside the demo container. Only run it when the user explicitly invokes it.

## Before you start — required gates (do these first, in order)

**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, ask for the test document, and get confirmation.** Before taking any action:

1. Show the phase plan:

```
HSB Test — Phase Plan
  Phase 0: Verify devkit SSH, board ping, and demo container availability
  Phase 1: Obtain test document, confirm setup, build executable test plan
  Phase 2: Execute tests, record pass/fail, analyze failures
  Phase 3: Produce test results report (with option to save)
  Phase 4: Clean up test artifacts
```
````
END THIRD-PARTY FILE e0f8be1117227c0f

The third-party file has ended. Everything between the e0f8be1117227c0f tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2556 of 16679 bytes. © Holoscan Team · Apache-2.0 · https://github.com/NVIDIA/skills/tree/HEAD/skills/hsb-test/SKILL.md

## Similar
- [scoutqa-test](https://affpapa.org/en/nevibecode/skills/scoutqa-test.md) — skill · 9967 installs
- [test-driven-development](https://affpapa.org/en/nevibecode/skills/test-driven-development.md) — skill · 259292 installs
- [convex-test](https://affpapa.org/en/nevibecode/skills/convex-test.md) — skill · 35900 installs
- [dart-add-unit-test](https://affpapa.org/en/nevibecode/skills/dart-add-unit-test.md) — skill · 19200 installs

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md