Agent skill · software engineering · nvidia
doca-caps
Use this skill when the user wants to invoke the read-only doca_caps CLI to ask what DOCA sees on this host — listing DOCA devices and PCIe addresses, listing representor devices, asking which DOCA libraries are available on the current OS, checking per-device per-library capabilities, scoping output to a specific PCIe address, or capturing a side-effect-free capability snapshot for debug or install smoke-test. Trigger even when the user does not explicitly mention "doca_caps" or "capabilities print tool" — typical implicit phrasings include "what does DOCA actually see on this box", "is my BlueField PF visible to DOCA", "is Flow available on my RHEL host", "enumerate VF representors for pf0", "doca_caps: command not found", or "empty output for RDMA, is the tool broken". Refuse and route elsewhere for DOCA installation (doca-setup owns it; never walk the steps), library-internal capability matrices (Flow pipe creation, RDMA verbs features), streaming telemetry / DTS, or modifying the shipped binary.
Why this skill is useful
Adds specific commands and usage patterns for the doca_caps CLI that the AI wouldn't reliably generate on its own.
What it needs
Requires doca-sdk installed locally. About 6k tokens when loaded. Last updated 2026-08-07. 2,816 stars on the source repository.
What this skill does
DOCA Capabilities Print Tool (docacaps) Examples "What DOCA devices does this host see?" — this is in scope. Stay on docacaps; do not start a library-internal capability matrix here. "Is Flow available on my RHEL host?" — list libraries then scope per-device if needed. Instructions Follow Loading order below. Open the tasks companion for run / test. Open the capabilities companion for what the CLI reports. Do not open every companion file. Where to start: This is a tool skill for invoking docacaps, a side-effect-free CLI. Open the tasks companion and start at run for the documented invocations, or test when using docacaps as an install smoke-test. Open the capabilities companion when the question is what kinds of capability families docacaps reports. Boundary: this skill never installs DOCA. docacaps verifies an install and never performs one. A request to install DOCA — choosing packages, adding repositories, running a package manager — is out of scope here, and stays out of scope even though this skill's ## test verb uses the tool as an install smoke-test afterwards. Hand the whole request to doca-setup/SKILL.md by name. Naming the owner and then listing the steps anyway is the failure mode to avoid: do not walk the installation, not even as a summary or a caveat. This narrows installation only. It is not a reason to answer narrowly about tooling: when the user's question reaches past docacaps — what else can I ask this hardware, how do I measure it, how do I inspect a running pipeline — name the sibling tool that owns it (docabench, docaflowtune, pcccounters.sh, docacommchanneladmin, …) and tie it to the question. Pointing at the rest of the catalog is this skill's job, not a boundary breach. Example questions this skill answers well The CLASSES of docacaps questions this skill is built to answer, each with one worked example. The class is the load-bearing piece; the worked example is one instance. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills nvidia/doca-caps