Index of every page on this site: llms.txt
All skills
nvidia avatar

/holoscan-setup

@6b75e9e
by NVIDIA Corporationnvidia/skills4.1k stars
547
Run it yourself

Assess a host and choose a Holoscan SDK 5.x installation method using release availability, CUDA 13 compatibility, and component needs.

Use this Skill: https://skilld.dev/gh/nvidia/skills/holoscan-setup

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈38 tokens for metadata: the name and description. ≈1k when used: this file. ≈4.5k more on demand in 3 files.

Description uses 1.9% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈152 characters, or 1.9%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Holoscan 5.x Setup

Establish the target

Determine the requested 5.x release or source branch and whether the user needs C++, Python, specific modules, or SDK development. Read the release notes and SDK installation guide with the matching 5.x version selected. An unversioned page may describe 4.x; for a development checkout use its docs/sdk_installation.mdx and DEVELOP.md. Treat Early Access binary methods as tentative until the exact artifacts are confirmed published. Package-name registration alone is not availability.

Inspect and assess

Use read-only checks on the intended Linux host:

uname -m
cat /etc/os-release
nvidia-smi
python3 --version
getconf GNU_LIBC_VERSION
docker --version
docker info

Report unavailable tools separately from incompatible hardware. Inspect an existing venv or SDK checkout only at user-selected or relevant known paths. Use python -m pip list in the intended environment and dpkg-query -W 'holoscan*' on Debian systems to distinguish 4.x installations from usable 5.x ones. A GPU passthrough check that runs/pulls an image is a separate execution step; a Docker version check alone does not establish passthrough.

The 5.0 baseline is CUDA 13 with dGPU support, Ubuntu 24.04 native packages, and x86_64/SBSA arm64. Wheels require glibc 2.39 and regular CPython 3.12–3.14. The nvidia-smi CUDA value describes driver capability, not toolkit presence. Check driver/runtime compatibility for the selected artifact; a CUDA 12-only host cannot be routed to a nonexistent 5.x CUDA 12 package. ARM64 does not establish Tegra/iGPU support. Confirm hardware-specific support before offering installation on Jetson, IGX, DGX Spark, or Grace systems.

To check an already-pulled image, run the bundled helper from this skill's installation directory with the full confirmed 5.x tag, for example:

bash scripts/check_ngc_image.sh v5.0.0-cuda13

It inspects the local image only, makes no registry request, and does not prove publication, GPU passthrough, or runtime success. Report its result accordingly.

Recommend and route

Present the relevant choices with separate publication and host-readiness status:

Method 5.x workflow
Development container Published CUDA 13 multiarch image; full C++ and Python stack under /usr
Debian Published Ubuntu 24.04 C++ holoscan metapackage or Core/optional modules
Python wheels Published holoscan metapackage or CUDA 13 component wheels in a venv
Source Explicit 5.x ref; build container and checkout-specific options
Conda Unavailable for 5.0; check the selected release's documentation for later 5.x support

Recommend source when the requested Early Access binaries are unavailable. Recommend the development container for a ready-to-use environment when the image and host support are confirmed; native C++ and Python needs can justify Debian or wheels. If the user already selected a supported method, honor that choice and proceed within their authorization. Otherwise ask one concise method-selection question before installation.

Use the corresponding holoscan-install-container, holoscan-install-debian, holoscan-install-wheel, or holoscan-install-source skill when available. Pass the release/source ref, host architecture, driver/runtime status, selected components, existing installation details, and verified artifact availability. If a companion skill is unavailable, consult the release instructions directly. For a Conda-specific request, holoscan-install-conda explains the limitation and alternatives; installing the 4.x Conda package does not meet a 5.x request.

Report the outcome

Report the selected SDK version/ref, method, component versions, and checks actually executed. Separate availability checks, imports, graph execution, and module/GPU qualification. Missing binaries should produce an actionable source alternative; missing host support should produce the prerequisite to resolve.

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts29d3 checks · Risk SAFE
  • Gen Agent Trust Hub29d

    This skill is safe and provides instructions for assessing a host and selecting an NVIDIA Holoscan SDK 5.x installation method. It uses standard, read-only system commands and a local helper script to verify environment compatibility and image presence.

  • Socket1mo

    No alerts

  • Snyk1mo

    Risk: LOW · No issues

Signed by skilld at 6b75e9e. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated last month
Other metadata
metadata
{
  "author": "Holoscan Team <holoscan-team@nvidia.com>",
  "version": "2.0.0",
  "github-url": "https://github.com/nvidia-holoscan/holoscan-sdk",
  "tags": [
    "holoscan",
    "installation",
    "setup"
  ]
}

README badge

README badge for nvidia/skills/holoscan-setup