NVIDIA/skills is a catalogue of portable instruction sets that teach coding agents how to use NVIDIA software for robotics, simulation, CUDA, retrieval-augmented generation, and related workflows. Developers install these skills in agents such as Claude Code or Codex, while the catalogue mirrors skills maintained in separate NVIDIA product repositories.
Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add NVIDIA/skills --skill doca-bare-metal-deploymentgit clone --depth 1 https://github.com/NVIDIA/skillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/nvidia/skills/doca-bare-metal-deployment)<a href="https://agentmods.dev/skills/nvidia/skills/doca-bare-metal-deployment"><img src="https://agentmods.dev/badge/skills/nvidia/skills/doca-bare-metal-deployment/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/nvidia/skills/doca-bare-metal-deployment"><img src="https://agentmods.dev/badge/skills/nvidia/skills/doca-bare-metal-deployment.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00250 | $0.02948 |
| Opus 5 | $0.00125 | $0.01474 |
| Sonnet 5 | $0.00050 | $0.00590 |
| Haiku 4.5 | $0.00025 | $0.00295 |
Grade A, and why
doca-bare-metal-deployment scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 235 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DOCA bare-metal deployment
Where to start: This skill is the bundle's home for operating
a DOCA-linked application binary directly on hardware — no
container, no kubelet, no static-pod manifest. It is the parallel
of doca-container-deployment
for the non-container path. If the user has a DOCA-linked binary
they built (per the canonical workflow in
doca-programming-guide)
and they want to know how to actually run it on the host or on
the BlueField Arm cores correctly, open
TASKS.md and start at
## configure. If the question is what
shape does the bare-metal runtime even have and what is the
deployment contract, start at CAPABILITIES.md.
If the user is not yet sure whether their target system shape is
the container path or the bare-metal path, route the recognition
step to doca-setup first; only return
here once bare-metal is the confirmed shape.
Audience
This skill serves external DOCA developers and operators who have a DOCA-linked application binary they built and want to run it directly on hardware — i.e., people who already have:
- a DOCA-linked application binary they built per
doca-programming-guide ## build, - a real BlueField NIC and a host that talks to it (the host x86 path — DOCA host install on the host talks to the BlueField NIC over PCIe), OR a BlueField with a console or SSH to the Arm side (the BlueField Arm bare-metal path — DOCA installed on the DPU Arm cores; the binary runs there directly), and
- a desire to RUN that binary directly on the hardware, not inside a kubelet-standalone-managed container.
It is not for:
- kernel-driver developers contributing to
mlx5_*or the BlueField OS, - DOCA library contributors (those changes go to the internal DOCA tree, not to a bare-metal deployment),
- full-Kubernetes-cluster operators managing a fleet of
BlueFields (the bundle covers
doca-container-deploymentfor the single-host kubelet-standalone shape; fleet/production-scale deployment is fleet-orchestration scope — route to the orchestration entry-point indoca-public-knowledge-map ## Deploying DOCA services at scale(DPF / Network Operator / Launch Kit), not hand-rolled static-pod loops), - fresh-laptop-no-hardware users with no DOCA install yet — those
belong on
doca-setup ## no-install.
What ships with it
7 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 9d ago First seen · 235 lines · 250 tokens per session scan A fd7304c1e9a6
doca-bare-metal-deployment is a skill published in the GitHub repository NVIDIA/skills (3,236 stars, last pushed yesterday), licensed Apache-2.0. It adds 250 tokens to every session and 2,948 once invoked, about $0.0013 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
spark-environment-setup
Set up a working ML training/inference environment on NVIDIA DGX Spark (GB10, aarch64, CUDA 13). Use when installing PyTorch/Unsloth/TRL/vLLM on DGX Spark, hitting libcudart or wheel-ABI errors on aarch64, or choosing between NGC containers and bare pip installs.
spark-training-gotchas
Preflight and diagnose the ten known failure modes for ML training on NVIDIA DGX Spark. Use when a training run on DGX Spark fails to start, OOMs below the 128GB limit, slows down mid-run, or before any multi-hour training job on GB10.
terraform-module-library
Build reusable Terraform modules for AWS, Azure, GCP, and OCI infrastructure following infrastructure-as-code best practices. Use when creating infrastructure modules, standardizing cloud provisioning, or implementing reusable IaC components.
hyperpod-version-checker
Check and compare software component versions on SageMaker HyperPod cluster nodes - NVIDIA drivers, CUDA toolkit, cuDNN, NCCL, EFA, AWS OFI NCCL, GDRCopy, MPI, Neuron SDK (Trainium/Inferentia), Python, and PyTorch. Use when checking component versions, verifying CUDA/driver compatibility, detecting version mismatches…
technical-troubleshooting
Provide setup, troubleshooting, and maintenance guidance. Use when the user reports a device that won't power on, connectivity issues, setup questions, overheating, or maintenance concerns.
gpu-optimizer
GPU optimization for consumer NVIDIA GPUs (8-24GB VRAM) covering mixed precision, gradient checkpointing, XGBoost GPU, CuPy/cuDF migration, and torch.compile. Triggers on: "optimize GPU training", "speed up CUDA", "reduce OOM", "migrate NumPy to CuPy", "manage GPU memory", "benchmark PyTorch".