Official agent skill

Holoscan Install Source

by NVIDIA in NVIDIA/skills

Build Holoscan SDK from source via the in-tree ./run script.

OfficialApache-2.0Auto-check: notesDevOps & Cloud

Install Holoscan Install Source

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

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

GitHub CLI
$ gh skill install NVIDIA/skills holoscan-install-source --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-source .claude/skills/holoscan-install-source && 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-source
GitHub stars
3.5k
Token cost
~1.5k tokens
SKILL.md length
531 words
Files
5
Skills in repo
380
Repo updated
First seen
Licence
Apache-2.0

At a glance

Build Holoscan SDK from source via the in-tree ./run script.

  • Works in 6 steps: Consult the Official Install Instructions → Prerequisites → Clone the Repository → …
  • DevOps & Cloud work in your project
  • SKILL.md covers Purpose, Prerequisites, Limitations and Step 0: Consult the Official…, plus 6 more sections
  • Calls apt-get, git and docker; reaches nvidia.github.io and docs.nvidia.com

What it does

Holoscan Install Source is an agent skill from NVIDIA/skills, published by the product's own GitHub organization. Build Holoscan SDK from source via the in-tree ./run script. Use only when published packages don't meet the user's needs.

Its SKILL.md is about 1.5k 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 DevOps & Cloud. It works with NVIDIA AI Platform, CUDA, Docker 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

  • DevOps & Cloud work in your project

Example prompts

  • “t meet the user”
  • “/holoscan-install-source”

Requirements

  • Docker

Workflow steps

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

  1. Consult the Official Install Instructions
  2. Prerequisites
  3. Clone the Repository
  4. Build
  5. Run Tests
  6. Point Applications at the Install Tree

What it can do on your machine

Read from SKILL.md and the folder at commit 67a13c0. 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:

    • apt-get
    • git
    • docker
    • curl
    • apt

    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:

    • nvidia.github.io
    • docs.nvidia.com
    • github.com

    Also links to:

    • docs.docker.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 Source loads about 1.5k tokens when it runs. Until then it costs about 37 tokens; SKILL.md has 531 words of instructions outside code blocks.

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

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

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NoteRuns commands with sudoSKILL.md:53
    a.github.io/libnvidia-container/gpgkey | sudo gpg --dearmor -o /usr/share/keyrings/nvidia-container-toolkit-keyring.gpg
  • NoteRuns commands with sudoSKILL.md:56
    | sudo tee /etc/apt/sources.list.d/nvidia-container-toolkit.list
  • NoteRuns commands with sudoSKILL.md:57
    sudo apt-get update && sudo apt-get install -y nvidia-container-toolkit
  • NoteRuns commands with sudoSKILL.md:58
    sudo nvidia-ctk runtime configure --runtime=docker && sudo systemctl restart docker
  • NoteRuns commands with sudoSKILL.md:60
    - If Docker buildx is missing: `sudo apt-get install docker-buildx-plugin`
  • NoteRuns commands with sudoSKILL.md:93
    rch64` | Cross-compile for ARM64 (needs `sudo apt install qemu-user-static`) |
  • NoteRuns commands with sudoSKILL.md:155
    | Docker buildx not found | `sudo apt-get install docker-buildx-plugin` |
  • NoteRuns commands with sudoSKILL.md:156
    ify NVIDIA Container Toolkit and re-run `sudo nvidia-ctk runtime configure --runtime=docker` |
  • NoteRuns commands with sudoSKILL.md:157
    compile fails (aarch64) | Install qemu: `sudo apt-get install qemu-user-static` |

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 67a13c0, republished under its Apache-2.0 licence (© NVIDIA). 531 words, ~1,530 tokens.

Download SKILL.mdSave it as .claude/skills/holoscan-install-source/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.
name
holoscan-install-source
description
Build Holoscan SDK from source via the in-tree ./run script. Use only when published packages don't meet the user's needs.
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, source, build, cmake

Holoscan SDK — Build from Source

Purpose

Build the Holoscan SDK from the nvidia-holoscan/holoscan-sdk source tree using its ./run script (which builds inside a Docker container), producing a local install tree consumable as a CMake dependency.

Prerequisites

  • Linux host with NVIDIA GPU + driver (nvidia-smi).
  • git, Docker with NVIDIA Container Toolkit (docker run --gpus all works), and docker-buildx-plugin.
  • ~20 GB free disk for the build container + build/install trees.
  • 10–30 min for a clean first build.

Limitations

  • Only recommended when published packages (Conda / container / apt / wheel) don't fit — debug symbols, custom CMake options, or unsupported configs.
  • Still requires Docker — the ./run script builds inside a container; this is not a true bare-metal build.
  • Cross-compiling to aarch64 needs qemu-user-static on the host.

Step 0: Consult the Official Install Instructions

Always fetch the "Build from Source" section of https://docs.nvidia.com/holoscan/sdk-user-guide/sdk_installation.html (and the linked GitHub README.md / DEVELOP.md for the chosen tag) before building. Extract: required ./run flags for the target architecture and CUDA major, supported branches/tags, any Dockerfile patches called out for the release, and the test names recommended for verification. If the doc disagrees with anything below, the doc wins.

Step 1: Prerequisites

Check that git and Docker (with GPU passthrough) are available:

bash
git --version
docker --version
docker run --rm --gpus all ubuntu:22.04 nvidia-smi
  • If Docker is missing → help install from https://docs.docker.com/engine/install/
  • If GPU passthrough fails → install NVIDIA Container Toolkit:
    bash
    curl -fsSL https://nvidia.github.io/libnvidia-container/gpgkey | sudo gpg --dearmor -o /usr/share/keyrings/nvidia-container-toolkit-keyring.gpg
    curl -s -L https://nvidia.github.io/libnvidia-container/stable/deb/nvidia-container-toolkit.list \
      | sed 's#deb https://#deb [signed-by=/usr/share/keyrings/nvidia-container-toolkit-keyring.gpg] https://#g' \
      | sudo tee /etc/apt/sources.list.d/nvidia-container-toolkit.list
    sudo apt-get update && sudo apt-get install -y nvidia-container-toolkit
    sudo nvidia-ctk runtime configure --runtime=docker && sudo systemctl restart docker
  • If Docker buildx is missing: sudo apt-get install docker-buildx-plugin

Step 2: Clone the Repository

Clone repo to ~/holoscan/holoscan-sdk if needed

bash
mkdir -p ~/holoscan/
git clone https://github.com/nvidia-holoscan/holoscan-sdk.git
cd ~/holoscan/holoscan-sdk

To build a specific release tag (recommended for stability):

bash
git tag | grep -E '^v[0-9]' | sort -V | tail -5   # list recent tags
git checkout v<VERSION>                             # e.g. v4.1.0

Step 3: Build

The ./run build script handles container creation, CMake configuration, compilation, and install in one step. Warn the user this takes 10–30 minutes on first run (downloads base image + compiles).

bash
./run build

Common options:

FlagPurpose
--type debugDebug build (symbols, no optimization)
--type RelWithDebInfoRelease + debug symbols
--arch aarch64Cross-compile for ARM64 (needs sudo apt install qemu-user-static)
--gpu igpuiGPU build for Jetson/IGX
--dryrunPreview commands without executing

If CMake cache errors occur after changing options:

bash
./run clear_cache && ./run build

Output lands in these folders, and can be retrieved with ./run get_build_dir and ./run get_install_dir

  • Build dir: build-cu<N>-<arch>/
  • Install dir: install-cu<N>-<arch>/.
Show full SKILL.md (191 more words)Show less

Step 4: Run Tests

Run the following tests

  • EXAMPLE_CPP_HELLO_WORLD_TEST
  • EXAMPLE_PYTHON_HELLO_WORLD_TEST
  • EXAMPLE_CPP_TENSOR_INTEROP_TEST
  • EXAMPLE_PYTHON_TENSOR_INTEROP_TEST
  • EXAMPLE_CPP_VIDEO_REPLAYER_TEST
  • EXAMPLE_PYTHON_VIDEO_REPLAYER_TEST
bash
./run test

To run all six required tests at once, use a single-quoted regex (the | must be quoted to prevent bash from treating it as a pipe):

bash
./run test --options "-R 'EXAMPLE_CPP_HELLO_WORLD_TEST|EXAMPLE_PYTHON_HELLO_WORLD_TEST|EXAMPLE_CPP_TENSOR_INTEROP_TEST|EXAMPLE_PYTHON_TENSOR_INTEROP_TEST|EXAMPLE_CPP_VIDEO_REPLAYER_TEST|EXAMPLE_PYTHON_VIDEO_REPLAYER_TEST' --output-on-failure"

Run a specific test by name or regex:

bash
./run test --name <test_name>
./run test --options "-R '<regex>' --output-on-failure"
./run test --verbose

Important: Always single-quote the regex string when it contains | — without quotes, bash interprets | as a pipe and the command fails with command not found.

Expected: all tests pass. Note any failures and report them to the user before continuing.

Step 5: Point Applications at the Install Tree

Once built, applications can use the install tree as a CMake dependency. Give the user this path:

/path/to/holoscan-sdk/install-cu<N>-<arch>/

They can set Holoscan_ROOT or CMAKE_PREFIX_PATH to this directory when building their own applications.

Troubleshooting

SymptomFix
bash: <TEST_NAME>: command not found when running testsThe regex contains | — wrap it in single quotes: --options "-R '<regex>'"
CMake cache errors after option change./run clear_cache && ./run build
Docker buildx not foundsudo apt-get install docker-buildx-plugin
GPU not visible inside build containerVerify NVIDIA Container Toolkit and re-run sudo nvidia-ctk runtime configure --runtime=docker
Cross-compile fails (aarch64)Install qemu: sudo apt-get install qemu-user-static

© 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-source of NVIDIA/skills.

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

Open the folder on GitHubat commit 67a13c0

Compare with similar skills

Holoscan Install Source 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 Source compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Holoscan Install Source this skillNVIDIA/skills3.5k—~1.5kAutomated safety check: NotesApache-2.0
Init GPU Serverdrawthingsai/draw-things-community580—~2.2kAutomated safety check: PassGPL-3.0
Vllm Deploy Dockervllm-project/vllm-skills103—~2.5kAutomated safety check: NotesApache-2.0
Cosmos3 Env TroubleshootNVIDIA/cosmos-framework558—~1.3kAutomated safety check: NotesCustom licence
Generate Nemo Gym Envadithya-s-k/FineEnvs443—~2.1kAutomated safety check: PassApache-2.0
Setup Workshopbrevdev/workshop-build-an-agent144—~2.3kAutomated safety check: NotesApache-2.0

Similar skills

  • Init GPU Server

    drawthingsai/draw-things-community

    Initialize a Draw Things GPU server with GPUScript, including script sync, Docker/CUDA/NVIDIA runtime setup, 7T data disk mounting, mergerfs, and end-to-end GPU verification.

    580 GitHub stars~2.2k tokensUpdated yesterday
    DevOps & CloudAuto-check passed
  • Vllm Deploy Docker

    vllm-project/vllm-skills

    Deploy vLLM using Docker (pre-built images or build-from-source) with NVIDIA GPU support and run the OpenAI-compatible server.

    103 GitHub stars~2.5k tokensUpdated 6 mo ago
    AI & LLM EngineeringAuto-check: notes
  • Cosmos3 Env Troubleshoot

    NVIDIA/cosmos-framework

    Official

    Diagnose and fix Cosmos3 environment, installation, and runtime errors.

    558 GitHub stars~1.3k tokensUpdated today
    DevOps & CloudAuto-check: notes
  • Generate Nemo Gym Env

    adithya-s-k/FineEnvs

    Builds a NeMo Gym (NVIDIA) variant of an RL environment. An agent skill from adithya-s-k/FineEnvs.

    443 GitHub stars~2.1k tokensUpdated today
    DevOps & CloudAuto-check passed
  • Setup Workshop

    brevdev/workshop-build-an-agent

    This skill should be used when the user wants to set up, install, deploy, bootstrap, or "spin up" the Build-an-Agent workshop (a.k.a.

    144 GitHub stars~2.3k tokensUpdated today
    DevOps & CloudAuto-check: notes
  • Dstack Presets

    dstackai/dstack

    Create and manage dstack presets: a toolkit that streamlines model inference optimization with agents, and a portable preset format.

    2.3k GitHub stars~403 tokensUpdated today
    DevOps & CloudAuto-check passed

More from NVIDIA/skills

All 380 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.5k 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.5k GitHub stars~2.9k tokensUpdated today
    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.5k GitHub stars~4.8k tokensUpdated today
    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.5k GitHub stars~5k tokensUpdated today
    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.5k GitHub stars~4.7k tokensUpdated today
    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.5k GitHub stars~2.7k tokensUpdated today
    Auto-check: notes

Categories

Questions about Holoscan Install Source

What does Holoscan Install Source do?

Build Holoscan SDK from source via the in-tree ./run script. Holoscan Install Source is an agent skill from NVIDIA/skills, published by the product's own GitHub organization./run script.

When should I use Holoscan Install Source?

Holoscan Install Source fits situations like: devOps & Cloud work in your project.

How do I install Holoscan Install Source in Claude Code?

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

How do I install Holoscan Install Source in Codex?

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

Can I use Holoscan Install Source 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-source -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-source, .gemini/skills/holoscan-install-source, .github/skills/holoscan-install-source and .opencode/skills/holoscan-install-source in your project.

What does Holoscan Install Source need to run?

Going by SKILL.md and its folder, Holoscan Install Source needs the command-line tools its instructions call (apt-get, git, docker, curl and apt). Our summary lists: Docker.

Does Holoscan Install Source access the network?

SKILL.md names 4 domains. In commands or code: nvidia.github.io, docs.nvidia.com and github.com; the agent is likely to contact these when it follows the instructions. As links in the text: docs.docker.com. This is read from the text; nothing was executed.

Is Holoscan Install Source safe to install?

Our automated static check of SKILL.md found notes only (runs commands with sudo), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Holoscan Install Source use?

Holoscan Install Source 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 Source use?

About 1.5k tokens (SKILL.md is roughly 6.1k 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 Source?

Skills that share tags, products or a category with Holoscan Install Source: Init GPU Server (drawthingsai/draw-things-community, 580 stars), Vllm Deploy Docker (vllm-project/vllm-skills, 103 stars), Cosmos3 Env Troubleshoot (NVIDIA/cosmos-framework, 558 stars) and Generate Nemo Gym Env (adithya-s-k/FineEnvs, 443 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Holoscan Install Source?

NVIDIA (a GitHub organization, an official publisher) maintains it in NVIDIA/skills, which has 3,539 GitHub stars. The repository holds 380 skills in this directory. The repository was last updated on October 7, 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.