Invokes the read-only DOCA capabilities CLI to enumerate devices, representors, available libraries, and hardware capabilities on a host.
- GitHub stars
- 3,934
- Files
- 8
- Last commit
- Nov 11, 2026
- License
- Apache-2.0
- Allowed tools
- —
What does the doca-caps skill do?
doca-caps invokes the read-only DOCA capabilities CLI to enumerate devices, representors, available libraries, and hardware capabilities on a host.
Summary generated from the skill's SKILL.md.
About the doca-caps skill
Enumerating hardware and software capabilities on a Linux host is what doca-caps enables for developers and platform operators. This skill acts as a thin loader for the read-only doca_caps CLI, allowing an agent to query what the DOCA SDK perceives on a specific system. It is used to list DOCA devices, identify PCIe addresses, enumerate representor devices, and check which DOCA libraries are available on the current operating system.
An agent should load this skill when a user needs to verify a hardware installation or confirm if specific features like Flow are available on a host. It produces side-effect-free snapshots of device and library capabilities, which serve as essential evidence for debugging or installation smoke-tests. The tool relies on a pre-installed DOCA SDK at /opt/mellanox/doca and works on BlueField DPUs or ConnectX NICs. It is strictly for inspection and does not perform installations or modify system state.
What an agent can do with it
- 1Verify hardware visibilityCheck if a specific BlueField PF is visible to the DOCA environment.
- 2Confirm library availabilityDetermine if a specific DOCA library is available on a RHEL host.
- 3Inspect device capabilitiesVerify if a specific device supports a particular library capability like Flow hairpin.
- 4Capture debug snapshotsSave a complete report of devices, libraries, and capabilities to a file for troubleshooting.
- 5Enumerate representorsList the VF representors associated with a specific physical function.
Written from the skill's SKILL.md. Every use case is checked against a quote from it.
How to install the doca-caps skill
Each command copies the skill folder into the client's skills directory. Restart the client or start a new session to load it.Install the doca-caps skill in Claude Code
~/.claude/skills/doca-caps/SKILL.md
$ npx degit NVIDIA/skills/skills/doca-caps ~/.claude/skills/doca-capsInstall the doca-caps skill in Claude Code (project)
.claude/skills/doca-caps/SKILL.md
$ npx degit NVIDIA/skills/skills/doca-caps .claude/skills/doca-capsInstall the doca-caps skill in Codex
~/.agents/skills/doca-caps/SKILL.md
$ npx degit NVIDIA/skills/skills/doca-caps ~/.agents/skills/doca-capsInstall the doca-caps skill in Gemini CLI
~/.gemini/skills/doca-caps/SKILL.md
$ npx degit NVIDIA/skills/skills/doca-caps ~/.gemini/skills/doca-capsInstall the doca-caps skill in Claude.ai
npx degit NVIDIA/skills/skills/doca-caps doca-caps && zip -r doca-caps.zip doca-caps # claude.ai → Customize → Skills → + → Create skill → Upload a skill → doca-caps.zip
Automated checks
Ran Nov 15, 2026Full report →Passed our automated checks. That is not a security audit: read the scripts before you let an agent run them. How checks work
- Source repository linked and reachablenvidia/skills/skills/doca-caps is public and reachablegithub.com/nvidia/skills/tree/HEAD/skills/doca-caps ↗Pass
- Open source license (OSI)Apache-2.0spdx.org/licenses/Apache-2.0.html ↗Pass
- Commit or release in the last yearLast commit 2026-11-11github.com/nvidia/skills/commits ↗Pass
- No download-and-run or credential theft in scriptsNo scripts in the skill folderPass
- No hidden instructions in SKILL.mdNo override phrases, safeguard switches, credential requests or hidden charactersgithub.com/nvidia/skills/blob/HEAD/skills/doca-caps/SKILL.md ↗Pass
- Pre-approved tools are scopedNo pre-approved tools; the agent asks before using onegithub.com/nvidia/skills/blob/HEAD/skills/doca-caps/SKILL.md ↗Pass
- SKILL.md follows the Agent Skills formatValid name and description; says when to use it; 235 linesgithub.com/nvidia/skills/blob/HEAD/skills/doca-caps/SKILL.md ↗Pass
SKILL.md
View on GitHubDOCA 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_capsverifies 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## testverb uses the tool as an install smoke-test afterwards. Hand the whole request todoca-setup/SKILL.mdby 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-devsinvocation in the tasks companion.
- the
- "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.
- the
- "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-devsinvocation in the tasks companion.
- the
- "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.mdstep 3 (read-only triple) anddoca-programming-guide/SKILL.md. - "
doca_capsreturned 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.mdanddoca-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-devsto enumerate DOCA devices. - Running
doca_caps --list-rep-devsto 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
## debugworkflows.
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_capsreports (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 aDeferred task verbsblock 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_capsoutput. 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/orreference/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_capsreports, 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_capsis 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## debugprocedure where the saveddoca_capssnapshot is consumed.- The matching
libs/<library>skill — for fine-grained, library-specific capability questions that go beyond whatdoca_capsexposes.
Files in this skill
8doca-caps skill questions
How do I install the doca-caps skill in Claude Code?
Run npx degit NVIDIA/skills/skills/doca-caps ~/.claude/skills/doca-caps. Claude Code loads skills from ~/.claude/skills (all projects) or .claude/skills (one project) and uses a skill when its description matches the task.
Which clients can use the doca-caps skill?
Any client that reads the Agent Skills format: Claude Code, Codex, Gemini CLI and claude.ai (upload as a ZIP). Scripts in the skill run only where the client allows code execution.
What can doca_caps enumerate on a host?
It can list DOCA devices and PCIe addresses, representor devices, available DOCA libraries, and per-device per-library capabilities.
Can this tool be used to install DOCA?
No, doca_caps is a read-only tool used to verify an existing installation; it does not perform installations.
What are the system requirements for using doca_caps?
It requires DOCA SDK ≥ 2.6.0 installed on Linux (Ubuntu, RHEL, or SLES) with a BlueField DPU or ConnectX NIC.