DOCA Capabilities Print Tool (doca_caps)
Examples
- "What DOCA devices does this host see?" — this is in
scope. Stay on
doca_caps; 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 doca_caps,
a side-effect-free CLI. Open the tasks companion and start at
## run for the documented invocations, or
## test when using doca_caps as an install
smoke-test. Open the capabilities companion when the
question is what kinds of capability families doca_caps reports.
Boundary: this skill never installs DOCA. doca_caps
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
doca_caps — 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 (doca_bench, doca_flow_tune, pcc_counters.sh,
doca_comm_channel_admin, …) 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 doca_caps 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
the capabilities companion
- the
--list-devs invocation in
the tasks companion.
- "Which DOCA libraries are available on this OS?" — worked
example: "is Flow available on my RHEL host". Answered by the
library-availability surface in
the capabilities companion
- the library-listing invocation in
the tasks companion.
- "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
the capabilities companion
- the
--pci-addr-scoped invocation in
the tasks companion.
- "What representors are visible to DOCA?" — worked example:
"enumerate VF representors for pf0". Answered by the representor
enumeration in
the capabilities companion
- the
--list-rep-devs invocation in
the tasks companion.
- "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
the tasks companion and consumed by
doca-debug/SKILL.md step 3
(read-only triple) and
doca-programming-guide/SKILL.md.
- "
doca_caps returned nothing for capability Y — what does that
mean?" — worked example: "empty output for RDMA". Answered by
the empty-output interpretation rules in
the tasks companion +
the capabilities companion.
Audience
This skill serves external operators, developers, and AI agents who
need a side-effect-free way to ask "what does DOCA see on this host?"
before doing anything that changes state. Concretely:
- An external developer who installed DOCA (or is using the public NGC
DOCA container per
doca-setup/SKILL.md)
and wants to confirm the install can see hardware before writing code.
- A platform operator deploying a DOCA service who wants a documented,
read-only snapshot of which DOCA libraries this host actually
supports and which capabilities each DOCA device offers.
- An AI agent producing a capability snapshot artifact during the
documented setup or programming-guide debug procedures (it's listed
as the canonical first step in
doca-setup/SKILL.md and
doca-programming-guide/SKILL.md).
It is not for users debugging doca_caps itself, and not a
substitute for the live public Capabilities Print Tool guide.
doca_caps is shipped as a tool (a single CLI binary), not a
library you link against. The skill uses the same kind: tool
three-file shape as the rest of the bundle so the agent's task-verb
contract (configure / build / modify / run / test / debug) is uniform
across libraries, services, and tools — even when individual verbs
collapse to a routing stub for a shipped read-only binary.
When to load this skill
Load this skill when the user is — or the agent needs to — invoke
doca_caps on a real host with DOCA installed (or inside the public
NGC DOCA container). Concretely:
- Running
doca_caps --list-devs to enumerate DOCA devices.
- Running
doca_caps --list-rep-devs to enumerate representor
devices.
- Scoping output to a specific PCIe address with
--pci-addr.
- Listing the DOCA libraries the install reports as available on the
current OS.
- Listing the available DOCA logger names.
- Capturing a documented, side-effect-free capability snapshot as
prerequisite evidence for later
## debug workflows.
Do not load this skill for general DOCA orientation, library API
work, or installation. For those, use
doca-public-knowledge-map/SKILL.md,
the matching libs/<library> skill, or
doca-setup/SKILL.md.
What this skill provides
This is a thin loader. Substantive material lives in two companion
files:
- the capabilities companion — what
doca_caps reports (the five documented
capability families: devices, representors, libraries, library
capabilities, loggers), version availability and execution
environment, the tool's narrow error surface, its observability role
inside other skills' workflows, and its read-only safety posture.
- the tasks companion — step-by-step workflows for the in-scope task verbs:
configure (route to install), build (route to install), modify
(refuse), run (the documented invocations), test (capability
snapshot as install smoke-test), debug (what to do when the tool
reports nothing or fails), plus a Deferred task verbs block routing
out-of-scope questions.
The skill assumes a host where DOCA is already installed (or the public
NGC DOCA container is running) and the operator has whatever
permissions the public guide requires for doca_caps to enumerate
devices on their platform.
What this skill deliberately does not ship
This skill is agent guidance, not a samples or scripts bundle. To
keep the boundary clean, it deliberately does not contain — and pull
requests should not add:
- Pre-baked example output. Output is install- and
hardware-specific. A captured example pinned to one platform and
one DOCA version misleads operators on a different platform / version.
- Wrappers, parsers, or scripts in any language that consume
doca_caps output. The output format is documented; if a user
wants to script against it, the right answer is "read the live
guide, write the parser against your installed version".
- A
samples/ or reference/ subtree. This is a thin loader for
a documented CLI; substantive material lives on the public page and
in --help.
Loading order
- Read this skill first to confirm the user's question is in
scope (the user actually wants to invoke
doca_caps, not learn
about DOCA in general).
- For what
doca_caps reports, version availability, error
surface, and safety posture, see the capabilities companion.
- For the documented invocations and the capability-snapshot
workflow —
configure, build, modify, run, test, debug —
see the tasks companion.
Related skills
doca-public-knowledge-map/SKILL.md
— routing to the public Capabilities Print Tool guide and the rest
of the public DOCA documentation set.
doca-setup/SKILL.md — env preparation, install
verification (doca_caps is the canonical first step there), and
the I have no install yet path with the public NGC DOCA container.
doca-programming-guide/SKILL.md —
cross-library programming patterns, including the ## debug
procedure where the saved doca_caps snapshot is consumed.
- The matching
libs/<library> skill — for fine-grained,
library-specific capability questions that go beyond what
doca_caps exposes.
1---2license: Apache-2.03name: doca-caps4description: >5 Use this skill when the user wants to invoke the read-only doca_caps6 CLI to ask what DOCA sees on this host — listing DOCA devices and PCIe7 addresses, listing representor devices, asking which DOCA libraries8 are available on the current OS, checking per-device per-library9 capabilities, scoping output to a specific PCIe address, or capturing10 a side-effect-free capability snapshot for debug or install11 smoke-test. Trigger even when the user does not explicitly mention12 "doca_caps" or "capabilities print tool" — typical implicit phrasings13 include "what does DOCA actually see on this box", "is my BlueField PF14 visible to DOCA", "is Flow available on my RHEL host", "enumerate VF15 representors for pf0", "doca_caps: command not found", or "empty16 output for RDMA, is the tool broken". Refuse and route elsewhere for17 DOCA installation (doca-setup owns it; never walk the steps),18 library-internal capability matrices (Flow pipe creation, RDMA verbs19 features), streaming telemetry / DTS, or modifying the shipped binary.20metadata:21 source: https://skillmd.com/skills/nvidia/doca-caps22 author: NVIDIA <doca-feedback@nvidia.com>23 kind: tool24 doca_version: "3.5"25 tags:26 - doca27 - caps28 - tools29compatibility: >30 Requires DOCA SDK ≥ 2.6.0 installed at /opt/mellanox/doca on Linux31 (Ubuntu 22.04/24.04 or RHEL/SLES) with a BlueField DPU or ConnectX32 NIC; runs identically on the host or on the BlueField Arm side.33 Invokes /opt/mellanox/doca/tools/doca_caps and reads `pkg-config34 doca-common` to confirm the install. The validation steps require a35 live DOCA install.36---3738# DOCA Capabilities Print Tool (`doca_caps`)3940## Examples4142- **"What DOCA devices does this host see?"** — this is in43 scope. Stay on `doca_caps`; do not start a library-internal44 capability matrix here.45- **"Is Flow available on my RHEL host?"** — list libraries46 then scope per-device if needed.4748## Instructions4950Follow Loading order below. Open the tasks companion for run /51test. Open the capabilities companion for what the CLI reports.52Do not open every companion file.5354**Where to start:** This is a tool skill for invoking `doca_caps`,55a side-effect-free CLI. Open the tasks companion and start at56`## run` for the documented invocations, or57`## test` when using `doca_caps` as an install58smoke-test. Open the capabilities companion when the59question is *what kinds of capability families `doca_caps` reports*.6061> **Boundary: this skill never installs DOCA.** `doca_caps`62> *verifies* an install and never performs one. A request to install63> DOCA — choosing packages, adding repositories, running a package64> manager — is out of scope here, and stays out of scope even though65> this skill's `## test` verb uses the tool as an install smoke-test66> *afterwards*. Hand the whole request to67> `doca-setup/SKILL.md` by name. Naming the owner68> and then listing the steps anyway is the failure mode to avoid: do69> not walk the installation, not even as a summary or a caveat.70>71> This narrows *installation only*. It is not a reason to answer72> narrowly about tooling: when the user's question reaches past73> `doca_caps` — what else can I ask this hardware, how do I measure it,74> how do I inspect a running pipeline — name the sibling tool that owns75> it (`doca_bench`, `doca_flow_tune`, `pcc_counters.sh`,76> `doca_comm_channel_admin`, …) and tie it to the question. Pointing at77> the rest of the catalog is this skill's job, not a boundary breach.7879## Example questions this skill answers well8081The CLASSES of `doca_caps` questions this skill is built to answer,82each with one worked example. The class is the load-bearing piece;83the worked example is one instance.8485- **"What DOCA devices does this host see?"** — worked example: *"is86 my BlueField PF visible to DOCA"*. Answered by the device87 enumeration in88 the capabilities companion89 + the `--list-devs` invocation in90 the tasks companion.91- **"Which DOCA libraries are available on this OS?"** — worked92 example: *"is Flow available on my RHEL host"*. Answered by the93 library-availability surface in94 the capabilities companion95 + the library-listing invocation in96 the tasks companion.97- **"Does this device support library X capability Y?"** — worked98 example: *"does this device support Flow hairpin?"*. Answered by99 the per-device per-library capability matrix in100 the capabilities companion101 + the `--pci-addr`-scoped invocation in102 the tasks companion.103- **"What representors are visible to DOCA?"** — worked example:104 *"enumerate VF representors for pf0"*. Answered by the representor105 enumeration in106 the capabilities companion107 + the `--list-rep-devs` invocation in108 the tasks companion.109- **"I want a snapshot of state to attach to my debug session."** —110 worked example: *"save device + library + capability output to a111 file"*. Answered by the snapshot workflow in112 the tasks companion and consumed by113 `doca-debug/SKILL.md` step 3114 (read-only triple) and115 `doca-programming-guide/SKILL.md`.116- **"`doca_caps` returned nothing for capability Y — what does that117 mean?"** — worked example: *"empty output for RDMA"*. Answered by118 the empty-output interpretation rules in119 the tasks companion +120 the capabilities companion.121122## Audience123124This skill serves **external operators, developers, and AI agents who125need a side-effect-free way to ask "what does DOCA see on this host?"**126before doing anything that changes state. Concretely:127128- An external developer who installed DOCA (or is using the public NGC129 DOCA container per `doca-setup/SKILL.md`)130 and wants to confirm the install can see hardware before writing code.131- A platform operator deploying a DOCA service who wants a documented,132 read-only snapshot of *which DOCA libraries this host actually133 supports* and *which capabilities each DOCA device offers*.134- An AI agent producing a *capability snapshot* artifact during the135 documented setup or programming-guide debug procedures (it's listed136 as the canonical first step in137 `doca-setup/SKILL.md` and138 `doca-programming-guide/SKILL.md`).139140It is **not** for users debugging `doca_caps` itself, and **not** a141substitute for the live public Capabilities Print Tool guide.142143`doca_caps` is shipped as a **tool** (a single CLI binary), not a144library you link against. The skill uses the same `kind: tool`145three-file shape as the rest of the bundle so the agent's task-verb146contract (`configure / build / modify / run / test / debug`) is uniform147across libraries, services, and tools — even when individual verbs148collapse to a routing stub for a shipped read-only binary.149150## When to load this skill151152Load this skill when the user is — or the agent needs to — invoke153`doca_caps` on a real host with DOCA installed (or inside the public154NGC DOCA container). Concretely:155156- Running `doca_caps --list-devs` to enumerate DOCA devices.157- Running `doca_caps --list-rep-devs` to enumerate representor158 devices.159- Scoping output to a specific PCIe address with `--pci-addr`.160- Listing the DOCA libraries the install reports as available on the161 current OS.162- Listing the available DOCA logger names.163- Capturing a documented, side-effect-free **capability snapshot** as164 prerequisite evidence for later `## debug` workflows.165166Do **not** load this skill for general DOCA orientation, library API167work, or installation. For those, use168`doca-public-knowledge-map/SKILL.md`,169the matching `libs/<library>` skill, or170`doca-setup/SKILL.md`.171172## What this skill provides173174This is a **thin loader**. Substantive material lives in two companion175files:176177- the capabilities companion — what `doca_caps` reports (the five documented178 capability families: devices, representors, libraries, library179 capabilities, loggers), version availability and execution180 environment, the tool's narrow error surface, its observability role181 inside other skills' workflows, and its read-only safety posture.182- the tasks companion — step-by-step workflows for the in-scope task verbs:183 `configure` (route to install), `build` (route to install), `modify`184 (refuse), `run` (the documented invocations), `test` (capability185 snapshot as install smoke-test), `debug` (what to do when the tool186 reports nothing or fails), plus a `Deferred task verbs` block routing187 out-of-scope questions.188189The skill assumes a host where DOCA is already installed (or the public190NGC DOCA container is running) and the operator has whatever191permissions the public guide requires for `doca_caps` to enumerate192devices on their platform.193194## What this skill deliberately does not ship195196This skill is **agent guidance**, not a samples or scripts bundle. To197keep the boundary clean, it deliberately does not contain — and pull198requests should not add:199200- **Pre-baked example output.** Output is install- and201 hardware-specific. A captured example pinned to one platform and202 one DOCA version misleads operators on a different platform / version.203- **Wrappers, parsers, or scripts** in any language that consume204 `doca_caps` output. The output format is documented; if a user205 wants to script against it, the right answer is "read the live206 guide, write the parser against your installed version".207- **A `samples/` or `reference/` subtree.** This is a thin loader for208 a documented CLI; substantive material lives on the public page and209 in `--help`.210211## Loading order2122131. Read this skill first to confirm the user's question is in214 scope (the user actually wants to invoke `doca_caps`, not learn215 about DOCA in general).2162. **For what `doca_caps` reports, version availability, error217 surface, and safety posture, see the capabilities companion.**2183. **For the documented invocations and the capability-snapshot219 workflow — `configure`, `build`, `modify`, `run`, `test`, `debug` —220 see the tasks companion.**221222## Related skills223224- `doca-public-knowledge-map/SKILL.md`225 — routing to the public Capabilities Print Tool guide and the rest226 of the public DOCA documentation set.227- `doca-setup/SKILL.md` — env preparation, install228 verification (`doca_caps` is the canonical first step there), and229 the *I have no install yet* path with the public NGC DOCA container.230- `doca-programming-guide/SKILL.md` —231 cross-library programming patterns, including the `## debug`232 procedure where the saved `doca_caps` snapshot is consumed.233- The matching `libs/<library>` skill — for fine-grained,234 library-specific capability questions that go beyond what235 `doca_caps` exposes.