Agent skill · 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 a debug session 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, library-internal capability matrices (Flow pipe creation, RDMA verbs features), streaming telemetry / DTS, or modifying the shipped binary — those belong to other skills.
What it needs
About 5k tokens when loaded.
What this skill does
DOCA Capabilities Print Tool (docacaps) Where to start: This is a tool skill for invoking docacaps, a side-effect-free CLI. Open TASKS.md and start at run for the documented invocations, or test when using docacaps as an install smoke-test. Open CAPABILITIES.md when the question is what kinds of capability families docacaps reports. If DOCA is not installed yet, route to doca-setup first. 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. "What DOCA devices does this host see?" — worked example: "is my BlueField PF visible to DOCA". Answered by the device enumeration in CAPABILITIES.md ## Capabilities and modes the --list-devs invocation in TASKS.md ## run. "Which DOCA libraries are available on this OS?" — worked example: "is Flow available on my RHEL host". Answered by the library-availability surface in CAPABILITIES.md ## Capabilities and modes the library-listing invocation in TASKS.md ## run. "Does this device support library X capability Y?" — worked example: "does this device support Flow hairpin?". Answered by the per-device per-library capability matrix in CAPABILITIES.md ## Capabilities and modes the --pci-addr-scoped invocation in TASKS.md ## run. "What representors are visible to DOCA?" — worked example: "enumerate VF representors for pf0". Answered by the representor enumeration in CAPABILITIES.md ## Capabilities and modes the --list-rep-devs invocation in TASKS.md ## run. "I want a snapshot of state to attach to my debug session." — worked example: "save device + library + capability output to a file". Answered by the snapshot workflow in TASKS.md ## test and consumed by doca-debug ## test step 3 (read-only triple) and doca-programming-guide ## debug. "docacaps returned nothing for capability Y — what does that mean?" — worked example: "empty output for RDMA". …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills NVIDIA/doca-caps