hsb-ip-def

Generate, validate, and compare HOLOLINK_def.svh configuration headers for NVIDIA Holoscan Sensor Bridge FPGA IP.

3.2k|370|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/NVIDIA/skills --skill hsb-ip-def
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hsb-ip-def
Source: https://github.com/NVIDIA/skills/tree/main/skills/hsb-ip-def
Command: npx skills add https://github.com/NVIDIA/skills --skill hsb-ip-def

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires PyYAML, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

Writing a correct HOLOLINK_def.svh configuration header for the NVIDIA Holoscan Sensor Bridge (HSB) FPGA IP requires knowing dozens of macros, their legal values, and cross-macro constraints. This Skill removes hand-editing errors by generating, validating, comparing, and explaining def files with bundled Python tooling and authoritative macro references.

Core Features & Use Cases

  • Guided Generation: Build a HOLOLINK_def.svh from confirmed board requirements via a one-question-per-turn workflow, or directly from a YAML/JSON profile; the generator validates before writing output.
  • Rule-Based Validation: Lint an existing def file against a catalog of stable rule IDs (HD-Exxx/Wxxx/Ixxx) with JSON or text output, including HD-W3xx silent-fallback footgun warnings.
  • Semantic Comparison: Diff two def files while ignoring whitespace, comments, and equivalent syntactic forms.
  • Use Case: An FPGA engineer bringing up a new HSB board answers questions about sensor interfaces, host width, clocks, and peripherals, then receives a validated HOLOLINK_def.svh targeting IP rev 16'h2604.

Quick Start

Ask your agent to use hsb-ip-def to generate a HOLOLINK_def.svh for your new HSB board, or to validate your existing def file and explain any warnings.

Frequently Asked Questions about hsb-ip-def

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a HOLOLINK_def.svh for a new HSB board?

Ask the agent to generate a HOLOLINK_def.svh and it will run the Generate workflow: script preflight, then one requirements question per turn covering sensors, host interfaces, clocks, and peripherals. It builds a YAML profile and runs scripts/generate_def.py, which validates before writing the output file.

How do I validate an existing HOLOLINK_def.svh file?

Provide the file path or paste its content, and the agent runs scripts/validate_def.py with JSON output. Findings are grouped by severity with rule IDs and line numbers, and HD-W3xx silent-fallback warnings are always surfaced even when no errors exist.

What are the requirements to run the hsb-ip-def scripts?

The bundled scripts require Python 3.9 or newer, and PyYAML is needed when the generator reads YAML profiles. The skill runs a preflight check once per session and stops with a clear message if Python or PyYAML is missing.

Which HSB IP versions does this skill support?

The skill targets HSB IP revision 16'h2604 and is backward-compatible with 16'h2603, the public release revision. When live HSB IP source is available, it supersedes the bundled references, and you can pass --ip-source to the validator.

Can this skill generate the FPGA_top.sv top-level wrapper?

No, generating FPGA_top.sv is explicitly out of scope. After a def file is generated and validated, the skill offers a handoff to the separate hsb-ip-create-top skill, which owns the top-level wrapper scaffold.

How do I compare two HOLOLINK_def.svh configuration files?

Run scripts/compare_defs.py with the two file paths to get a semantic diff. It ignores whitespace, comments, and equivalent syntactic forms, reporting differences in scalar defines, arrays, init_reg entries, and wrapper structure as JSON or text.