/holoscan-install-conda
Install Holoscan SDK v4.3+ via Conda in a CUDA 13 environment. Use for Conda installs; redirect CUDA 12 hosts to container/wheel.
$ npx -y skills add NVIDIA/skills --skill holoscan-install-conda --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/holoscan-install-conda
Context preview
The summary Claude sees to decide when to auto-load this skill.
Install Holoscan SDK v4.3+ via Conda in a CUDA 13 environment. Use for Conda installs; redirect CUDA 12 hosts to container/wheel.
SKILL.md
holoscan-install-conda.SKILL.mdname: holoscan-install-conda
version: "1.0.0"
description: "Install Holoscan SDK v4.3+ via Conda in a CUDA 13 environment. Use for Conda installs; redirect CUDA 12 hosts to container/wheel."
license: Apache-2.0
metadata:
author: "Holoscan Team <holoscan-team@nvidia.com>"
github-url: "https://github.com/nvidia-holoscan/holoscan-sdk"
tags:
- holoscan
- install
- conda
- cudaHoloscan Conda Installation
Purpose
Install the Holoscan SDK (Python runtime and/or C++ dev headers) into a Conda environment on Linux x86_64, using conda-forge + rapidsai with a correctly pinned CUDA metapackage.
Prerequisites
- Linux x86_64 with an NVIDIA GPU and CUDA 13 driver (check `nvidia-smi`).
- `conda` (Miniforge preferred). Step 1 installs it if missing.
- Network access to conda-forge, rapidsai, and `docs.nvidia.com`.
Limitations
- **CUDA 13 only** (since v4.3.0 — earlier releases were CUDA 12). If the user has a CUDA 12 driver, redirect to `/holoscan-install-container` or `/holoscan-install-wheel` instead.
- Linux x86_64 only — no aarch64/iGPU support on conda-forge.
- `ulimit -s 32768` is recommended in every shell that runs Holoscan — without it, some apps **may** segfault.
Step 0: Consult the Official Install Instructions
Always fetch the current Conda section of `https://docs.nvidia.com/holoscan/sdk-user-guide/sdk_installation.html` before installing — package names, channel selection, and the runtime/dev split can change between releases. Specifically extract:
- The exact runtime package name (e.g. `holoscan` for Python bindings).
- The C++ dev package name and whether the user needs it. As of v4.1.0, `libholoscan-dev` is a separate package containing headers and CMake config — install it whenever the user wants to develop C++ apps. Without it, `find_package(holoscan)` fails and there are no headers to `#include`.
- Supported Python versions for the current release (3.10–3.13 for v4.3).
- The current `cuda-version` pin (v4.3 → `13`).
`rmm` and `ucxx` are distributed via the `rapidsai` channel; `holoscan`, `libholoscan`, and `libholoscan-dev` come from `conda-forge`.
If the doc disagrees with anything below, the doc wins — update the install commands accordingly and tell the user.
Step 1: Prerequisites Check
conda --version 2>&1
nvidia-smi 2>&1 | head -5
If `conda` is not found, install Miniforge silently (preferred over Miniconda for conda-forge):
wget -q https://github.com/conda-forge/miniforge/releases/latest/download/Miniforge3-Linux-x86_64.sh -O /tmp/Miniforge3.sh
bash /tmp/Miniforge3.sh -b -p ~/miniforge3
source ~/miniforge3/etc/profile.d/conda.sh
conda --version
The `-b` flag installs non-interactively without modifying `.bashrc`. Users must `source ~/miniforge3/etc/profile.d/conda.sh` in each new shell (or add it to their shell RC file) to make `conda` available.
Step 2: Create Environment and Install
Package roles
- `libholoscan` — C++ runtime symbols (`libholoscan_core.so`). Auto-pulled as a dependency.
- `holoscan` — Python bindings.
- `libholoscan-dev` — C++ headers, `libholoscan_core.so` symlink, and `holoscan-config.cmake` for `find_package(holoscan)`.
- `rmm` — RAPIDS Memory Manager (rapidsai channel). Undeclared runtime dep of `holoscan`; `import holoscan` fails without it.
- `ucxx` — UCX Python bindings (rapidsai channel), needed for distributed/multi-process apps.
- `cuda-version=13` — pins the CUDA 13 metapackage so the solver picks compatible CUDA runtime libs.
Create the environment first:
source ~/miniforge3/etc/profile.d/conda.sh # if conda not yet on PATH
conda create -n holoscan python=3.13 -y
conda activate holoscan
Then pick one of the variants below based on the user's goal.
Pick the packages for the user's goal — Python-only needs `holoscan`, C++ dev needs `libholoscan-dev`, both works for combined use:
conda install <packages> rmm ucxx cuda-version=13 -c rapidsai -c conda-forge -y
For C++ development, also install the toolchain:
conda install -c conda-forge cxx-compiler cmake ninja -y
Verify Python installs with `python3 -c "import holoscan; print(holoscan.__version__)"`. Verify C++ dev installs with `ls "$CONDA_PREFIX/include/holoscan"`.
Step 3: Run Python Tests
`ulimit -s 32768` is recommended — without it, some Holoscan apps may segfault on startup.
`video_replayer` is a display app that loops forever by default. Always patch its YAML to stop after 10 frames (`count: 10`, `repeat: false`, `realtime: false`) and to run headless (`headless: true`) — headless works with or without a display attached and avoids GUI failure modes over SSH, so we don't branch on `$DISPLAY`.
Download scripts and YAML configs, patch the YAML, then run:
source ~/miniforge3/etc/profile.d/conda.sh
conda activate holoscan
ulimit -s 32768
SDK_VER=$(python3 -c "import holoscan; print(holoscan.__version__)")
BASE="https://raw.githubusercontent.com/nvidia-holoscan/holoscan-sdk/v${SDK_VER}/examples"
curl -fsSL "${BASE}/hello_world/python/hello_world.py" -o /tmp/hs_hello_world.py
curl -fsSL "${BASE}/video_replayer/python/video_replayer.py" -o /tmp/hs_video_replayer.py
curl -fsSL "${BASE}/video_replayer/python/video_replayer.yaml" -o /tmp/video_replayer.yaml
# Patch video_replayer.yaml — 10 frames, headless.
python3 -c "
c = open('/tmp/video_replayer.yaml').read()
c = c.replace('count: 0', 'count: 10')
c = c.replace('repeat: true', 'repeat: false')
c = c.replace('realtime: true', 'realtime: false')
c = c.replace(' width: 854', ' headless: true\n width: 854')
open('/tmp/video_replayer.yaml', 'w').write(c)"
# hello_world — no display, no data needed; expected: "Hello World!"
python3 /tmp/hs_hello_world.py
# video_replayer — needs racerx data; expected: frames rendered, "Graph execution finished."
HOLOSCAN_INPUT_PATH=/path/to/holoscan/data python3 /tmp/hs_video_replayer.py`HOLOSCAN_INPUT_PATH` must point to the directory contain
Read more
name: holoscan-install-conda
version: "1.0.0"
description: "Install Holoscan SDK v4.3+ via Conda in a CUDA 13 environment. Use for Conda installs; redirect CUDA 12 hosts to container/wheel."
license: Apache-2.0
metadata:
author: "Holoscan Team <holoscan-team@nvidia.com>"
github-url: "https://github.com/nvidia-holoscan/holoscan-sdk"
tags:
- holoscan
- install
- conda
- cudaHoloscan Conda Installation
Purpose
Install the Holoscan SDK (Python runtime and/or C++ dev headers) into a Conda environment on Linux x86_64, using conda-forge + rapidsai with a correctly pinned CUDA metapackage.
Prerequisites
- Linux x86_64 with an NVIDIA GPU and CUDA 13 driver (check `nvidia-smi`).
- `conda` (Miniforge preferred). Step 1 installs it if missing.
- Network access to conda-forge, rapidsai, and `docs.nvidia.com`.
Limitations
- **CUDA 13 only** (since v4.3.0 — earlier releases were CUDA 12). If the user has a CUDA 12 driver, redirect to `/holoscan-install-container` or `/holoscan-install-wheel` instead.
- Linux x86_64 only — no aarch64/iGPU support on conda-forge.
- `ulimit -s 32768` is recommended in every shell that runs Holoscan — without it, some apps **may** segfault.
Step 0: Consult the Official Install Instructions
Always fetch the current Conda section of `https://docs.nvidia.com/holoscan/sdk-user-guide/sdk_installation.html` before installing — package names, channel selection, and the runtime/dev split can change between releases. Specifically extract:
- The exact runtime package name (e.g. `holoscan` for Python bindings).
- The C++ dev package name and whether the user needs it. As of v4.1.0, `libholoscan-dev` is a separate package containing headers and CMake config — install it whenever the user wants to develop C++ apps. Without it, `find_package(holoscan)` fails and there are no headers to `#include`.
- Supported Python versions for the current release (3.10–3.13 for v4.3).
- The current `cuda-version` pin (v4.3 → `13`).
`rmm` and `ucxx` are distributed via the `rapidsai` channel; `holoscan`, `libholoscan`, and `libholoscan-dev` come from `conda-forge`.
If the doc disagrees with anything below, the doc wins — update the install commands accordingly and tell the user.
Step 1: Prerequisites Check
conda --version 2>&1 nvidia-smi 2>&1 | head -5
If `conda` is not found, install Miniforge silently (preferred over Miniconda for conda-forge):
wget -q https://github.com/conda-forge/miniforge/releases/latest/download/Miniforge3-Linux-x86_64.sh -O /tmp/Miniforge3.sh bash /tmp/Miniforge3.sh -b -p ~/miniforge3 source ~/miniforge3/etc/profile.d/conda.sh conda --version
The `-b` flag installs non-interactively without modifying `.bashrc`. Users must `source ~/miniforge3/etc/profile.d/conda.sh` in each new shell (or add it to their shell RC file) to make `conda` available.
Step 2: Create Environment and Install
Package roles
- `libholoscan` — C++ runtime symbols (`libholoscan_core.so`). Auto-pulled as a dependency.
- `holoscan` — Python bindings.
- `libholoscan-dev` — C++ headers, `libholoscan_core.so` symlink, and `holoscan-config.cmake` for `find_package(holoscan)`.
- `rmm` — RAPIDS Memory Manager (rapidsai channel). Undeclared runtime dep of `holoscan`; `import holoscan` fails without it.
- `ucxx` — UCX Python bindings (rapidsai channel), needed for distributed/multi-process apps.
- `cuda-version=13` — pins the CUDA 13 metapackage so the solver picks compatible CUDA runtime libs.
Create the environment first:
source ~/miniforge3/etc/profile.d/conda.sh # if conda not yet on PATH conda create -n holoscan python=3.13 -y conda activate holoscan
Then pick one of the variants below based on the user's goal.
Pick the packages for the user's goal — Python-only needs `holoscan`, C++ dev needs `libholoscan-dev`, both works for combined use:
conda install <packages> rmm ucxx cuda-version=13 -c rapidsai -c conda-forge -y
For C++ development, also install the toolchain:
conda install -c conda-forge cxx-compiler cmake ninja -y
Verify Python installs with `python3 -c "import holoscan; print(holoscan.__version__)"`. Verify C++ dev installs with `ls "$CONDA_PREFIX/include/holoscan"`.
Step 3: Run Python Tests
`ulimit -s 32768` is recommended — without it, some Holoscan apps may segfault on startup.
`video_replayer` is a display app that loops forever by default. Always patch its YAML to stop after 10 frames (`count: 10`, `repeat: false`, `realtime: false`) and to run headless (`headless: true`) — headless works with or without a display attached and avoids GUI failure modes over SSH, so we don't branch on `$DISPLAY`.
Download scripts and YAML configs, patch the YAML, then run:
source ~/miniforge3/etc/profile.d/conda.sh
conda activate holoscan
ulimit -s 32768
SDK_VER=$(python3 -c "import holoscan; print(holoscan.__version__)")
BASE="https://raw.githubusercontent.com/nvidia-holoscan/holoscan-sdk/v${SDK_VER}/examples"
curl -fsSL "${BASE}/hello_world/python/hello_world.py" -o /tmp/hs_hello_world.py
curl -fsSL "${BASE}/video_replayer/python/video_replayer.py" -o /tmp/hs_video_replayer.py
curl -fsSL "${BASE}/video_replayer/python/video_replayer.yaml" -o /tmp/video_replayer.yaml
# Patch video_replayer.yaml — 10 frames, headless.
python3 -c "
c = open('/tmp/video_replayer.yaml').read()
c = c.replace('count: 0', 'count: 10')
c = c.replace('repeat: true', 'repeat: false')
c = c.replace('realtime: true', 'realtime: false')
c = c.replace(' width: 854', ' headless: true\n width: 854')
open('/tmp/video_replayer.yaml', 'w').write(c)"
# hello_world — no display, no data needed; expected: "Hello World!"
python3 /tmp/hs_hello_world.py
# video_replayer — needs racerx data; expected: frames rendered, "Graph execution finished."
HOLOSCAN_INPUT_PATH=/path/to/holoscan/data python3 /tmp/hs_video_replayer.py`HOLOSCAN_INPUT_PATH` must point to the directory contain
Official, NVIDIA-verified Agent Skills for Claude Code, Codex, and other coding agents.
Other skills on nvidia-skills.
- /nvidia-skill-finder
Use for NVIDIA-related requests where an NVIDIA skill might help, even if the user did not ask for a skill. Trigger on NVIDIA products, hardware, software, SDKs, GPUs, Jetson/JetPack/L4T/BSP/SDK Manager/driver/flashing/setup, CUDA, NIM, NeMo, Omniverse/OpenUSD/SimReady,
Open skill - /accelerated-computing-cudf
Official NVIDIA-authored guidance for NVIDIA cuDF GPU DataFrames, pandas acceleration, dask-cuDF, ETL, joins, groupby, CSV/Parquet I/O, nullable semantics, and multi-GPU DataFrame workloads.
Open skill - /aiq-deploy
Use when asked to install, deploy, run, validate, troubleshoot, or stop NVIDIA AI-Q Blueprint infrastructure.
Open skill - /aiq-research
Use when asked to run deep research or AI-Q research through a reachable NVIDIA AI-Q Blueprint backend.
Open skill - /amc-run-sample-calibration
Run end-to-end calibration on the shipped sample dataset (sdg_08_2_sample_data_010926.zip) against a running AMC microservice. Use when user says 'test sample dataset', 'run sample calibration', 'verify AMC install', or 'launch and test'.
Open skill - /amc-run-video-calibration
Calibrate a new dataset from pre-recorded video files via the AutoMagicCalib REST API. Use when user has local MP4s and says 'calibrate my videos', 'run AMC on these videos', or similar. For RTSP/live streams, use amc-run-rtsp-calibration instead.
Open skill

