Official agent skill

Holoscan Install Conda

by NVIDIA in NVIDIA/skills

Install Holoscan SDK v4.3+ via Conda in a CUDA 13 environment.

OfficialApache-2.0Auto-check passedAI & LLM Engineering

Install Holoscan Install Conda

skills CLI
$ npx skills add NVIDIA/skills --skill holoscan-install-conda -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install NVIDIA/skills holoscan-install-conda --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/NVIDIA/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/holoscan-install-conda .claude/skills/holoscan-install-conda && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
holoscan-install-conda
GitHub stars
3.6k
Token cost
~2k tokens
SKILL.md length
733 words
Files
5
Skills in repo
390
Repo updated
First seen
Licence
Apache-2.0

At a glance

Install Holoscan SDK v4.3+ via Conda in a CUDA 13 environment.

  • Works in 5 steps: Consult the Official Install Instructions → Prerequisites Check → Create Environment and Install → …
  • Redirect CUDA 12 hosts to container/wheel
  • SKILL.md covers Purpose, Prerequisites, Limitations and Step 0: Consult the Official…, plus 5 more sections
  • Calls conda, python3 and curl; reaches github.com and docs.nvidia.com

What it does

Holoscan Install Conda is an agent skill from NVIDIA/skills, published by the product's own GitHub organization. Install Holoscan SDK v4.3+ via Conda in a CUDA 13 environment. Use for Conda installs; redirect CUDA 12 hosts to container/wheel.

Its SKILL.md is about 2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files (for example `BENCHMARK.md`, `evals/evals.json` and `skill-card.md`).

It sits in AI & LLM Engineering. It works with NVIDIA AI Platform, CUDA, Python and C++. The repository describes itself as: Agent Skills for NVIDIA products — install into Claude Code, Codex, and other coding agents to run Physical AI, robotics, simulation, CUDA, and RAG workflows end to end. The licence is Apache-2.0.

When your agent uses it

  • Redirect CUDA 12 hosts to container/wheel

Example prompts

  • “/holoscan-install-conda”

Requirements

  • Python 3

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Consult the Official Install Instructions
  2. Prerequisites Check
  3. Create Environment and Install
  4. Run Python Tests
  5. Remind the User

What it can do on your machine

Read from SKILL.md and the folder at commit 14a98ae. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • conda
    • python3
    • curl
    • wget
    • bash

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • github.com
    • docs.nvidia.com
    • raw.githubusercontent.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Holoscan Install Conda loads about 2k tokens when it runs. Until then it costs about 38 tokens; SKILL.md has 733 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~38
When it runs · the whole SKILL.md, loaded when a task matches
~2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from NVIDIA/skills at commit 14a98ae, republished under its Apache-2.0 licence (© NVIDIA). 733 words, ~1,958 tokens.

Download SKILL.mdSave it as .claude/skills/holoscan-install-conda/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.
name
holoscan-install-conda
description
Install Holoscan SDK v4.3+ via Conda in a CUDA 13 environment. Use for Conda installs; redirect CUDA 12 hosts to container/wheel.
version
1.0.0
license
Apache-2.0
metadata.author
Holoscan Team <holoscan-team@nvidia.com>
metadata.github-url
https://github.com/nvidia-holoscan/holoscan-sdk
metadata.tags
holoscan, install, conda, cuda

Holoscan 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

bash
conda --version 2>&1
nvidia-smi 2>&1 | head -5

If conda is not found, install Miniforge silently (preferred over Miniconda for conda-forge):

bash
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:

bash
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:

bash
conda install <packages> rmm ucxx cuda-version=13 -c rapidsai -c conda-forge -y

For C++ development, also install the toolchain:

bash
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".

Show full SKILL.md (315 more words)Show less

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:

bash
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 containing a racerx/ subdirectory. If the user has the SDK source repo that is ~/repos/holoscan-sdk/data; otherwise download with the download_ngc_data script from the Debian or source install tree.

Step 4: Remind the User

They must do the following in each new shell session:

bash
source ~/miniforge3/etc/profile.d/conda.sh   # if Miniforge was installed with -b
conda activate holoscan
ulimit -s 32768   # recommended — prevents segfaults in some apps

Consider adding these lines to ~/.bashrc or ~/.zshrc to avoid repeating them.

Then offer next steps:

  • Explore C++ and Python examples at https://github.com/nvidia-holoscan/holoscan-sdk/tree/v<VERSION>/examples
  • Walk through a specific example: /explain-example
  • Start building a custom Holoscan application

Troubleshooting

  • ImportError: librmm.so: cannot open shared object file. rmm was not installed. Re-run the Step 2 conda install line — rmm is an undeclared runtime dependency of holoscan.
  • Solver picks an older holoscan build than expected. Channel order may be wrong. Use -c rapidsai -c conda-forge (rapidsai first) — that's the order in the official install command, and under strict channel priority a conda-forge-first ordering can lock the solver to an older holoscan build.
  • Segmentation fault on app startup. Set ulimit -s 32768 in the current shell before running any Holoscan app. Not all apps trip this, but the larger stack avoids the failure mode.
  • find_package(holoscan) fails when building C++ apps. Install libholoscan-dev (headers + CMake config are in a separate package since v4.1.0).
  • conda: command not found in a new shell. Miniforge was installed with -b and did not patch .bashrc. Run source ~/miniforge3/etc/profile.d/conda.sh or add it to your shell RC file.

© NVIDIA, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 4 other files in skills/holoscan-install-conda of NVIDIA/skills.

  • SKILL.md
  • BENCHMARK.md
  • evals/evals.json
  • skill-card.md
  • skill.oms.sig

Open the folder on GitHubat commit 14a98ae

Compare with similar skills

Holoscan Install Conda next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Holoscan Install Conda compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Holoscan Install Conda this skillNVIDIA/skills3.6k—~2kAutomated safety check: PassApache-2.0
Cutlass SkillslowlyC/agent-gpu-skills169—~1.3kAutomated safety check: PassMIT
Make Op VerifyCVCUDA/CV-CUDA2.7k—~433Automated safety check: PassCustom licence
Review Op SupportCVCUDA/CV-CUDA2.7k—~248Automated safety check: PassCustom licence
Review Op Test CoverageCVCUDA/CV-CUDA2.7k—~264Automated safety check: PassCustom licence
Paddle BuildPaddlePaddle/Paddle24k—~1kAutomated safety check: PassApache-2.0

Similar skills

  • Cutlass Skill

    slowlyC/agent-gpu-skills

    Write, debug, and optimize CUTLASS, CuTe, and CuTeDSL GPU kernels from local upstream source, examples, and headers.

    169 GitHub stars~1.3k tokensUpdated 2 mo ago
    AI & LLM EngineeringAuto-check passed
  • Make Op Verify

    CVCUDA/CV-CUDA

    Verify a new CV-CUDA operator against the deterministic final regression checklist (the /make-op done-gate).

    2.7k GitHub stars~433 tokensUpdated 23 days ago
    AI & LLM EngineeringAuto-check passed
  • Review Op Support

    CVCUDA/CV-CUDA

    Review a CV-CUDA operator's input-type, layout, dtype, and channel support matrix.

    2.7k GitHub stars~248 tokensUpdated 23 days ago
    AI & LLM EngineeringAuto-check passed
  • Review a CV-CUDA operator's test coverage, including C++ correctness, required cross-layout parity, correctness rigor, and the Python API surface.

    2.7k GitHub stars~264 tokensUpdated 23 days ago
    Testing & QAAuto-check passed
  • Paddle Build

    PaddlePaddle/Paddle

    A skill your agent uses when needing to compile, rebuild, or install Paddle from source after code changes.

    24k GitHub stars~1k tokensUpdated today
    AI & LLM EngineeringAuto-check passed
  • Optimize Op

    CVCUDA/CV-CUDA

    Drive a single-operator optimization campaign per .agents/guidance/OPTIMIZATIONGUIDELINES.md, with a deterministically enforced definition-of-done and versioned MR summary.

    2.7k GitHub stars~834 tokensUpdated 23 days ago
    AI & LLM EngineeringAuto-check passed

More from NVIDIA/skills

All 390 skills in this repo
  • Official

    A skill your agent uses when the user wants to deploy, run, debug, tear down, or call the REST API of the RTVI-CV 2D detection / tracking microservice.

    3.6k GitHub starsUsed in 1 repo~4.5k tokens
    Auto-check passed
  • Official

    Generates, validates, compares and explains HOLOLINK_def.svh macro files for the HSB IP, using bundled Python scripts and asking before it writes anything.

    3.6k GitHub stars~2.9k tokensUpdated yesterday
    Auto-check passed
  • Official

    Runs and validates an end-to-end Mission Control demo in a locally installed Isaac Sim, with a Nova Carter robot driven through a Python server.

    3.6k GitHub stars~4.8k tokensUpdated yesterday
    Auto-check passed
  • Orchestrates defect image generation for PCBA, metal surface and glass inspection with NVIDIA Cosmos AnomalyGen on OSMO, from cold-start Day 0 to real-photo Day 1 labeling.

    3.6k GitHub stars~5k tokensUpdated yesterday
    Auto-check: notes
  • Orchestrates video data augmentation and auto-labeling workflows on OSMO, from flow selection and preflight checks to submission, monitoring and output download.

    3.6k GitHub stars~4.7k tokensUpdated yesterday
    Auto-check: notes
  • Official

    Runs NVIDIA TAO Data Services KPI analysis on object detection results, comparing predictions to ground truth and writing per-class precision, recall and AP to a CSV.

    3.6k GitHub stars~2.7k tokensUpdated yesterday
    Auto-check: notes

Questions about Holoscan Install Conda

What does Holoscan Install Conda do?

Install Holoscan SDK v4.3+ via Conda in a CUDA 13 environment. Holoscan Install Conda is an agent skill from NVIDIA/skills, published by the product's own GitHub organization.3+ via Conda in a CUDA 13 environment.

When should I use Holoscan Install Conda?

Holoscan Install Conda fits situations like: redirect CUDA 12 hosts to container/wheel.

How do I install Holoscan Install Conda in Claude Code?

Run `npx skills add NVIDIA/skills --skill holoscan-install-conda -a claude-code`. Or copy the skill folder (skills/holoscan-install-conda in NVIDIA/skills) into .claude/skills/holoscan-install-conda in your project. Claude Code loads it when a task matches its description.

How do I install Holoscan Install Conda in Codex?

Run `npx skills add NVIDIA/skills --skill holoscan-install-conda -a codex`. Or copy the skill folder (skills/holoscan-install-conda in NVIDIA/skills) into .agents/skills/holoscan-install-conda in your project. Codex loads it when a task matches its description.

Can I use Holoscan Install Conda in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add NVIDIA/skills --skill holoscan-install-conda -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/holoscan-install-conda, .gemini/skills/holoscan-install-conda, .github/skills/holoscan-install-conda and .opencode/skills/holoscan-install-conda in your project.

What does Holoscan Install Conda need to run?

Going by SKILL.md and its folder, Holoscan Install Conda needs the command-line tools its instructions call (conda, python3, curl, wget and bash). Our summary lists: Python 3.

Does Holoscan Install Conda access the network?

SKILL.md names 3 domains. In commands or code: github.com, docs.nvidia.com and raw.githubusercontent.com; the agent is likely to contact these when it follows the instructions. This is read from the text; nothing was executed.

Is Holoscan Install Conda safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Holoscan Install Conda use?

Holoscan Install Conda is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Holoscan Install Conda use?

About 2k tokens (SKILL.md is roughly 7.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Holoscan Install Conda?

Skills that share tags, products or a category with Holoscan Install Conda: Cutlass Skill (slowlyC/agent-gpu-skills, 169 stars), Make Op Verify (CVCUDA/CV-CUDA, 2.7k stars), Review Op Support (CVCUDA/CV-CUDA, 2.7k stars) and Review Op Test Coverage (CVCUDA/CV-CUDA, 2.7k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Holoscan Install Conda?

NVIDIA (a GitHub organization, an official publisher) maintains it in NVIDIA/skills, which has 3,555 GitHub stars. The repository holds 390 skills in this directory. The repository was last updated on October 9, 2026.

Source: NVIDIA/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.