Agent skill · NVIDIA
hsb-ip-def
Generate, validate, compare, or explain HSB HOLOLINK_def.svh macros. Do not use for FPGA_top.sv wrappers or packetizer-only derivation. Generation runs bundled Python scripts locally through shell commands and writes validated .svh output files after user-confirmed paths.
What it needs
About 6k tokens when loaded.
What this skill does
HSB IP Def Skill Purpose Use this skill through four workflows: Generate a HOLOLINKdef.svh from confirmed board requirements. Validate an existing def file with the bundled validator. Explain / Reason about HSB IP macros, legality, and macro-driven ports. Compare two def files semantically. Scope This skill owns the contents of HOLOLINKdef.svh: \define directives, localparam arrays, the HOLOLINKpkg wrapper, and boot-time initreg[] sequence. The surrounding top-level wrapper is owned by hsb-ip-create-top; packetizer-only profile derivation can be delegated to hsb-ip-packetizer. The file must use the standard guard plus package HOLOLINKpkg wrapper. Load references/macro-reference.md for the full wrapper requirement and per-macro semantics. Prerequisites Python 3.9+ is required for the bundled scripts; PyYAML is required when reading YAML profiles. The user must confirm file writes and shell commands unless they already asked for that exact operation. A concrete def file path, pasted content, or confirmed generation profile is required before script-backed validation or generation. Live HSB IP source is optional but preferred when validating against a specific checked-out IP revision. Instructions Run bundled script preflight from references/script-usage.md before Generate, Validate, Compare, or script-backed legality checks. Never silently default a macro during Generate. Show the proposed value or inferred requirement and get user confirmation. Ask one requirements question per turn during chat-driven Generate. Use sensor-agnostic language unless the user says the design is camera-specific. Avoid unsupported "typical", "common", "most designs", or corpus-frequency claims. Anchor choices to IP behavior, documented constraints, or user requirements. Always surface HD-W3xx footgun warnings, even when the user asks only about errors. Do not generate FPGAtop.sv; offer handoff to hsb-ip-create-top after a generated def file is validated. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills NVIDIA/hsb-ip-def