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 "capa
SkillScore91Maintained
Automatic
◆DevOps & SRE pack
Last verified 8/12/2026
What it changes
Passed 20 of 22 test cases with the skill, and 11 of 22 without it.
Without skill50%
With skill91%
Checks it passed that the model alone missed
Recommends using the --list-devs flag.
Refuses to provide source code modification or build steps for doca_caps.
Explains that doca_caps is a read-only, pre-built binary provided by NVIDIA DOCA.
and 9 more in the full report
9 fixed11 passed either way2 still failing0 broke
Pass-rate lift
+41 pp
Tokens
+60%
Agent turns
0%
Response time
-44%
Model gemini-3.6-flashMeasured 8/12/2026v120 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 9
Prompt
I just set up a host with DOCA installed and need to check hardware visibility. What is the CLI invocation using doca_caps to list all DOCA-compatible network devices detected on the host?
What was checked, without and with the skill
Checked
Without skill
With skill
Recommends using the --list-devs flag.
Missed
Passed
Does not recommend running doca_caps without arguments to list devices.
Passed
Passed
case-01 · gemini-3.6-flash · 8/12/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md168 linessingle file
DOCA Capabilities Print Tool (doca_caps)
Where to start: This is a tool skill for invoking doca_caps,
a side-effect-free CLI. Open TASKS.md and start at
## run for the documented invocations, or
## test when using doca_caps as an install
smoke-test. Open CAPABILITIES.md when the
question is what kinds of capability families doca_caps reports.
If DOCA is not installed yet, route to
doca-setup first.
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
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
Use this skill to enumerate host↔DPU DOCA comch (formerly Comm Channel) servers and connections via the shipped doca_comm_channel_admin binary — listing comch-capable devices and decoding the per-device server / connection table (server name, PID, in-use / max, PCIe address). The shipped binary is a SINGLE-SHOT SCAN-AND-PRINT tool with no registered arguments — NO list / inspect / drain / restart subcommands; one inventory pass over every comch-capable doca_dev on this side. Channel reset / drai