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-flow-dpa-providergit 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-flow-dpa-provider)<a href="https://agentmods.dev/skills/nvidia/skills/doca-flow-dpa-provider"><img src="https://agentmods.dev/badge/skills/nvidia/skills/doca-flow-dpa-provider/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-flow-dpa-provider"><img src="https://agentmods.dev/badge/skills/nvidia/skills/doca-flow-dpa-provider.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.00244 | $0.04530 |
| Opus 5.5 | $0.00098 | $0.01812 |
| Sonnet 5.5 | $0.00049 | $0.00906 |
| Haiku 4.5 | $0.00024 | $0.00453 |
Grade A, and why
doca-flow-dpa-provider 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 5d 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 — 390 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DOCA Flow DPA Provider
Examples
- "DPA kernel never sees entries in the exported pipe." — this is in scope. Honor the export handshake order; do not rebuild the Flow pipe from the DPA kernel.
- "BAD_STATE from
_pipe_export." — finish_export_prepareand add entries before_export. Do not skip to the device address.
Instructions
Follow Loading order below. Open the tasks companion for configure / export / debug. Open the capabilities companion for queue types and the handshake.
Where to start: This skill assumes DOCA is already
installed, the user has a BlueField with a DPA processor that
the host can see through DOCA, the user already programs DOCA
Flow from the host (doca-flow) and already runs DPA kernels
from the host (doca-dpa / DPACC compiler), and the user is
doing hands-on DPA Flow Provider work: using
doca-flow-dpa-provider to export an existing DOCA Flow pipe
or external resource into the DPA address space so a DPA
kernel can manipulate it inline. Open the tasks companion
if the user wants to do something (configure / build /
modify / run / test / debug); open
the capabilities companion when the question is
what can the provider express on this version + this
BlueField generation. If the user has not installed DOCA yet,
route to doca-setup/SKILL.md first; if
the user has not stood up a host-side Flow pipe yet, route to
doca-flow/SKILL.md first; if the user has
not stood up host-side DPA execution yet, route to
doca-dpa/SKILL.md first.
Example questions this skill answers well
The CLASSES of DPA Flow Provider questions this skill is built to answer, each with one worked example. The agent should treat the class as the load-bearing piece — the worked example is a single instance.
- "Is this library even the right tool for what I want?" —
worked example: "I want my DOCA Flow pipe to be readable
from a DPA kernel, OR I want to do something fancier than
the host-side
doca-flowAPI exposes". Answered by the decision rule inCapabilities and modes
("three-program model: when this library is the right surface vs pure host-side Flow vs pure DPA"). Most first-time askers do NOT need this library; the skill's first job is to confirm they do. - "How do I export an existing DOCA Flow pipe to the DPA
side?" — worked example: "I have a Flow pipe with a
counter on every entry; I want a DPA kernel to read those
counters inline and decide what to do next". Answered by
the host-side export sequence in
Capabilities and modes
- the bring-up steps in
configure.
- "How do I drive the exported pipe from inside the DPA
kernel?" — worked example: "I have the device address of
an exported hash pipe; how do I disable an entry from the
DPA, and how do I know the operation completed?".
Answered by the device-side API surface in
Capabilities and modes
("DPA-side consumption") + the host-side queue allocation- DPA-side polling step in
run.
- "What does this
DOCA_ERROR_*from adoca_flow_dpa_*call mean, and is the bug on the host side, on the DPA side, or in the export handshake between them?" — worked example: "DOCA_ERROR_BAD_STATEfromdoca_flow_dpa_pipe_export". Answered by the provider overlay on the cross-library taxonomy inError taxonomy
- the layered ladder in
debug that escalates to
doca-debug/SKILL.md. - "Why did my pipe export succeed but my DPA kernel never
sees entries?" — worked example: "I called
doca_flow_dpa_pipe_export_prepareAFTER adding entries to the pipe". Answered by the lifecycle ordering rule inSafety policy
- the staged-export workflow in
test.
- "Is the host-side / DPA-side provider API I'm reading
about on my installed DOCA?" — worked example: "is the
three-queue-type
doca_flow_dpa_queues_createavailable against the DOCA + DPACC versions on this host, or am I still on the olderdoca_flow_dpa_pipe_queues-based surface?". Answered by the version-compatibility overlay inVersion compatibility
which cross-links the canonical detection chain indoca-version/SKILL.mdand adds the provider-specific overlay inherited fromdoca-dpa/SKILL.md.
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.
- 5d ago Changed · +1 lines a89e342042e0
- 13d ago Changed · +18 lines 027c94fa9c68
- 1mo ago First seen · 371 lines · 244 tokens per session scan A 75fc7c6223df
doca-flow-dpa-provider is a skill published in the GitHub repository NVIDIA/skills (3,763 stars, last pushed today), licensed Apache-2.0. It adds 244 tokens to every session and 4,530 once invoked, about $0.0010 per session on Opus 5.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-09-03.
Other skills, from other repositories
desktop-and-local-ipc-security
Use when the diff adds or changes a loopback HTTP or WebSocket server, a bind address, a Unix socket, named pipe, XPC or D-Bus service, an Electron or Tauri main-process handler, a custom URL scheme or file association, a privileged helper or updater, or code that spawns tools inside directories a user or download…
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.
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.
screen-mockup-html
Use when you draw a screen as HTML mockup documents (one per variant) - the sanitizer-safe recipe, phone and wide frames, the states grid, static control states, and the loopback self-check with screenshots at 375, 768 and 1440 attached to the task.
responsive-layout
Use when you build or change a layout, page, section, navigation, table, form or image - mobile-first rules, breakpoints and the overflow traps.