Hsb Ip Create Top

NVIDIAOfficialCreated by Holoscan TeamDistributed by NVIDIA

Skill
Workflow
Software development
Apache-2.0
Medium risk

From the author

Create or explain fixed-format HSB FPGA_top.sv wrappers from validated HOLOLINK_def.svh files. Do not use for def generation or validation.

— the description by Holoscan Team

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

This skill provides a structured workflow to generate an FPGA_top.sv scaffold, which serves as the top-level wrapper for HSB IP. It ensures that the generated code adheres to a fixed format, including necessary license headers, module shells, and signal declarations derived from a validated HOLOLINK_def.svh file. The skill is designed to work either as a standalone tool or as a follow-up to the hsb-ip-def skill, ensuring that integration scaffolds are consistent with the underlying IP configuration.

What it does

Generates a fixed-format FPGA_top.sv scaffold.
Instantiates the HOLOLINK_top module.
Declares HSB-facing signals based on validated HOLOLINK_def.svh macros.
Provides TODO comments for top-level integration points.
Supports both live HSB IP source extraction and bundled known-revision references.

When to use it

When you have a validated HOLOLINK_def.svh and need to create a top-level wrapper.
When you need to ensure your FPGA top-level structure follows established HSB integration standards.
When transitioning from IP definition to top-level system integration.

Advantages

Ensures consistent top-level structure across different HSB IP configurations.
Automates the tedious process of declaring complex HSB-facing signal groups.
Maintains strict adherence to port shapes and interface requirements.
Reduces integration errors by using validated defs as the source of truth.

Usage examples

“Create an FPGA_top.sv scaffold using my validated HOLOLINK_def.svh.”: The agent will verify the defs file, determine the appropriate port map source, and generate the fixed-format SystemVerilog scaffold.
“I just finished generating my defs with hsb-ip-def, can you create the top-level wrapper now?”: The agent will consume the existing context from the def-skill handoff and proceed directly to generating the FPGA_top.sv scaffold.

Install

Download the skill as a ZIP:
https://mp-staging.autogineer.com/agent-skills/nvidia/hsb-ip-create-top/download

Unzip it into the cross-client skills folder of your project:

mkdir -p .agents/skills && unzip hsb-ip-create-top.zip -d .agents/skills

Documentation by Holoscan Team

HSB IP Create Top Skill

Purpose

Create a fixed-format SystemVerilog top-level scaffold that instantiates HOLOLINK_top and declares the HSB-facing signals required by a validated HOLOLINK_def.svh.

This skill owns only the top-level scaffold around the HSB IP:

SPDX/Apache license header
HOLOLINK_def.svh include
FPGA_top module shell
HSB-facing signal declarations
HOLOLINK_top instantiation
comments/TODOs for top-level integration

Use hsb-ip-def for HOLOLINK_def.svh generation and validation. Do not create or validate the defs file here.

Prerequisites

A validated HOLOLINK_def.svh path or pasted file content is required before generating FPGA_top.sv.
Live HOLOLINK_top.sv source is preferred when source-sensitive port extraction is needed; bundled references cover known rev 16'h2604 and compatible rev 16'h2603.
The user must provide or accept the output path when writing a scaffold file.

Instructions

Require a validated HOLOLINK_def.svh before creating FPGA_top.sv. If the user does not have one, invoke or direct them to hsb-ip-def first.
Treat live HOLOLINK_top.sv as the source of truth for ports, directions, macro gates, and IP revision whenever it is available.
First classify the request as Standalone Create Top, Def-Skill Handoff, or Explain. Load only the references required for that workflow and do not re-read the same reference just to reconfirm formatting.
Use references/fixed-format.md as the baked formatting and naming style. Do not inspect example top-level files just to confirm formatting during normal generation.
Emit a fixed-format scaffold, not a complete project top. Because the surrounding design is unknown, the generated FPGA_top module normally has no top-level ports.
Derive active signal groups from the validated defs file. Do not connect ports that are absent from HOLOLINK_top under the active macro set.
Preserve HOLOLINK_top port shapes exactly: keep packed vector widths before the signal name and unpacked interface-array dimensions after the signal name.
When using bundled known-rev references, still preserve the signal shapes in references/fixed-format.md, including unpacked arrays for multi-interface *_tdata, *_tkeep, and *_tuser buses and the APB shape documented there.
Use sensor-agnostic language. Say "sensor data", "sensor interface", and "stream"; use camera-specific language only after the user says the design is camera-specific.
Ask one plain-language question per turn when information is missing. Keep source-selection questions as plain-language prompts rather than radio buttons, structured choices, or multi-question prompts.
Do not invent project-specific integration details. Leave concise TODO comments where the surrounding design must connect to HSB.
For packetizer comments in FPGA_top.sv, use generic wording such as "data manipulation behavior".
In final summaries, include the defs validation/source status, the port-map source used, and the emitted HSB signal groups. Do not enumerate what is outside the scaffold's scope. Use only this generic note: "This file is a reference/template for hooking up top-level signals and companion IP to the HSB IP."

Live HSB IP Source Policy

Prefer live HSB IP source over bundled references whenever the user's workspace provides it. The bundled references describe known rev 16'h2604 and backward-compatible rev 16'h2603; live source is the authority for the checked-out IP.

When source is available:

Locate <hsb-ip-root>/top/HOLOLINK_top.sv. Known roots include hw/nvcpu_dgx_fpga/vrtl/hololink/ and public-release fpga/nv_hsb_ip/.
Read HOLOLINK_REV and HOLOLINK_BACKWARD_COMPAT_REV from HOLOLINK_top.sv.
Read the HOLOLINK_top module declaration to confirm port names, directions, widths, ordering, and ifdef/ifndef gates.
If the rev is newer, unknown, or the live source disagrees with this skill's references, state the mismatch. Trust the live source for IO extraction and warn that bundled references may need an update.

When no source is available, use the bundled references as known-revision guidance and say the scaffold is based on the skill's supported HSB IP rev. If the user already authorized using the bundled known-rev port reference when no checkout is obvious, do a brief search of obvious roots and then proceed with bundled references instead of asking the live-source question.

If the source root is not obvious, ask conversationally in one turn:

Do you have a current HSB IP `HOLOLINK_top.sv` source checkout you want me to use for port extraction, or should I use the skill's bundled known-rev port reference?

Accept either a path or a "use bundled reference" answer.

Reference Loading

Load only the reference needed for the user's task:

File	When to load
`references/source-policy.md`	Finding live HSB IP source, handling unknown revisions, or deciding source/reference precedence
`references/fixed-format.md`	Generating or explaining the fixed `FPGA_top.sv` scaffold format
`references/handoff-contract.md`	Standalone prerequisite handling or def-skill handoff behavior

Workflow Decision

If invoked by hsb-ip-def after a successful defs generation/validation, use Def-Skill Handoff.
If the user directly asks to create FPGA_top.sv, instantiate HOLOLINK_top, or make a top-level wrapper, use Standalone Create Top.
If the user asks about version handling, port groups, or why a signal appears, use Explain.

Standalone Create Top

Use this when the user invokes this skill directly.

Steps:

Ask for the path to a validated HOLOLINK_def.svh, or accept pasted content. If the user does not have a defs file, stop and direct them to hsb-ip-def to create and validate it first.
If validation status is unknown, invoke or direct the user to hsb-ip-def validation. Do not proceed from an unvalidated defs file.
If the HSB IP source root is not obvious and source-sensitive output is needed, ask the live-source question from "Live HSB IP Source Policy" unless the user already authorized bundled known-rev fallback. Do not show path options as radio buttons. The known roots are search hints for the agent, not choices to force on the user.
Load references/source-policy.md and references/fixed-format.md.
Derive the active macro set from the validated defs file.
Derive or verify HOLOLINK_top port groups from live source when available.
Produce FPGA_top.sv in the fixed format. If writing a file, default filename is FPGA_top.sv unless the user provides a path.
Explain that the result is an HSB integration scaffold. Use the generic reference/template note in ## Instructions; do not enumerate what is outside the scaffold's scope.

Def-Skill Handoff

Use this when hsb-ip-def has just completed a validated HOLOLINK_def.svh and the user chooses to create a matching top-level scaffold.

Steps:

Accept the validated defs file path/content and any known profile/source-root context from hsb-ip-def.
Do not re-ask for defs-file decisions already completed by the def skill.
Ask only for missing top-generation facts, such as output path or HSB IP source root when needed. If source root is missing, ask the live-source question from "Live HSB IP Source Policy" unless the user already authorized bundled known-rev fallback; do not use radio buttons or structured choices.
Load references/handoff-contract.md and references/fixed-format.md.
Generate the fixed-format FPGA_top.sv scaffold from the active defs macros and live HOLOLINK_top.sv when available.
Return a concise summary of which HSB signal groups were emitted, then use the generic reference/template note in ## Instructions. Do not enumerate what is outside the scaffold's scope.

Explain

Use this when the user asks why a port or signal group appears, how macro settings affect the top scaffold, or how the skill handles IP revisions.

Steps:

For port questions, prefer live HOLOLINK_top.sv when available. Otherwise load references/fixed-format.md.
For revision/source questions, load references/source-policy.md.
For defs-file macro meaning, defer to hsb-ip-def.

Troubleshooting

Missing or unvalidated defs file: stop before generation and send the user to hsb-ip-def validation.
Unknown or newer HSB IP revision: prefer live source if available, state the mismatch, and warn that bundled references may need updates.
Port missing under the active macro set: omit that connection and explain which validated def macro disabled the signal group.

Examples

Use hsb-ip-create-top to create an FPGA_top.sv scaffold from my validated HOLOLINK_def.svh. Use the bundled known-rev port reference if no HSB IP source checkout is obvious. Treat as Standalone Create Top, require the validated defs file, load references/source-policy.md and references/fixed-format.md, use bundled known-rev ports after a brief source search, and report the defs status, port-map source, and emitted signal groups.
Create a top-level FPGA_top.sv wrapper for HSB, but I do not have a HOLOLINK_def.svh yet. Stop before generation, direct the user to hsb-ip-def, and ask for a validated defs file path or content before proceeding.
Why does the generated FPGA_top.sv include different HSB signal groups depending on my HOLOLINK_def.svh macros? Treat as Explain, say that validated defs macros gate the HSB-facing signal groups and that the live HOLOLINK_top.sv port map wins when available; defer detailed macro semantics to hsb-ip-def.

Limitations

Do not generate HOLOLINK_def.svh.
Do not validate full HOLOLINK_def.svh files.
Do not generate project-specific integration outside the HSB-facing scaffold.
Do not infer signal meanings, polarity, sources, or behavior outside the HSB port map.
Do not copy example project logic into the scaffold unless the user explicitly requests project-specific adaptation.

Files

ATTRIBUTION.mdAdded by AutoGineer916 B
BENCHMARK.md3.4 KiB
LICENSELicence file added by AutoGineer11.2 KiB
SKILL.md10.7 KiB
evals/evals.json3.4 KiB
references/fixed-format.md7.3 KiB
references/handoff-contract.md1.6 KiB
references/source-policy.md2.5 KiB
skill-card.md3.8 KiB
skill.oms.sig5.2 KiB

LICENSE

Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved.


                                 Apache License
                           Version 2.0, January 2004
                        http://www.apache.org/licenses/

   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION

   1. Definitions.

      "License" shall mean the terms and conditions for use, reproduction,
      and distribution as defined by Sections 1 through 9 of this document.

      "Licensor" shall mean the copyright owner or entity authorized by
      the copyright owner that is granting the License.

      "Legal Entity" shall mean the union of the acting entity and all
      other entities that control, are controlled by, or are under common
      control with that entity. For the purposes of this definition,
      "control" means (i) the power, direct or indirect, to cause the
      direction or management of such entity, whether by contract or
      otherwise, or (ii) ownership of fifty percent (50%) or more of the
      outstanding shares, or (iii) beneficial ownership of such entity.

      "You" (or "Your") shall mean an individual or Legal Entity
      exercising permissions granted by this License.

      "Source" form shall mean the preferred form for making modifications,
      including but not limited to software source code, documentation
      source, and configuration files.

      "Object" form shall mean any form resulting from mechanical
      transformation or translation of a Source form, including but
      not limited to compiled object code, generated documentation,
      and conversions to other media types.

      "Work" shall mean the work of authorship, whether in Source or
      Object form, made available under the License, as indicated by a
      copyright notice that is included in or attached to the work
      (an example is provided in the Appendix below).

      "Derivative Works" shall mean any work, whether in Source or Object
      form, that is based on (or derived from) the Work and for which the
      editorial revisions, annotations, elaborations, or other modifications
      represent, as a whole, an original work of authorship. For the purposes
      of this License, Derivative Works shall not include works that remain
      separable from, or merely link (or bind by name) to the interfaces of,
      the Work and Derivative Works thereof.

      "Contribution" shall mean any work of authorship, including
      the original version of the Work and any modifications or additions
      to that Work or Derivative Works thereof, that is intentionally
      submitted to Licensor for inclusion in the Work by the copyright owner
      or by an individual or Legal Entity authorized to submit on behalf of
      the copyright owner. For the purposes of this definition, "submitted"
      means any form of electronic, verbal, or written communication sent
      to the Licensor or its representatives, including but not limited to
      communication on electronic mailing lists, source code control systems,
      and issue tracking systems that are managed by, or on behalf of, the
      Licensor for the purpose of discussing and improving the Work, but
      excluding communication that is conspicuously marked or otherwise
      designated in writing by the copyright owner as "Not a Contribution."

      "Contributor" shall mean Licensor and any individual or Legal Entity
      on behalf of whom a Contribution has been received by Licensor and
      subsequently incorporated within the Work.

   2. Grant of Copyright License. Subject to the terms and conditions of
      this License, each Contributor hereby grants to You a perpetual,
      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
      copyright license to reproduce, prepare Derivative Works of,
      publicly display, publicly perform, sublicense, and distribute the
      Work and such Derivative Works in Source or Object form.

   3. Grant of Patent License. Subject to the terms and conditions of
      this License, each Contributor hereby grants to You a perpetual,
      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
      (except as stated in this section) patent license to make, have made,
      use, offer to sell, sell, import, and otherwise transfer the Work,
      where such license applies only to those patent claims licensable
      by such Contributor that are necessarily infringed by their
      Contribution(s) alone or by combination of their Contribution(s)
      with the Work to which such Contribution(s) was submitted. If You
      institute patent litigation against any entity (including a
      cross-claim or counterclaim in a lawsuit) alleging that the Work
      or a Contribution incorporated within the Work constitutes direct
      or contributory patent infringement, then any patent licenses
      granted to You under this License for that Work shall terminate
      as of the date such litigation is filed.

   4. Redistribution. You may reproduce and distribute copies of the
      Work or Derivative Works thereof in any medium, with or without
      modifications, and in Source or Object form, provided that You
      meet the following conditions:

      (a) You must give any other recipients of the Work or
          Derivative Works a copy of this License; and

      (b) You must cause any modified files to carry prominent notices
          stating that You changed the files; and

      (c) You must retain, in the Source form of any Derivative Works
          that You distribute, all copyright, patent, trademark, and
          attribution notices from the Source form of the Work,
          excluding those notices that do not pertain to any part of
          the Derivative Works; and

      (d) If the Work includes a "NOTICE" text file as part of its
          distribution, then any Derivative Works that You distribute must
          include a readable copy of the attribution notices contained
          within such NOTICE file, excluding those notices that do not
          pertain to any part of the Derivative Works, in at least one
          of the following places: within a NOTICE text file distributed
          as part of the Derivative Works; within the Source form or
          documentation, if provided along with the Derivative Works; or,
          within a display generated by the Derivative Works, if and
          wherever such third-party notices normally appear. The contents
          of the NOTICE file are for informational purposes only and
          do not modify the License. You may add Your own attribution
          notices within Derivative Works that You distribute, alongside
          or as an addendum to the NOTICE text from the Work, provided
          that such additional attribution notices cannot be construed
          as modifying the License.

      You may add Your own copyright statement to Your modifications and
      may provide additional or different license terms and conditions
      for use, reproduction, or distribution of Your modifications, or
      for any such Derivative Works as a whole, provided Your use,
      reproduction, and distribution of the Work otherwise complies with
      the conditions stated in this License.

   5. Submission of Contributions. Unless You explicitly state otherwise,
      any Contribution intentionally submitted for inclusion in the Work
      by You to the Licensor shall be under the terms and conditions of
      this License, without any additional terms or conditions.
      Notwithstanding the above, nothing herein shall supersede or modify
      the terms of any separate license agreement you may have executed
      with Licensor regarding such Contributions.

   6. Trademarks. This License does not grant permission to use the trade
      names, trademarks, service marks, or product names of the Licensor,
      except as required for reasonable and customary use in describing the
      origin of the Work and reproducing the content of the NOTICE file.

   7. Disclaimer of Warranty. Unless required by applicable law or
      agreed to in writing, Licensor provides the Work (and each
      Contributor provides its Contributions) on an "AS IS" BASIS,
      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
      implied, including, without limitation, any warranties or conditions
      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
      PARTICULAR PURPOSE. You are solely responsible for determining the
      appropriateness of using or redistributing the Work and assume any
      risks associated with Your exercise of permissions under this License.

   8. Limitation of Liability. In no event and under no legal theory,
      whether in tort (including negligence), contract, or otherwise,
      unless required by applicable law (such as deliberate and grossly
      negligent acts) or agreed to in writing, shall any Contributor be
      liable to You for damages, including any direct, indirect, special,
      incidental, or consequential damages of any character arising as a
      result of this License or out of the use or inability to use the
      Work (including but not limited to damages for loss of goodwill,
      work stoppage, computer failure or malfunction, or any and all
      other commercial damages or losses), even if such Contributor
      has been advised of the possibility of such damages.

   9. Accepting Warranty or Additional Liability. While redistributing
      the Work or Derivative Works thereof, You may choose to offer,
      and charge a fee for, acceptance of support, warranty, indemnity,
      or other liability obligations and/or rights consistent with this
      License. However, in accepting such obligations, You may act only
      on Your own behalf and on Your sole responsibility, not on behalf
      of any other Contributor, and only if You agree to indemnify,
      defend, and hold each Contributor harmless for any liability
      incurred by, or claims asserted against, such Contributor by reason
      of your accepting any such warranty or additional liability.

   END OF TERMS AND CONDITIONS

   APPENDIX: How to apply the Apache License to your work.

      To apply the Apache License to your work, attach the following
      boilerplate notice, with the fields enclosed by brackets "[]"
      replaced with your own identifying information. (Don't include
      the brackets!)  The text should be enclosed in the appropriate
      comment syntax for the file format. We also recommend that a
      file or class name and description of purpose be included on the
      same "printed page" as the copyright notice for easier
      identification within third-party archives.

   Copyright [yyyy] [name of copyright owner]

   Licensed under the Apache License, Version 2.0 (the "License");
   you may not use this file except in compliance with the License.
   You may obtain a copy of the License at

       http://www.apache.org/licenses/LICENSE-2.0

   Unless required by applicable law or agreed to in writing, software
   distributed under the License is distributed on an "AS IS" BASIS,
   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
   See the License for the specific language governing permissions and
   limitations under the License.

Requirements and compatibility

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

The author says: Targets HSB IP rev 16'h2604; backward-compatible with 16'h2603. Prefer live HSB IP source when available; warn on unknown revisions. Designed to work standalone or as a companion to hsb-ip-def.

Security

What our scanner noticed· Medium risk

Large base64-encoded blobs

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Created by

Holoscan Team

Publisher

NVIDIA (Official)

Distributed by

NVIDIA

Source

NVIDIA/skills · skills/hsb-ip-create-top · commit fce3cca

Licence

Apache License 2.0 (redistribution allowed)

LICENSE (added by AutoGineer from LICENSE-APACHE)
ATTRIBUTION.md (written by AutoGineer)

Synced

2026-11-08

AutoGineer is not affiliated with or endorsed by Holoscan Team or NVIDIA.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download hsb-ip-create-top.zip

From the author

AutoGineer summary

What it does

When to use it

Advantages

Usage examples

Install

Documentation by Holoscan Team

HSB IP Create Top Skill

Purpose

Prerequisites

Instructions

Live HSB IP Source Policy

Reference Loading

Workflow Decision

Standalone Create Top

Def-Skill Handoff

Explain

Troubleshooting

Examples

Limitations

Files

LICENSE

Requirements and compatibility

Security

Attribution and licence

Related skills

Setup TS Deep Modules

To Spec

Improve Codebase Architecture

Domain Modeling

Codebase Design

Prototype

Download ZIP