Official agent skill

Tao Setup Nvidia GPU Host

by NVIDIA in NVIDIA/skills

Host setup for TAO GPU backends. An agent skill from NVIDIA/skills.

OfficialApache-2.0Auto-check: notesDevOps & Cloud

Install Tao Setup Nvidia GPU Host

skills CLI
$ npx skills add NVIDIA/skills --skill tao-setup-nvidia-gpu-host -a claude-code

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

GitHub CLI
$ gh skill install NVIDIA/skills tao-setup-nvidia-gpu-host --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/tao-setup-nvidia-gpu-host .claude/skills/tao-setup-nvidia-gpu-host && 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
tao-setup-nvidia-gpu-host
GitHub stars
3.5k
Token cost
~3.4k tokens
SKILL.md length
1,367 words
Files
8 (incl. scripts, references)
Skills in repo
380
Repo updated
First seen
Licence
Apache-2.0

At a glance

Host setup for TAO GPU backends. An agent skill from NVIDIA/skills.

  • Works in 7 steps: Adds NVIDIA's CUDA repository if missing… → Adds NVIDIA's Container Toolkit… → Installs the matching kernel header /… → …
  • The user asks to set up an NVIDIA GPU host
  • SKILL.md covers Quick Start, Workflow Contract, Model Runtime Override Contract and What The Installer Does, plus 3 more sections
  • Runs Shell scripts from its folder; calls bash, docker and helm; reaches docs.nvidia.com and docs.docker.com

What it does

Tao Setup Nvidia GPU Host is an agent skill from NVIDIA/skills, published by the product's own GitHub organization. Host setup for TAO GPU backends. Checks and, after user approval, installs minimum-compatible NVIDIA driver, CUDA Toolkit, and NVIDIA Container Toolkit versions for Docker/local-Docker and Kubernetes GPU worker hosts. TAO-wide defaults can be overridden by the selected model's runtime profile. The --check-only path works on any Linux distribution; --install automates debian-family (Ubuntu/Debian/Pop!OS/Mint/Zorin/Raspbian), rhel-family (Fedora/RHEL/Rocky/AlmaLinux), and suse-family (openSUSE/SLES) hosts, and…

Its SKILL.md is about 3.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 11 other files, including scripts and reference files (for example `BENCHMARK.md`, `config/skillspector-baseline.yaml` and `evals/evals.json`). Compatibility notes: Runs --check-only on any Linux distribution. --install automates Ubuntu 22.04/24.04 + Debian 12 (apt), Fedora + RHEL/Rocky/AlmaLinux 9/10 (dnf), and openSUSE…

It sits in DevOps & Cloud, covering Containers and Container orchestration. It works with NVIDIA AI Platform, CUDA, Docker and Kubernetes. 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

  • The user asks to set up an NVIDIA GPU host
  • Check TAO Docker GPU runtime
  • Prepare a Kubernetes GPU worker for TAO

Example prompts

  • “set up an NVIDIA GPU host”
  • “check TAO Docker GPU runtime”
  • “/tao-setup-nvidia-gpu-host”

Requirements

  • Python 3
  • A Bash shell
  • Docker
  • Compatibility (from SKILL.md): Runs `--check-only` on any Linux distribution. `--install` automates Ubuntu 22.04/24.04 + Debian 12 (apt), Fedora + RHEL/Rocky/AlmaLinux 9/10 (dnf), and openSUSE Leap / SLES 15 (zypper). Requires sudo/root, internet access to NVIDIA package repositories (and download.docker.com on rhel-family), and an x86_64 or aarch64 (sbsa) host. Other distributions (Arch, Alpine, Gentoo, NixOS, …) get a clear error that names the version targets and the NVIDIA install-guide URL.
  • Pre-approved tools (allowed-tools): Read, Bash

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

  1. Adds NVIDIA's CUDA repository if missing (apt cuda-keyring deb,
  2. Adds NVIDIA's Container Toolkit repository if missing (.list for apt,
  3. Installs the matching kernel header / devel package for the running
  4. Installs the current open-driver and Container Toolkit packages from the
  5. For Docker backends and when Docker is missing, installs Docker
  6. Adds the invoking user ($SUDO_USER if available, else $USER) to the
  7. Attempts modprobe nvidia so verification can pass before reboot.

What it can do on your machine

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

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Bash

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 1 file in scripts/ (Shell), which the agent can run.

    Shell commands in SKILL.md call:

    • bash
    • docker
    • helm

    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:

    • docs.nvidia.com
    • docs.docker.com
    • helm.ngc.nvidia.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.

  • Compatibility

    Runs `--check-only` on any Linux distribution. `--install` automates Ubuntu 22.04/24.04 + Debian 12 (apt), Fedora + RHEL/Rocky/AlmaLinux 9/10 (dnf), and openSUSE Leap / SLES 15 (zypper). Requires sudo/root, internet access to NVIDIA package repositories (and download.docker.com on rhel-family), and an x86_64 or aarch64 (sbsa) host. Other distributions (Arch, Alpine, Gentoo, NixOS, …) get a clear error that names the version targets and the NVIDIA install-guide URL.

    From compatibility in the SKILL.md frontmatter.

Context cost

Tao Setup Nvidia GPU Host loads about 3.4k tokens when it runs, and up to ~4k if it reads all its reference files. Until then it costs about 184 tokens; SKILL.md has 1,367 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~184
When it runs · the whole SKILL.md, loaded when a task matches
~3.4k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~4k

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:169
    sudo docker run --rm --runtime=nvidia --gpus all "$TAO_IMAGE" nvidia-smi -L
  • NoteRuns commands with sudoSKILL.md:256
    `sudo modprobe nvidia` or reboot. Secure Boot may require MOK enrollment on
  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Read, Bash

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); the scripts in this folder are not scanned.

SKILL.md

The full file from NVIDIA/skills at commit 0e0d506, republished under its Apache-2.0 licence (© NVIDIA). 1,367 words, ~3,381 tokens.

Download SKILL.mdSave it as .claude/skills/tao-setup-nvidia-gpu-host/SKILL.md (or your agent's skills folder). This skill also uses 7 other files; get the full folder from GitHub.
name
tao-setup-nvidia-gpu-host
description
Host setup for TAO GPU backends. Checks and, after user approval, installs minimum-compatible NVIDIA driver, CUDA Toolkit, and NVIDIA Container Toolkit versions for Docker/local-Docker and Kubernetes GPU worker hosts. TAO-wide defaults can be overridden by the selected model's runtime profile. The `--check-only` path works on any Linux distribution; `--install` automates debian-family (Ubuntu/Debian/Pop!_OS/Mint/Zorin/Raspbian), rhel-family (Fedora/RHEL/Rocky/AlmaLinux), and suse-family (openSUSE/SLES) hosts, and prints actionable manual-install steps for everything else. Use when the user asks to "set up an NVIDIA GPU host", "check TAO Docker GPU runtime", or prepare a Kubernetes GPU worker for TAO.
allowed-tools
Read, Bash
compatibility
Runs `--check-only` on any Linux distribution. `--install` automates Ubuntu 22.04/24.04 + Debian 12 (apt), Fedora + RHEL/Rocky/AlmaLinux 9/10 (dnf), and openSUSE Leap / SLES 15 (zypper). Requires sudo/root, internet access to NVIDIA package repositories (and download.docker.com on rhel-family), and an x86_64 or aarch64 (sbsa) host. Other distributions (Arch, Alpine, Gentoo, NixOS, …) get a clear error that names the version targets and the NVIDIA install-guide URL.
license
Apache-2.0
metadata.author
NVIDIA Corporation
metadata.version
0.1.2
tags
setup, nvidia, cuda, docker, kubernetes

NVIDIA GPU Host Setup

Standalone install? If this session was not initialized by the TAO skill bank plugin, run the tao-setup skill first (host preflight, credentials, cross-skill discovery).

Use this setup skill before TAO workflows run on the docker, local-docker, or kubernetes backend. The TAO-wide default minimums are:

  • NVIDIA driver >=580 (open kernel module preferred)
  • CUDA Toolkit >=13.0
  • NVIDIA Container Toolkit >=1.19.0
  • Docker engine — only installed for docker / local-docker backends and only when Docker is missing. The package picked depends on the distro family (docker.io on Debian-family by default, moby-engine / docker-ce from download.docker.com on RHEL-family, docker on SUSE-family). Pass --skip-docker-install to opt out.

The check is safe and read-only by default — it works on any Linux distribution because it only probes nvidia-smi, the CUDA toolkit path, the installed container-toolkit package version (via dpkg/rpm/the nvidia-ctk binary version), and the Docker daemon's NVIDIA runtime.

Installation must be explicitly authorized by the user and rerun with --install. The install path is automated for these distro families:

FamilyTested distrosManagerNotes
debianUbuntu 22.04 / 24.04, Debian 12 (and derivatives Pop!_OS, Mint, Zorin, Raspbian, KDE Neon, etc. via UBUNTU_CODENAME / VERSION_CODENAME)apt-getAdds NVIDIA cuda-keyring + Container Toolkit .list. Docker via docker.io (override $DOCKER_PACKAGE_DEBIAN).
rhelFedora 39+, RHEL / Rocky / AlmaLinux 9 and 10dnf (or yum)Adds NVIDIA cuda-<distro>.repo + Container Toolkit .repo. Docker via Fedora moby-engine when available, otherwise docker-ce from download.docker.com.
suseopenSUSE Leap 15, SLES 15zypperAdds the same NVIDIA .repo files. Docker via the distribution docker package.
other (Arch, Alpine, Gentoo, NixOS, FreeBSD, …)n/an/a--install exits with a clear error listing the version targets and the NVIDIA install-guide URLs. Install manually, then rerun --check-only.

Quick Start

From the skill bank root:

bash
# Check the local Docker backend host.
bash skills/platform/tao-setup-nvidia-gpu-host/scripts/setup-nvidia-gpu-host.sh --backend docker --check-only

# Install or repair after user approval.
bash skills/platform/tao-setup-nvidia-gpu-host/scripts/setup-nvidia-gpu-host.sh --backend docker --install

# Check a Kubernetes GPU worker host.
bash skills/platform/tao-setup-nvidia-gpu-host/scripts/setup-nvidia-gpu-host.sh --backend kubernetes --check-only

⚠️ Note — running non-interactively (agent/skill runs): a skill run has no terminal, so the installer's Continue? [y/N] prompt cannot be answered. After running --check-only to preview and getting the user's approval, append the assume-yes flag (--yes) to the --install command so it proceeds without a prompt — this auto-confirms installation of system packages (NVIDIA driver, CUDA Toolkit, NVIDIA Container Toolkit, and Docker for Docker backends) and modifies the host, so only do this on a host you control. A person running --install directly at a terminal gets the prompt instead.

Workflow Contract

Docker and Kubernetes workflows must run the check before submitting GPU work:

bash
SB="${TAO_SKILL_BANK_PATH:-${TAO_SKILL_BANK_ROOT:-$PWD}}"
SETUP_SCRIPT="${SB}/skills/platform/tao-setup-nvidia-gpu-host/scripts/setup-nvidia-gpu-host.sh"

bash "$SETUP_SCRIPT" --backend docker --check-only || {
  echo "MISSING: TAO GPU host runtime is not ready."
  echo "After user approval, run (append --yes for non-interactive agent runs):"
  echo "  bash \"$SETUP_SCRIPT\" --backend docker --install"
  exit 1
}

Never install silently. If the check fails, explain what is missing, ask the user to authorize the fix, then run the install command and rerun the check.

Model Runtime Override Contract

Platform defaults apply when a model has no override. A model that needs a different validated host stack declares it in references/skill_info.yaml:

yaml
runtime_requirements:
  gpu_host:
    min_driver_version: '<version>'
    min_cuda_version: '<version>'
    min_container_toolkit_version: '<version>'

Read those values before the final platform preflight and pass them to the matching --min-*-version flags. Model minimums take precedence for that workflow only; do not rewrite the platform defaults or requirements for other models. Version checks use numeric lower bounds, so later compatible releases pass. Always retain the selected-image GPU smoke test because a version bound cannot prove support for a particular GPU architecture.

What The Installer Does

The installer dispatches on the detected distribution family. On every supported family it adds NVIDIA's CUDA and Container Toolkit repositories (if missing), installs packages that satisfy the active minimums, optionally installs Docker, wires the NVIDIA Docker runtime, and adds the invoking user to the docker group.

Common steps (all families):

  1. Adds NVIDIA's CUDA repository if missing (apt cuda-keyring deb, cuda-<distro>.repo for dnf/zypper).
  2. Adds NVIDIA's Container Toolkit repository if missing (.list for apt, .repo for dnf/zypper).
  3. Installs the matching kernel header / devel package for the running kernel.
  4. Installs the current open-driver and Container Toolkit packages from the configured repositories plus the CUDA Toolkit package selected by --min-cuda-version, then verifies all three against the active minimums.
  5. For Docker backends and when Docker is missing, installs Docker (override / opt-out flags below), enables/starts the daemon, then runs nvidia-ctk runtime configure --runtime=docker and restarts Docker when systemctl is available.
  6. Adds the invoking user ($SUDO_USER if available, else $USER) to the docker group so subsequent shells can run docker without sudo — opt out with --skip-docker-group. The new group membership does not take effect in the current shell: log out and back in, or run newgrp docker in each new shell.
  7. Attempts modprobe nvidia so verification can pass before reboot.

Family-specific package selections:

Stepdebian-familyrhel-familysuse-family
Kernel headerslinux-headers-$(uname -r)kernel-devel-$(uname -r), kernel-headers-$(uname -r)kernel-default-devel
Drivercurrent nvidia-open (override: $NVIDIA_DRIVER_PACKAGE_DEBIAN)current nvidia-driver-cuda, kmod-nvidia-open-dkms (override: $NVIDIA_DRIVER_PACKAGE_RHEL, $NVIDIA_DRIVER_KMOD_RHEL)current nvidia-open-driver-G06-signed-kmp-default (override: $NVIDIA_DRIVER_PACKAGE_SUSE)
CUDA toolkitpackage derived from the active minimum, such as cuda-toolkit-13-0samesame
Container Toolkitcurrent nvidia-container-toolkit + base/tools/libs, then minimum-version validationsamesame
Dockerdocker.io (override: $DOCKER_PACKAGE_DEBIAN)moby-engine+moby-cli on Fedora when available, else docker-ce docker-ce-cli containerd.io from download.docker.comdocker
Show full SKILL.md (583 more words)Show less

Verification

After installation, verify:

bash
nvidia-smi
nvcc --version
docker info --format '{{json .Runtimes}}' | grep nvidia
sudo docker run --rm --runtime=nvidia --gpus all "$TAO_IMAGE" nvidia-smi -L

The detected driver, CUDA Toolkit, and Container Toolkit versions must meet the active TAO-wide or model-specific minimums. Then run the selected image's GPU smoke test; version comparison alone is not sufficient compatibility proof.

For a Cosmos backend, extend that smoke with the backend contract's Python and entrypoint checks. Cosmos Framework must execute /workspace/.venv/bin/python as a non-root UID, import cosmos_framework.callbacks.tao_status, find native torchrun, and verify the A100 PatchEmbed compatibility marker when the host reports compute capability 8.0. Cosmos-RL must resolve its requested action executable, import system PyAV for video workflows, resolve the restricted FFmpeg h264_cuvid decoder, load libnvcuvid.so.1, verify the backward-safe linear Qwen3-VL PatchEmbed marker, and verify its checkpoint loader accepts the prepared qwen3_vl directory. A container that only passes nvidia-smi is not ready for Cosmos training.

Kubernetes Notes

For self-managed Kubernetes clusters, run the host installer on every GPU worker node or bake the same package set into the node image before installing the NVIDIA GPU Operator or device plugin.

The workflow check also warns if kubectl is available but the cluster reports no nvidia.com/gpu allocatable capacity. In that case, install/configure the NVIDIA GPU Operator after the worker host runtime is ready:

bash
helm repo add nvidia https://helm.ngc.nvidia.com/nvidia
helm repo update
helm install --wait gpu-operator -n gpu-operator --create-namespace nvidia/gpu-operator

Managed Kubernetes providers may own driver installation through node images or GPU Operator policy. Do not overwrite a provider-managed GPU node without user approval and a rollback plan.

Failure Modes

Unsupported distribution family: --install automates debian-, rhel-, and suse-family hosts. On Arch, Alpine, Gentoo, NixOS, FreeBSD, or anything without /etc/os-release (e.g. macOS), the script exits with a clear error that lists the four version targets and the upstream NVIDIA install-guide URLs:

  • https://docs.nvidia.com/cuda/cuda-installation-guide-linux/
  • https://docs.nvidia.com/datacenter/cloud-native/container-toolkit/latest/install-guide.html
  • https://docs.docker.com/engine/install/

Install those four pieces using your distribution's package manager and rerun the script with --check-only to verify. The check is universally portable — it only queries the binaries / package databases — so once the runtime is in place the workflow contract is satisfied regardless of the underlying distro.

Unsupported Ubuntu/Debian derivative: When ID is e.g. pop, mint, zorin, raspbian, or another debian-family derivative, the script maps the host onto the upstream Ubuntu/Debian CUDA repo via UBUNTU_CODENAME / VERSION_CODENAME (focal/jammy/noble → Ubuntu 20.04/22.04/24.04; bullseye/bookworm/trixie → Debian 11/12/12). If the host's codename doesn't match a known upstream release, --install exits with the same manual-install guidance described above.

Docker not installed: --check-only reports MISSING: Docker is not installed and prints the exact rerun command appropriate to the detected distro family. The default --install path installs Docker (docker.io / moby-engine / docker-ce / docker depending on family), enables/starts the daemon, configures the NVIDIA runtime, and adds the invoking user to the docker group. If you prefer to manage Docker yourself, install it before rerunning the script or pass --skip-docker-install.

Docker installed but docker run still needs sudo: The script adds the invoking user to the docker group, but Linux only refreshes group membership on a new login session. Log out and back in, or run newgrp docker in each new shell, until the new membership is active.

Docker runtime still missing: Restart Docker, then rerun nvidia-ctk runtime configure --runtime=docker.

Detected version is below the active minimum: Rerun the same command with --install after approval, preserving any model-specific --min-*-version flags. Package-name environment overrides select distribution-specific driver packages but do not weaken the minimum-version checks.

Driver installed but nvidia-smi fails: Load the module with sudo modprobe nvidia or reboot. Secure Boot may require MOK enrollment on systems where it is enabled.

Kubernetes still has no GPU capacity: Confirm the driver works on each GPU node with nvidia-smi, then check the GPU Operator/device plugin pods and node labels.

© 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 7 other files (scripts, references) in skills/tao-setup-nvidia-gpu-host of NVIDIA/skills.

  • SKILL.md
  • BENCHMARK.md
  • config/skillspector-baseline.yaml
  • evals/evals.json
  • references/skill_info.yaml
  • scripts/setup-nvidia-gpu-host.sh
  • skill-card.md
  • skill.oms.sig

Open the folder on GitHubat commit 0e0d506

Compare with similar skills

Tao Setup Nvidia GPU Host 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.

Tao Setup Nvidia GPU Host compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Tao Setup Nvidia GPU Host this skillNVIDIA/skills3.5k—~3.4kAutomated safety check: NotesApache-2.0
Ama Logs Update Charts Release Notesmicrosoft/Docker-Provider173—~2.6kAutomated safety check: PassCustom licence
Alibabacloud Ecs Sec Userspacealiyun/alibabacloud-ecs-troubleshoot-skills148—~2.6kAutomated safety check: NotesApache-2.0
Crowdsecmagnus919/agent-skills111—~1.7kAutomated safety check: PassMIT
GitHub Runnermagnus919/agent-skills111—~1.7kAutomated safety check: PassMIT
Dotnet Debuggingnovotnyllc/dotnet-artisan233—~2.1kAutomated safety check: PassMIT

Similar skills

  • Ama Logs Update Charts Release Notes

    microsoft/Docker-Provider

    Official

    Prepare an ama-logs release PR: bump the image tag (X.Y.Z) across Helm charts, manifests, and Dockerfiles, and add a formatted ReleaseNotes.md entry.

    173 GitHub stars~2.6k tokensUpdated today
    DevOps & CloudAuto-check passed
  • Alibabacloud Ecs Sec Userspace

    aliyun/alibabacloud-ecs-troubleshoot-skills

    Linux 用户态安全入侵检测与取证工具,专为 AI Agent 设计。自动判断服务器是否被入侵, 提供完整证据链和可执行修复建议。51 个安全分析器覆盖进程/网络/认证/持久化/Rootkit/ 恶意软件/内存取证/容器逃逸等 12 类检测维度,10 个数据采集器全面采集系统状态, 映射 103+ MITRE ATT&CK 技术,支持 standalone/docker/k8s 三种部署模式。

    148 GitHub stars~2.6k tokensUpdated 1 mo ago
    DevOps & CloudAuto-check: notes
  • Crowdsec

    magnus919/agent-skills

    Deploy, configure, and operate CrowdSec Security Engine, cscli, remediation components, acquisition pipelines, and AppSec WAF.

    111 GitHub stars~1.7k tokensUpdated today
    DevOps & CloudAuto-check passed
  • GitHub Runner

    magnus919/agent-skills

    Deploy, manage, and troubleshoot self-hosted GitHub Actions runners.

    111 GitHub stars~1.7k tokensUpdated today
    DevOps & CloudAuto-check passed
  • Dotnet Debugging

    novotnyllc/dotnet-artisan

    Debugs Windows and Linux/macOS applications (native, .NET/CLR, mixed-mode) with WinDbg MCP (crash dumps, !analyze, !syncblk, !dlk, !runaway, !dumpheap, !gcroot, BSOD), dotnet-dump, lldb with SOS…

    233 GitHub stars~2.1k tokensUpdated 1 mo ago
    DevelopmentAuto-check passed
  • LangBot Deployment Guide

    langbot-app/LangBot

    Deploys and configures a LangBot instance with Docker Compose or Kubernetes, covering config.yaml, the Box sandbox runtime, the plugin runtime and the global API key.

    18k GitHub stars~1.2k tokensUpdated today
    DevOps & CloudAuto-check: notes

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 Tao Setup Nvidia GPU Host

What does Tao Setup Nvidia GPU Host do?

Host setup for TAO GPU backends. An agent skill from NVIDIA/skills. Tao Setup Nvidia GPU Host is an agent skill from NVIDIA/skills, published by the product's own GitHub organization. Host setup for TAO GPU backends.

When should I use Tao Setup Nvidia GPU Host?

Tao Setup Nvidia GPU Host fits situations like: the user asks to set up an NVIDIA GPU host; check TAO Docker GPU runtime; prepare a Kubernetes GPU worker for TAO.

How do I install Tao Setup Nvidia GPU Host in Claude Code?

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

How do I install Tao Setup Nvidia GPU Host in Codex?

Run `npx skills add NVIDIA/skills --skill tao-setup-nvidia-gpu-host -a codex`. Or copy the skill folder (skills/tao-setup-nvidia-gpu-host in NVIDIA/skills) into .agents/skills/tao-setup-nvidia-gpu-host in your project. Codex loads it when a task matches its description.

Can I use Tao Setup Nvidia GPU Host 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 tao-setup-nvidia-gpu-host -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/tao-setup-nvidia-gpu-host, .gemini/skills/tao-setup-nvidia-gpu-host, .github/skills/tao-setup-nvidia-gpu-host and .opencode/skills/tao-setup-nvidia-gpu-host in your project.

What does Tao Setup Nvidia GPU Host need to run?

Going by SKILL.md and its folder, Tao Setup Nvidia GPU Host needs a shell for the scripts in its folder and the command-line tools its instructions call (bash, docker and helm). Our summary lists: Python 3; A Bash shell; Docker. Its frontmatter pre-approves these tools: Read, Bash. Compatibility (from SKILL.md): Runs `--check-only` on any Linux distribution. `--install` automates Ubuntu 22.04/24.04 + Debian 12 (apt), Fedora + RHEL/Rocky/AlmaLinux 9/10 (dnf), and openSUSE Leap / SLES 15 (zypper). Requires sudo/root, internet access to NVIDIA package repositories (and download.docker.com on rhel-family), and an x86_64 or aarch64 (sbsa) host. Other distributions (Arch, Alpine, Gentoo, NixOS, …) get a clear error that names the version targets and the NVIDIA install-guide URL..

Does Tao Setup Nvidia GPU Host access the network?

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

Is Tao Setup Nvidia GPU Host safe to install?

Our automated static check of SKILL.md found notes only (runs commands with sudo; pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Tao Setup Nvidia GPU Host use?

Tao Setup Nvidia GPU Host 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 Tao Setup Nvidia GPU Host use?

About 3.4k tokens (SKILL.md is roughly 14k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 668 tokens, read only when the agent opens those files.

What are the alternatives to Tao Setup Nvidia GPU Host?

Skills that share tags, products or a category with Tao Setup Nvidia GPU Host: Ama Logs Update Charts Release Notes (microsoft/Docker-Provider, 173 stars), Alibabacloud Ecs Sec Userspace (aliyun/alibabacloud-ecs-troubleshoot-skills, 148 stars), Crowdsec (magnus919/agent-skills, 111 stars) and GitHub Runner (magnus919/agent-skills, 111 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Tao Setup Nvidia GPU Host?

NVIDIA (a GitHub organization, an official publisher) maintains it in NVIDIA/skills, which has 3,534 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.