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.
npx skills add NVIDIA/skills --skill hsb-ip-def --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# HSB IP Def Skill ## Purpose Use this skill through four workflows: - **Generate** a `HOLOLINK_def.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 `HOLOLINK_def.svh`: `\`define` dire
What does the hsb-ip-def skill do?
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.
How do I install it?
Run `npx skills add NVIDIA/skills --skill hsb-ip-def --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From NVIDIA/skills, a repository with 2,789 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.