Generated banner for Holoscan Install Container
Generated logo for Holoscan Install Container

Holoscan Install Container

NVIDIAOfficialCreated by Holoscan TeamDistributed by NVIDIA

  • Skill
  • Workflow
  • Cloud and DevOps
  • Apache-2.0
  • Medium risk

From the author

Install and verify the Holoscan SDK 5.x CUDA 13 development container after checking release availability and host compatibility.
— 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 procedure for setting up the Holoscan SDK 5.x development environment using Docker. It guides the user through verifying host compatibility, selecting the correct container image for CUDA 13, pulling the image, and performing verification tests to ensure the SDK and its components are correctly installed and functional.

What it does

  • Verifies host system compatibility and driver requirements for Holoscan SDK 5.x.
  • Identifies the correct multi-architecture container image for CUDA 13.
  • Provides commands to pull and inspect the official Holoscan development image.
  • Executes verification tests for C++ and Python SDK components.
  • Validates core functionality using provided example pipelines.
  • Reports final installation status, including image digests and test results.

When to use it

  • When setting up a new development environment for Holoscan SDK 5.x.
  • When troubleshooting containerized Holoscan installations.
  • When verifying that a host system meets the requirements for CUDA 13-based Holoscan development.
  • When needing to confirm the integrity of a pulled Holoscan development image.

Advantages

  • Ensures compatibility by checking host drivers and architecture before installation.
  • Standardizes the verification process for both C++ and Python APIs.
  • Reduces configuration errors by using official container images.
  • Provides a clear reporting structure for installation success or failure.

Usage examples

“Install the Holoscan 5.0 development container on my system.”
The agent will check your host compatibility, pull the specific v5.0-cuda13 image, and run verification tests to confirm the SDK is ready for use.
“Verify if my current Holoscan container is correctly installed.”
The agent will execute the verification workflow, checking for the presence of core examples and Python API accessibility to confirm the installation.

Install

  1. Download the skill as a ZIP:

    https://autogineer.com/agent-skills/nvidia/holoscan-install-container/download
  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip holoscan-install-container.zip -d .agents/skills

Documentation by Holoscan Team

Holoscan 5.x Development Container

1. Check the release and platform

This skill targets Holoscan SDK 5.x. Select the requested 5.x release before choosing artifacts. Read its release notes and the matching SDK installation guide. Select the 5.x documentation version; an unversioned page may describe 4.x. For an unreleased checkout, use its docs/sdk_installation.mdx and DEVELOP.md. Early Access binary commands describe planned artifacts, so confirm publication for the exact release before installing. If unavailable, explain that status and offer holoscan-install-source; keep the requested 5.x version.

The 5.0 artifact set targets CUDA 13 and dGPU systems on x86_64 or arm64. Native packages use Ubuntu 24.04; wheels use glibc 2.39 and regular CPython 3.12–3.14. Check the selected release for changes to that matrix. There is no CUDA 12 variant or separate Tegra/iGPU artifact in this set. A driver reporting CUDA 12 support needs a compatibility assessment or driver upgrade before a CUDA 13 installation; the nvidia-smi CUDA field is a driver capability, not the installed toolkit version. Never infer compatibility from that field alone.

2. Select and pull the image

Inspect Linux architecture, GPU model, driver, Docker, and NVIDIA Container Toolkit. The planned image is one multi-architecture amd64/arm64 dGPU image: nvcr.io/nvidia/clara-holoscan/holoscan:v<SDK_VERSION>-cuda13. Check the NGC catalog and release notes for the exact published tag and supported host. There are no cuda12-dgpu or cuda12-igpu tags for this 5.x workflow. GPU passthrough tests may pull an image; explain the download before running one if needed.

Use the exact published tag within the installation scope the user authorized. When the method and release are already selected, proceed with that choice. Ask only when a missing release or host fact prevents safe selection. For a plan-only request, return the commands without pulling or running images:

# SDK_VERSION is the exact published 5.x tag version from the release notes.
IMAGE="nvcr.io/nvidia/clara-holoscan/holoscan:v${SDK_VERSION}-cuda13"
docker pull "$IMAGE"
docker image inspect --format 'ID={{.Id}} RepoDigests={{json .RepoDigests}}' "$IMAGE"
docker run --rm --gpus all "$IMAGE" nvidia-smi

Record the image ID and repository digests from inspection for the final report. If no repository digest is available, report the image ID and that limitation.

The development image contains the installed C++ and Python SDK under /usr, all three optional modules, examples, and RacerX data. It is distinct from the source-build container managed by ./run.

3. Verify the installed SDK

Use a bounded Core example and Python API discovery first. Locate the examples instead of assuming the 4.x /opt/nvidia/holoscan layout or a fixed multiarch library directory:

docker run --rm --gpus all "$IMAGE" bash -eu -c '
  example=$(find /usr/lib -type f -path "*/holoscan/examples/hello_world/cpp/hello_world" -print -quit)
  test -n "$example"
  "$example"
  python3 -c "import holoscan as hs; print(hs.__version__); print(hs.RealtimeClock); print(len(hs.registry.operators()))"
'

Expect Hello Holoscan!, the requested 5.x version, and successful API access. Run the installed first_pipeline/python/first_pipeline.py example when present for graph execution coverage. Check the release's installed example tree and README before adding module/GPU tests; a Core import alone does not qualify Vision, Visualization, Inference, graphics, or camera support.

4. Report results and reuse the image

docker run --rm -it --gpus all "$IMAGE" bash

Add mounts for the user's project or devices as the application needs them. For GUI workloads follow the selected release's display/graphics instructions; keep initial verification independent of display and datasets.

  • GPU passthrough failure: check the host driver and Container Toolkit setup.

  • Missing tag: report publication status and offer source; keep the 5.x target.

  • Missing examples or Python components: inspect the pulled image tag/digest; verify it is the development image for the selected release.

Report the image tag/digest, architecture, SDK version, tests run, and skipped hardware or module checks.

Files

BENCHMARK.md

Skill Benchmark: holoscan-install-container

✅ Overall verdict: PASS — Recommended for publication

Publication Recommendation

Recommended for publication based on the completed evaluation evidence in this report.

Evaluation Metadata

  • Skill: holoscan-install-container

  • Evaluation date: 2026-10-15

  • Evaluator version: 1.5.6

  • Agents: Claude Code (aws/anthropic/bedrock-claude-opus-4-8), Codex (openai/openai/gpt-5.5)

  • Tasks: 4 evaluation tasks (3 positive, 1 negative)

  • Dataset digest: sha256:ed38125dd6f2c6f949645eb559436a68b8acd45f40b70699f3c00835ad4f6f29 (skill-evaluator-dataset-snapshot/1)

  • Attempts per task: 1

  • Environment: k8s-sandbox

  • Tier 2 evidence: required for publication

  • Tier 3 evidence: required for publication

Each task attempt ran in its own isolated sandbox pod.

What This Report Answers

The three-tier evaluation checks whether the skill:

  • is safe to use;

  • produces correct answers;

  • is discovered and activated when needed;

  • helps the agent complete the user's goal and expected workflow; and

  • avoids wasted skill and tool usage.

Results at a Glance

MeasureClaude Code (Baseline → Skill Uplift)Codex (Baseline → Skill Uplift)
Overall93.3% — baseline ran, but no comparable score was available; uplift unavailable94.6% — baseline ran, but no comparable score was available; uplift unavailable
Security75.0% → 75.0% (±0.0 points)75.0% → 87.5% (+12.5 points)
Correctness75.0% → 100.0% (+25.0 points)90.0% → 100.0% (+10.0 points)
Discoverability100.0% — baseline ran, but no comparable score was available; uplift unavailable95.0% — baseline ran, but no comparable score was available; uplift unavailable
Effectiveness73.1% → 91.3% (+18.2 points)71.5% → 90.4% (+18.9 points)
Efficiency100.0% — baseline ran, but no comparable score was available; uplift unavailable100.0% — baseline ran, but no comparable score was available; uplift unavailable

How to read this table: baseline is the same task attempted without the target skill. Scores are rounded to one decimal; threshold-adjacent values use additional precision so their displayed band matches the verdict. Uplift is derived from those displayed scores and shown in percentage points.

Example: 47.0% → 92.0% (+45.0 points) means the skill-assisted run scored 92.0%, 45.0 percentage points above its 47.0% no-skill baseline.

A partial dimension was calculated from only the available configured signals; review the detailed report before relying on it.

Token Usage

Actual Tier 3 execution usage is reported for every observed agent/case pair and both conditions.

AgentDataset caseWith skillWithout skillDeltaChangeCoverage
claude-codeAll cases756,691983,319N/AN/Askill 1/4; base 1/4
claude-codeholoscan-install-container-5x-001N/AN/AN/AN/Askill 0/1; base 0/1
claude-codeholoscan-install-container-5x-002756,691983,319-226,628-23.05%skill 1/1; base 1/1
claude-codeholoscan-install-container-5x-003N/AN/AN/AN/Askill 0/1; base 0/1
claude-codeholoscan-install-container-5x-004N/AN/AN/AN/Askill 0/1; base 0/1
codexAll cases750,625616,870N/AN/Askill 1/4; base 1/4
codexholoscan-install-container-5x-001N/A616,870N/AN/Askill 0/1; base 1/1
codexholoscan-install-container-5x-002N/AN/AN/AN/Askill 0/1; base 0/1
codexholoscan-install-container-5x-003750,625N/AN/AN/Askill 1/1; base 0/1
codexholoscan-install-container-5x-004N/AN/AN/AN/Askill 0/1; base 0/1
ALL AGENTSDataset aggregate1,507,3161,600,189N/AN/Askill 2/8; base 2/8

Prompt tokens include cached reads, so total tokens are prompt + completion (cached is not added twice). The Efficiency score uses (prompt - cached) + completion. N/A means the relevant trajectory counters were not available; coverage is never estimated.

Tier Status

TierPurposeStatusEvidence
Tier 1Static validationPASSED WITH OBSERVATIONS11 validator(s); 11 finding(s)
Tier 2Semantic deduplicationPASSED2 validator(s); 0 finding(s)
Tier 3Live agent evaluationPASS2 agent(s); 4 task(s)

Findings and Observations

<details> <summary>Show detailed findings and successful checks</summary>

  • MEDIUM SCHEMA/body_recommended_section: Missing recommended section: '## Instructions' (team-skills/holoscan/holoscan-sdk/holoscan-install-container/SKILL.md)

  • MEDIUM SCHEMA/body_recommended_section: Missing recommended section: '## Examples' (team-skills/holoscan/holoscan-sdk/holoscan-install-container/SKILL.md)

  • MEDIUM SECURITY/Unknown (RP1): MCP Rug Pull: The docker pull "$IMAGE" command uses a shell variable $IMAGE constructed from SDK_VERSION and a hardcoded suffix (SKILL.md:54)

  • MEDIUM SECURITY/Unknown (RP1): MCP Rug Pull: The docker run --rm --gpus all "$IMAGE" nvidia-smi command runs a container from an image referenced by a mutable tag (SKILL.md:56)

  • MEDIUM SECURITY/Unknown (RP1): MCP Rug Pull: The verification docker run command at line 73 also uses $IMAGE (a mutable tag) and executes bash -eu -c '...' ins (SKILL.md:73)

  • 6 additional finding(s) are available in the full evaluation artifacts.

</details>

Scoring Methodology

<details> <summary>Show dimension definitions, source signals, and thresholds</summary>

DimensionQuestionScored signals
SecurityIs it safe to use?security (100%)
CorrectnessIs the answer correct?accuracy (100%)
DiscoverabilityWas the right skill loaded when needed?skill_execution (100%)
EffectivenessDid the skill help complete the task?goal_accuracy (50%) + behavior_check (50%)
EfficiencyDid it avoid wasted tool calls and token usage?skill_efficiency (50%) + token_efficiency (50%)
  • Dimension bands: PASS at 50% or above; NEUTRAL from 40% to below 50%; FAIL below 40%.

  • Overall Tier 3 lift: PASS at +5 points or more; FAIL at -10 points or less; values between those bands are NEUTRAL.

  • Overall verdict: PASS only when every configured dimension passes for at least one supported agent. Lift is reported as diagnostic evidence and does not override this gate.

  • The 50% attempt pass threshold is a separate per-task gate; it is not the dimension pass threshold.

  • Effectiveness is the equal-weight mean of goal completion (goal_accuracy) and expected workflow adherence (behavior_check).

  • Efficiency is 50% tool-call productivity (the backward-compatible skill_efficiency wire id) and 50% token_efficiency. Positive-case skill routing is scored under Discoverability, not Efficiency; a negative case without a routing target is N/A. N/A sources are omitted, remaining weights are renormalized, and the dimension is marked partial.

Signals present in this run:

  • security (Security): unsafe operations, secret leakage, and unauthorized access.

  • skill_execution (Skill Execution): whether the expected skill was selected, decoys were avoided, and the workflow executed.

  • skill_efficiency (Tool Productivity): tool-call productivity (legacy wire id; routing is scored under Discoverability).

  • accuracy (Accuracy): final-answer correctness against the reference answer.

  • goal_accuracy (Goal Accuracy): whether the user's goal was achieved.

  • behavior_check (Behavior Check): whether the expected workflow behavior was followed.

</details>

Freshness

Regenerate this benchmark when the skill, evaluation dataset, target agent/model, evaluator version, environment, or scoring policy changes.

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.

Needs: Needs a command-line tool, Needs Python

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/holoscan-install-container · commit fce3cca
Licence
Apache License 2.0 (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE-APACHE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

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 holoscan-install-container.zip