DOCA Verbs
Examples
- "Should I use doca-verbs or doca-rdma?" — ordinary RDMA data
movement with no raw QP / CQ / WR / SRQ / Address-Handle attribute
named is out of scope — route to
doca-rdma/SKILL.md.
- "I need a raw QP attribute the task API does not expose." — stay
here. Use only the installed
doca_verbs.h surface.
Instructions
Follow ## Loading order. Open only the companion
that matches the question.
STOP — most RDMA tasks do NOT belong here
If the task is general RDMA data movement (send / receive / read /
write / atomic between endpoints) and the user did not name a raw
QP / CQ / work-request / SRQ / Address-Handle attribute the
higher-level API cannot express, this skill is out of scope —
route to doca-rdma/SKILL.md and stop after
explaining the boundary. Unless doca-rdma guidance is loaded, do not
infer its implementation APIs; conceptual terms (QP, CQ, connection,
send, receive) are not implementation API names.
Loading this skill is never a license to hand-roll libibverbs /
librdmacm. A general-RDMA deliverable whose ldd shows no
libdoca_rdma is a failed task — the same rule
doca-rdma/SKILL.md enforces. Raw doca_verbs_* is in
scope only for the narrow attribute-level needs below; everything else
climbs back up.
Where to start: This skill is the raw-verbs escape hatch beneath
the higher-level DOCA libraries (doca-rdma/SKILL.md,
doca-eth/SKILL.md, doca-rmax/SKILL.md).
The agent's first job is to confirm the user actually needs to drop
down — most users do not; the right answer is almost always "stay in
the higher-level library". Open CAPABILITIES.md
for what the verbs surface exposes and the libibverbs boundary; open
TASKS.md once raw verbs is confirmed. If DOCA is not
installed, route to doca-setup/SKILL.md first.
Non-negotiable answer checklist
For every in-scope porting, lifecycle, or debugging answer, do not declare
it complete until it explicitly states all applicable items below:
doca_verbs_context is the DOCA Core context owning the verbs
surface; it wraps the doca_dev, integrates with the progress
engine, and owns the per-object PD / MR / CQ / QP lifecycle in
CAPABILITIES.md ## Capabilities and modes.
- A submit-time success followed by
DOCA_ERROR_IO_FAILED is
diagnosed from the completion-queue entry's error field — not the
submit return — before recommending retries or code changes.
- The answer selects exactly one completion path: progress engine,
manual CQ polling, or completion-channel delivery.
- Both version axes are stated before any symbol is promised:
pkg-config --modversion doca-verbs must agree with
doca_caps --version and pkg-config --modversion doca-common;
and the doca_verbs_* ABI ships in the EXPERIMENTAL tier — symbols
may rename or graduate between releases and the installed headers
outrank documentation (doca-version/SKILL.md).
Device support for a verb is answered by the doca_devinfo
capability query, not by either version.
- Existing
ibv_* handles are replaced, never mixed with
doca_verbs_* handles on the same hardware objects.
The decision this skill exists to gate
The decision every conversation loading this skill must make FIRST,
before any code-level discussion:
- Has the user confirmed that the matching higher-level DOCA
library does not expose the semantic they need? If no — route
back:
doca-rdma/SKILL.md for general RDMA,
doca-eth/SKILL.md for Ethernet TX / RX,
doca-rmax/SKILL.md for timing-precise media.
The most common failure is recommending raw verbs unnecessarily
because the user said "verbs" or "QP" without confirming the
higher-level surface already covers the case.
- Is the needed semantic a specific verb / opcode / WR flag / QP
attribute / SRQ option the higher-level library does not expose?
Examples: a raw WR flag
doca_rdma_task_* does not surface; custom
CQ handling beyond the progress engine; an esoteric QP attribute
(path MTU, PSN, ECE); explicit SRQ control; congestion-control
group (doca_verbs_cc_group_*) attachment; Address-Handle tuning
(DGID / DLID / SL / SGID index / hop limit / traffic class / UDP
source port). If yes — in scope.
- Is the user porting existing libibverbs code into the DOCA Core
model? In scope, AND the agent must teach the porting path
(replace
ibv_* handles with doca_verbs_* handles, integrate via
doca_verbs_context_create, drive completions via the DOCA
progress engine instead of polling the CQ) — not a mechanical 1:1
replacement.
If none of (1)-(3) apply, the answer to "should I use doca-verbs?"
is no — route back to the matching higher-level library. A raw-verbs
skill that talks the user out of raw verbs is doing its job.
Audience
This skill serves external developers building applications that
consume the DOCA Verbs library — code calling doca_verbs_*
(directly in C/C++, or via FFI/bindings) for raw QP / CQ / PD / MR /
SRQ / Address-Handle / Ethernet-SQ / Ethernet-RQ control inside a
DOCA Core context. It is not for NVIDIA developers contributing to
DOCA Verbs, and not the entry point for general DOCA RDMA / Eth /
RMAX work — that belongs in the matching higher-level library skill.
Language scope
DOCA Verbs ships as a C library (pkg-config module doca-verbs);
public headers live under the installed DOCA tree
($(pkg-config --variable=includedir doca-common)/doca_verbs.h plus
the doca_verbs_*.h family) and, per the headers-win-over-docs rule
in doca-version/SKILL.md, are the
authoritative symbol surface. C / C++ is the canonical case TASKS.md
assumes; other languages reach the same *.so through FFI, and the
skill keeps its rules language-neutral while routing to the public C
ABI as the authoritative surface.
When to load this skill
Load this skill ONLY after the user has confirmed the matching
higher-level DOCA library does not expose the needed semantic.
Concretely:
- The user asks "do I need to drop to
doca-verbs for this?" —
load to answer, but expect "no, stay in the higher-level
library" unless the user can name the verb / opcode / option the
higher-level library does not surface.
- The user wants a specific raw WR flag, QP option, SRQ feature,
custom CQ-handling pattern, or congestion-control group attachment
the higher-level library does not expose.
- The user is porting libibverbs code into the DOCA Core model and
needs the integration path (lifecycle, progress engine, no-mixing).
- A
DOCA_ERROR_* from a doca_verbs_* call needs diagnosis —
including IO_FAILED, where the answer lives on the
completion-queue entry, not the submit return.
- Designing non-C bindings wrapping the verbs C ABI that must honor
the boundary, lifecycle, and cap-query rules.
Do not load for: general RDMA (doca-rdma/SKILL.md);
Ethernet queueing (doca-eth/SKILL.md); timing-precise
media (doca-rmax/SKILL.md); cases another
higher-level library covers (doca-flow/SKILL.md for
steering, doca-sta/SKILL.md for NVMe-oF target acceleration); DOCA install
(doca-setup/SKILL.md); or general orientation —
all routed via
doca-public-knowledge-map/SKILL.md.
What this skill provides
This is a thin loader. The substantive raw-verbs material lives
in two companion files:
CAPABILITIES.md — what doca-verbs can express on this
version: the higher-level-vs-verbs selection table, the libibverbs
boundary, the verbs object model (doca_verbs_context + QP / CQ /
PD / MR / SRQ / Address-Handle / Completion-Channel / Ethernet-SQ /
Ethernet-RQ / CC-group), the capability-query surface
(doca_verbs_query_device + doca_verbs_device_attr_get_*), the
error taxonomy (mapped onto DOCA_ERROR_* with the IO_FAILED →
completion-entry overlay), the observability surface (progress
engine vs manual CQ polling vs comp-channel delivery), and the
safety policy gating the no-mixing-with-libibverbs rule.
TASKS.md — workflows for the six in-scope verbs: configure,
build, modify, run, test, debug, plus a Deferred task verbs block. Every workflow assumes the drop-down decision above
was made; ## configure re-confirms it.
The skill assumes DOCA is installed and the user has the privileges
their install profile expects (RDMA stack on host, same as
doca-rdma/SKILL.md). It does not cover installing
DOCA — route to doca-setup/SKILL.md.
What this skill deliberately does not ship
This skill is agent guidance, not a samples or templates bundle.
It deliberately does not contain — and pull requests should not add:
- Pre-written DOCA Verbs application source code, in any
language. The verified verbs source is the shipped C samples on
the install (via
ls /opt/mellanox/doca/samples/); the agent
routes there and prescribes a minimum-diff modification via the
modify-a-sample workflow in
doca-programming-guide/SKILL.md,
layered with the verbs overrides in
TASKS.md ## modify.
- Standalone build manifests (
meson.build, CMakeLists.txt,
Cargo.toml, …) parked inside the skill. The agent constructs the
manifest in the user's project against the installed DOCA, where
pkg-config --modversion doca-verbs is the source of truth.
- A
samples/, bindings/, or reference/ subtree of any
kind. A mock artifact labeled "reference" reads as buildable and
misleads.
- A migration script from libibverbs to
doca-verbs. Porting is
judgment, not mechanical replacement — see
TASKS.md ## modify.
Loading order
- Confirm the question is in scope by walking the drop-down decision above.
- For the higher-level-vs-verbs split, the libibverbs boundary,
the object model, capability discovery, error taxonomy,
observability, and safety policy, see CAPABILITIES.md.
- For step-by-step workflows — configure, build, modify, run,
test, debug — see TASKS.md.
Both companion files cross-link to each other, to the higher-level
libraries (doca-rdma/SKILL.md,
doca-eth/SKILL.md,
doca-rmax/SKILL.md) as climb-back homes, to
doca-common/SKILL.md for the doca_dev /
doca_pe / doca_ctx foundation primitives, to
doca-version/SKILL.md for canonical version
rules, and to
doca-public-knowledge-map/SKILL.md
whenever the right answer is "look it up in the public docs or the
install layout".
Related skills
When a step below routes to another skill that is not already loaded,
read that skill first; if unavailable, stop and name it and the layer it
covers — do not continue that layer from memory.
doca-rdma/SKILL.md — the canonical higher-level
RDMA library and the home this skill routes most RDMA users back
to. Any conversation loading doca-verbs for an RDMA question
should also load doca-rdma so the climb-back answer is immediate.
doca-eth/SKILL.md — the higher-level Ethernet
queue library. doca-verbs also exposes Ethernet SQ / RQ verbs
(doca_verbs_eth_sq_*, doca_verbs_eth_rq_*); once the user
confirms doca-eth lacks the needed option (TS-source-type tuning,
plane-index pinning, multi-pkt-send-WQE), this skill takes over.
doca-rmax/SKILL.md — the higher-level Rivermax
library for timing-precise media. Most Rivermax cases stay there;
raw verbs is the escape hatch for the rare case needing a verb
Rivermax does not expose.
doca-common/SKILL.md — the foundation every
DOCA context (including doca_verbs_context) rests on:
doca_dev / doca_pe / doca_ctx, the doca_devinfo cap-query
rule, and the lifecycle. This skill layers verbs specifics on top.
doca-public-knowledge-map/SKILL.md —
the routing table for public DOCA docs and the install layout; the
DOCA Verbs public guide is listed there.
doca-setup/SKILL.md — env preparation,
install verification, and the no install yet path via the NGC
DOCA container. This skill assumes its preconditions hold.
doca-version/SKILL.md — canonical DOCA
version-handling rules. ## Version compatibility cross-links the
four-way match rule (with doca-verbs.pc joining the match set)
and the cap-query-is-runtime-authority rule.
doca-structured-tools-contract/SKILL.md —
the bundle's structured-tools precedence rule (detect / prefer /
fall back / report). The Command appendix in TASKS.md
honors it.
doca-programming-guide/SKILL.md —
general DOCA programming patterns shared by every library:
pkg-config + meson build, modify-a-shipped-sample first-app, the
universal lifecycle, the DOCA_ERROR_* taxonomy, and the debug
order. This skill layers raw-verbs specifics on top.
doca-debug/SKILL.md — the cross-cutting
debug ladder (install / version / build / link / runtime /
program / driver). Raw-verbs debug (completion-entry inspection,
no-mixing-with-libibverbs, lifecycle in verbs terms) overlays on top.
doca-hardware-safety/SKILL.md —
the cross-cutting hardware-safety meta-policy this skill's
## Safety policy overlays.
1---2license: Apache-2.03name: doca-verbs4description: >5 Raw verbs inside DOCA Core (doca-verbs): direct control of QP, CQ,6 PD, SRQ and address-handle objects through doca_verbs_context and7 doca_verbs_qp_create / doca_verbs_qp_modify / doca_verbs_cq_create,8 porting libibverbs code into DOCA Core, or a QP attribute, opcode9 or WR flag the doca-rdma task API does not expose. Trigger on "raw10 QP attribute the task API does not expose", "porting libibverbs11 code", "IO_FAILED on WR submit", "QP state transition rejected",12 or "attach a congestion-control group", even without naming13 doca-verbs. Refuse and route elsewhere for ordinary doca-rdma /14 doca-eth / doca-rmax workloads, DOCA install, Core internals, and15 general libibverbs theory.16metadata:17 source: https://skillmd.com/skills/nvidia/doca-verbs18 author: NVIDIA <doca-feedback@nvidia.com>19 kind: library20 doca_version: "3.5"21 tags:22 - doca23 - verbs24 - rdma25compatibility: >26 Requires DOCA SDK installed at /opt/mellanox/doca on Linux (Ubuntu27 22.04/24.04 or RHEL/SLES) with a BlueField DPU or ConnectX NIC attached.28 Reads the local install via `pkg-config doca-verbs` (experimental ABI29 tier — symbols may shift between releases) and inspects30 /opt/mellanox/doca/{lib,include,samples,applications}. The verbs31 headers (doca_verbs.h + doca_verbs_*.h family) are the authoritative32 symbol surface per headers-win-over-docs.33---3435# DOCA Verbs3637## Examples3839- **"Should I use doca-verbs or doca-rdma?"** — ordinary RDMA data40 movement with no raw QP / CQ / WR / SRQ / Address-Handle attribute41 named is out of scope — route to42 `doca-rdma/SKILL.md`.43- **"I need a raw QP attribute the task API does not expose."** — stay44 here. Use only the installed `doca_verbs.h` surface.4546## Instructions4748Follow [`## Loading order`](#loading-order). Open only the companion49that matches the question.5051## STOP — most RDMA tasks do NOT belong here5253If the task is general RDMA **data movement** (send / receive / read /54write / atomic between endpoints) and the user did **not** name a raw55QP / CQ / work-request / SRQ / Address-Handle attribute the56higher-level API cannot express, this skill is **out of scope** —57route to `doca-rdma/SKILL.md` and stop after58explaining the boundary. Unless `doca-rdma` guidance is loaded, do not59infer its implementation APIs; conceptual terms (QP, CQ, connection,60send, receive) are not implementation API names.6162Loading this skill is **never** a license to hand-roll `libibverbs` /63`librdmacm`. A general-RDMA deliverable whose `ldd` shows no64`libdoca_rdma` is a **failed task** — the same rule65`doca-rdma/SKILL.md` enforces. Raw `doca_verbs_*` is in66scope only for the narrow attribute-level needs below; everything else67climbs back up.6869**Where to start:** This skill is the **raw-verbs escape hatch beneath70the higher-level DOCA libraries** (`doca-rdma/SKILL.md`,71`doca-eth/SKILL.md`, `doca-rmax/SKILL.md`).72The agent's first job is to confirm the user actually needs to drop73down — most users do not; the right answer is almost always *"stay in74the higher-level library"*. Open [`CAPABILITIES.md`](CAPABILITIES.md)75for *what the verbs surface exposes and the libibverbs boundary*; open76[`TASKS.md`](TASKS.md) once raw verbs is confirmed. If DOCA is not77installed, route to `doca-setup/SKILL.md` first.7879## Non-negotiable answer checklist8081For every in-scope porting, lifecycle, or debugging answer, do not declare82it complete until it explicitly states all applicable items below:83841. `doca_verbs_context` is the DOCA Core context owning the verbs85 surface; it wraps the `doca_dev`, integrates with the progress86 engine, and owns the per-object PD / MR / CQ / QP lifecycle in87 [`CAPABILITIES.md ## Capabilities and modes`](CAPABILITIES.md#capabilities-and-modes).882. A submit-time success followed by `DOCA_ERROR_IO_FAILED` is89 diagnosed from the completion-queue entry's error field — not the90 submit return — before recommending retries or code changes.913. The answer selects exactly one completion path: progress engine,92 manual CQ polling, or completion-channel delivery.934. Both version axes are stated before any symbol is promised:94 `pkg-config --modversion doca-verbs` must agree with95 `doca_caps --version` and `pkg-config --modversion doca-common`;96 and the `doca_verbs_*` ABI ships in the EXPERIMENTAL tier — symbols97 may rename or graduate between releases and the installed headers98 outrank documentation (`doca-version/SKILL.md`).99 Device support for a verb is answered by the `doca_devinfo`100 capability query, not by either version.1015. Existing `ibv_*` handles are replaced, never mixed with102 `doca_verbs_*` handles on the same hardware objects.103104## The decision this skill exists to gate105106The decision every conversation loading this skill must make FIRST,107before any code-level discussion:1081091. **Has the user confirmed that the matching higher-level DOCA110 library does not expose the semantic they need?** If no — route111 back: `doca-rdma/SKILL.md` for general RDMA,112 `doca-eth/SKILL.md` for Ethernet TX / RX,113 `doca-rmax/SKILL.md` for timing-precise media.114 The most common failure is recommending raw verbs *unnecessarily*115 because the user said "verbs" or "QP" without confirming the116 higher-level surface already covers the case.1172. **Is the needed semantic a specific verb / opcode / WR flag / QP118 attribute / SRQ option the higher-level library does not expose?**119 Examples: a raw WR flag `doca_rdma_task_*` does not surface; custom120 CQ handling beyond the progress engine; an esoteric QP attribute121 (path MTU, PSN, ECE); explicit SRQ control; congestion-control122 group (`doca_verbs_cc_group_*`) attachment; Address-Handle tuning123 (DGID / DLID / SL / SGID index / hop limit / traffic class / UDP124 source port). If yes — in scope.1253. **Is the user porting existing libibverbs code into the DOCA Core126 model?** In scope, AND the agent must teach the porting path127 (replace `ibv_*` handles with `doca_verbs_*` handles, integrate via128 `doca_verbs_context_create`, drive completions via the DOCA129 progress engine instead of polling the CQ) — not a mechanical 1:1130 replacement.131132If none of (1)-(3) apply, the answer to *"should I use `doca-verbs`?"*133is **no** — route back to the matching higher-level library. A raw-verbs134skill that talks the user *out* of raw verbs is doing its job.135136## Audience137138This skill serves **external developers building applications that139consume the DOCA Verbs library** — code calling `doca_verbs_*`140(directly in C/C++, or via FFI/bindings) for raw QP / CQ / PD / MR /141SRQ / Address-Handle / Ethernet-SQ / Ethernet-RQ control inside a142DOCA Core context. It is *not* for NVIDIA developers contributing to143DOCA Verbs, and *not* the entry point for general DOCA RDMA / Eth /144RMAX work — that belongs in the matching higher-level library skill.145146## Language scope147148DOCA Verbs ships as a C library (`pkg-config` module `doca-verbs`);149public headers live under the installed DOCA tree150(`$(pkg-config --variable=includedir doca-common)/doca_verbs.h` plus151the `doca_verbs_*.h` family) and, per the headers-win-over-docs rule152in `doca-version/SKILL.md`, are the153authoritative symbol surface. C / C++ is the canonical case `TASKS.md`154assumes; other languages reach the same `*.so` through FFI, and the155skill keeps its rules language-neutral while routing to the public C156ABI as the authoritative surface.157158## When to load this skill159160Load this skill ONLY after the user has confirmed the matching161higher-level DOCA library does not expose the needed semantic.162Concretely:163164- The user asks *"do I need to drop to `doca-verbs` for this?"* —165 load to answer, but expect *"no, stay in the higher-level166 library"* unless the user can name the verb / opcode / option the167 higher-level library does not surface.168- The user wants a specific raw WR flag, QP option, SRQ feature,169 custom CQ-handling pattern, or congestion-control group attachment170 the higher-level library does not expose.171- The user is porting libibverbs code into the DOCA Core model and172 needs the integration path (lifecycle, progress engine, no-mixing).173- A `DOCA_ERROR_*` from a `doca_verbs_*` call needs diagnosis —174 including IO_FAILED, where the answer lives on the175 completion-queue entry, not the submit return.176- Designing non-C bindings wrapping the verbs C ABI that must honor177 the boundary, lifecycle, and cap-query rules.178179180Do **not** load for: general RDMA (`doca-rdma/SKILL.md`);181Ethernet queueing (`doca-eth/SKILL.md`); timing-precise182media (`doca-rmax/SKILL.md`); cases another183higher-level library covers (`doca-flow/SKILL.md` for184steering, `doca-sta/SKILL.md` for NVMe-oF target acceleration); DOCA install185(`doca-setup/SKILL.md`); or general orientation —186all routed via187`doca-public-knowledge-map/SKILL.md`.188189## What this skill provides190191This is a **thin loader**. The substantive raw-verbs material lives192in two companion files:193194- `CAPABILITIES.md` — what `doca-verbs` can express on this195 version: the higher-level-vs-verbs selection table, the libibverbs196 boundary, the verbs object model (`doca_verbs_context` + QP / CQ /197 PD / MR / SRQ / Address-Handle / Completion-Channel / Ethernet-SQ /198 Ethernet-RQ / CC-group), the capability-query surface199 (`doca_verbs_query_device` + `doca_verbs_device_attr_get_*`), the200 error taxonomy (mapped onto `DOCA_ERROR_*` with the IO_FAILED →201 completion-entry overlay), the observability surface (progress202 engine vs manual CQ polling vs comp-channel delivery), and the203 safety policy gating the no-mixing-with-libibverbs rule.204- `TASKS.md` — workflows for the six in-scope verbs: `configure`,205 `build`, `modify`, `run`, `test`, `debug`, plus a `Deferred task206 verbs` block. Every workflow assumes the drop-down decision above207 was made; `## configure` re-confirms it.208209The skill assumes DOCA is installed and the user has the privileges210their install profile expects (RDMA stack on host, same as211`doca-rdma/SKILL.md`). It does not cover installing212DOCA — route to `doca-setup/SKILL.md`.213214## What this skill deliberately does not ship215216This skill is **agent guidance**, not a samples or templates bundle.217It deliberately does not contain — and pull requests should not add:218219- **Pre-written DOCA Verbs application source code, in any220 language.** The verified verbs source is the shipped C samples on221 the install (via `ls /opt/mellanox/doca/samples/`); the agent222 routes there and prescribes a minimum-diff modification via the223 modify-a-sample workflow in224 `doca-programming-guide/SKILL.md`,225 layered with the verbs overrides in226 [`TASKS.md ## modify`](TASKS.md#modify).227- **Standalone build manifests** (`meson.build`, `CMakeLists.txt`,228 `Cargo.toml`, …) parked inside the skill. The agent constructs the229 manifest *in the user's project* against the installed DOCA, where230 `pkg-config --modversion doca-verbs` is the source of truth.231- **A `samples/`, `bindings/`, or `reference/` subtree** of any232 kind. A mock artifact labeled "reference" reads as buildable and233 misleads.234- **A migration script from libibverbs to `doca-verbs`.** Porting is235 *judgment*, not mechanical replacement — see236 [`TASKS.md ## modify`](TASKS.md#modify).237238## Loading order2392401. Confirm the question is in scope by walking the drop-down decision above.2412. **For the higher-level-vs-verbs split, the libibverbs boundary,242 the object model, capability discovery, error taxonomy,243 observability, and safety policy, see [CAPABILITIES.md](CAPABILITIES.md).**2443. **For step-by-step workflows — configure, build, modify, run,245 test, debug — see [TASKS.md](TASKS.md).**246247Both companion files cross-link to each other, to the higher-level248libraries (`doca-rdma/SKILL.md`,249`doca-eth/SKILL.md`,250`doca-rmax/SKILL.md`) as climb-back homes, to251`doca-common/SKILL.md` for the `doca_dev` /252`doca_pe` / `doca_ctx` foundation primitives, to253`doca-version/SKILL.md` for canonical version254rules, and to255`doca-public-knowledge-map/SKILL.md`256whenever the right answer is "look it up in the public docs or the257install layout".258259## Related skills260261When a step below routes to another skill that is not already loaded,262read that skill first; if unavailable, stop and name it and the layer it263covers — do not continue that layer from memory.264265- `doca-rdma/SKILL.md` — the canonical higher-level266 RDMA library and the home this skill routes most RDMA users *back*267 to. Any conversation loading `doca-verbs` for an RDMA question268 should also load `doca-rdma` so the climb-back answer is immediate.269- `doca-eth/SKILL.md` — the higher-level Ethernet270 queue library. `doca-verbs` also exposes Ethernet SQ / RQ verbs271 (`doca_verbs_eth_sq_*`, `doca_verbs_eth_rq_*`); once the user272 confirms `doca-eth` lacks the needed option (TS-source-type tuning,273 plane-index pinning, multi-pkt-send-WQE), this skill takes over.274- `doca-rmax/SKILL.md` — the higher-level Rivermax275 library for timing-precise media. Most Rivermax cases stay there;276 raw verbs is the escape hatch for the rare case needing a verb277 Rivermax does not expose.278- `doca-common/SKILL.md` — the foundation every279 DOCA context (including `doca_verbs_context`) rests on:280 `doca_dev` / `doca_pe` / `doca_ctx`, the `doca_devinfo` cap-query281 rule, and the lifecycle. This skill layers verbs specifics on top.282- `doca-public-knowledge-map/SKILL.md` —283 the routing table for public DOCA docs and the install layout; the284 DOCA Verbs public guide is listed there.285- `doca-setup/SKILL.md` — env preparation,286 install verification, and the *no install yet* path via the NGC287 DOCA container. This skill assumes its preconditions hold.288- `doca-version/SKILL.md` — canonical DOCA289 version-handling rules. `## Version compatibility` cross-links the290 four-way match rule (with `doca-verbs.pc` joining the match set)291 and the cap-query-is-runtime-authority rule.292- `doca-structured-tools-contract/SKILL.md` —293 the bundle's structured-tools precedence rule (detect / prefer /294 fall back / report). The Command appendix in [TASKS.md](TASKS.md)295 honors it.296- `doca-programming-guide/SKILL.md` —297 general DOCA programming patterns shared by every library:298 `pkg-config` + meson build, modify-a-shipped-sample first-app, the299 universal lifecycle, the `DOCA_ERROR_*` taxonomy, and the debug300 order. This skill layers raw-verbs specifics on top.301- `doca-debug/SKILL.md` — the cross-cutting302 debug ladder (install / version / build / link / runtime /303 program / driver). Raw-verbs debug (completion-entry inspection,304 no-mixing-with-libibverbs, lifecycle in verbs terms) overlays on top.305- `doca-hardware-safety/SKILL.md` —306 the cross-cutting hardware-safety meta-policy this skill's307 `## Safety policy` overlays.