DOCA RDMA Initiator
Where to start: This skill assumes DOCA is already installed and
the user is doing hands-on RDMI work on a host or BlueField with
the DOCA package set that ships the doca-rdmi library. Open
TASKS.md if the user wants to do something
(install / configure / build / modify / run / test / debug / use);
open CAPABILITIES.md when the question is
what can RDMI express on this version — the object model, the
DPA-side handle types, the relationship to doca-rdma, the
EXPERIMENTAL-tag policy, and the safety overlay.
End-to-end "walk me through doca-rdmi" questions are answerable
entirely from this skill. Go straight to
TASKS.md ## end-to-end (quickref),
which carries the self-contained install-check → device/cap
discovery → sample → pkg-config build → run → debug walkthrough
with the exact commands. You do not need to open doca-setup or
doca-programming-guide to answer an RDMI build/run/debug question.
Route to doca-setup when the required
DOCA prerequisites are absent, partial, or version-mismatched.
Example questions this skill answers well
The CLASSES of RDMI questions this skill is built to answer, each
with one worked example. The agent should treat the class as the
load-bearing piece — the worked example is a single instance.
- "Should I use
doca-rdmi or doca-rdma for this case?" —
worked example: "I have a DPA kernel that needs to fire 1 MB
RDMA writes at a remote responder; which library?". Answered by
the initiator-side vs general-purpose selection rule in
CAPABILITIES.md ## Capabilities and modes
surface-selection table + the routing back to
doca-rdma when the use case is
two-sided or host-CPU initiated.
- "How do I bring up an RDMI connection on the DPA datapath?" —
worked example: "create a
doca_rdmi_connection, attach a DPA
completion context, hand the DPA-side handle to my kernel".
Answered by the connection-object lifecycle in
CAPABILITIES.md ## Capabilities and modes
- the configure walk in
TASKS.md ## configure.
- "How do connection and poster relate — when do I need both?"
— worked example: "my application receives work requests AND
posts RDMA writes; do I need a
doca_rdmi_connection plus a
doca_rdmi_poster, or one of them?". Answered by the
two-object model in
CAPABILITIES.md ## Capabilities and modes
- the modify-from-sample slot table in
TASKS.md ## modify.
- "How do I drive completions on the DPA side?" — worked
example: "hook the connection to a
doca_dpa_completion so my
kernel polls completions directly". Answered by the DPA-side
completion-attach pattern in
CAPABILITIES.md ## Capabilities and modes
- the run-side wiring in
TASKS.md ## run, cross-linked into
doca-dpa for the DPA programming
surface itself.
- "Is the symbol I want available — and is it stable enough to
ship?" — worked example: "is
doca_rdmi_poster_post GA on
my installed DOCA, or still EXPERIMENTAL?". Answered by the
EXPERIMENTAL-tag policy in
CAPABILITIES.md ## Version compatibility
- the version-discovery rule
(
pkg-config --modversion doca-rdmi) pinned in
TASKS.md ## configure.
- "What does this
DOCA_ERROR_* from a doca_rdmi_* call
mean?" — worked example: "DOCA_ERROR_BAD_STATE from
doca_rdmi_connection_dpa_completion_attach". Answered by the
RDMI overlay on the cross-library taxonomy in
CAPABILITIES.md ## Error taxonomy
- the layered ladder in
TASKS.md ## debug
that escalates to doca-debug.
Audience
This skill serves external developers building DPA-resident DOCA
applications that need to initiate one-sided RDMA operations
against a remote responder — i.e., users whose accelerator-side
code wants to post sends, writes, or reads directly from the
accelerator without round-tripping through the host CPU. The
canonical caller is a DPA kernel that has been compiled with
doca-dpacc-compiler and runs on the BlueField DPA datapath; a
GPU-side caller that drives the DPU's RDMA queues is the
sister case routed to doca-gpi. This
skill is not for NVIDIA developers contributing to DOCA RDMI
itself, and it is not the right surface for general host-CPU
two-sided RDMA — that belongs to
doca-rdma.
Language scope
DOCA RDMI ships as a C library with the pkg-config module name
doca-rdmi. The library's host-side surface
(doca_rdmi_connection_*, doca_rdmi_poster_*) is C; the DPA-side
surface that the accelerator kernel uses is also C, compiled against
the DOCA DPA toolchain documented in
doca-dpa. Other-language consumers (Rust,
Go, Python, …) consume the host-side *.so through FFI; the skill's
contribution in that case is to keep the connection / poster
lifecycle, the EXPERIMENTAL-tag policy, the DPA-side handoff rules,
and the safety overlay language-neutral, and to route the agent to
the public C ABI as the authoritative surface that any wrapper will
eventually call. The DPA-side surface is not wrappable in another
language — it is compiled and linked into the DPA binary itself.
When to load this skill
Load this skill when the user is doing hands-on DOCA RDMI work
on a host or BlueField with DOCA installed. Concretely:
- Deciding between
doca-rdmi and doca-rdma for a new
one-sided RDMA workload that runs from the DPA datapath.
- Creating a
doca_rdmi_connection or doca_rdmi_poster,
attaching a doca_dpa_completion or a doca_verbs_cq, and
starting the context on the DPA datapath.
- Wiring the DPA-side handle returned by
doca_rdmi_connection_get_dpa_handle /
doca_rdmi_poster_get_dpa_handle into a DPA kernel that calls
the matching device-side header
(doca_rdmi_dev_connection.h, doca_rdmi_dev_poster.h,
doca_rdmi_dev_cqe.h).
- Acknowledging receive completions on the host side via
doca_rdmi_connection_recv_ack after the DPA kernel consumed
them.
- Auditing which RDMI symbols are EXPERIMENTAL on the installed
DOCA version, before declaring an RDMI-using component
production-stable.
- Debugging a
DOCA_ERROR_* returned by a doca_rdmi_* call and
deciding whether the cause is a configuration mistake, a
lifecycle ordering bug, an unsupported capability on this device,
or a layer below DOCA.
Do not load this skill for general DOCA orientation, install of
DOCA itself, or two-sided host-CPU RDMA questions. For those, use
doca-public-knowledge-map,
doca-setup, and
doca-rdma respectively.
What this skill provides
This is a thin loader. The body keeps only the orientation
needed to pick the right next file. The substantive RDMI-specific
material lives in two companion files:
CAPABILITIES.md — what RDMI can express on this version: the
doca_rdmi_connection and doca_rdmi_poster object model, the
DPA-side completion-attach pattern, the relationship to
doca-verbs (RDMI builds on a doca_verbs_context) and to
doca-dpa (the accelerator-side datapath), the EXPERIMENTAL-tag
rule for version handling, the RDMI overlay on the cross-library
DOCA_ERROR_* taxonomy, the observability surface (completion
events on the PE / DPA-side completions), and the safety policy
that gates posting work from an accelerator kernel into a remote
responder's memory.
TASKS.md — step-by-step workflows for the eight in-scope verbs:
install, configure, build, modify, run, test,
debug, use. Plus a ## rollback overlay (RDMI-specific
five-step teardown for the verbs / connection / DPA-attach /
MR stack) and the 5-phase universal debug-loop instantiation
appended to ## debug. Plus a Deferred task verbs block
that points out-of-scope questions at the right next skill.
The skill assumes a host or BlueField where DOCA is already
installed at the standard location and the user has the privileges
their public install profile expects. It does not cover installing
DOCA itself — that path goes through
doca-setup.
What this skill deliberately does not ship
This skill is agent guidance, not a samples or templates
bundle. To keep the boundary clean, it deliberately does not
contain — and pull requests should not add:
- Pre-written DOCA RDMI application source code, in any
language. The agent's job is to route the user to verified
reference code on the user's installed DOCA and to prescribe a
minimum-diff modification via the universal modify-a-sample
workflow in
doca-programming-guide,
layered with the RDMI-specific overrides in
TASKS.md ## modify. Because every RDMI
symbol is EXPERIMENTAL at the time of writing, the skill
refuses to author RDMI source code from documentation prose —
the API can change between releases and the resulting code may
not even compile.
- Standalone build manifests (
meson.build, CMakeLists.txt,
Cargo.toml, …) parked inside the skill. The agent constructs
the build manifest in the user's project directory against the
user's installed DOCA, where pkg-config --modversion doca-rdmi
is the source of truth.
- DPA-side kernel templates. The DPA-side surface is owned by
doca-dpa; RDMI's DPA-side headers are
consumed by the DPA programming model documented there. This
skill names the RDMI-specific handoff (the DPA handle type, the
completion-attach call) but does not author DPA kernels.
- A
samples/, bindings/, or reference/ subtree of any
kind. A mock or incomplete artifact in this skill's tree, even
one labeled "reference", is misleading: users will read it as
buildable.
Loading order
- Read this
SKILL.md first to confirm the user's question is in
scope.
- For the RDMI object model, the DPA-side handoff pattern, the
EXPERIMENTAL-tag policy, the error taxonomy, observability, and
safety policy, see CAPABILITIES.md.
- For step-by-step workflows — install, configure, build,
modify, run, test, debug, use — see TASKS.md.
Both companion files cross-link to each other and to
doca-public-knowledge-map
whenever the right answer is "look it up in the public docs or the
installed package layout" rather than "RDMI-specific guidance".
Related skills
doca-rdma — the higher-level RDMA
library covering two-sided and host-CPU-initiated RDMA. RDMI is
the focused initiator-side surface; doca-rdma is the right
answer for the majority of RDMA use cases. The selection table
in CAPABILITIES.md ## Capabilities and modes
is the load-bearing decision aid.
doca-dpa — the DOCA DPA programming
surface. RDMI returns DPA-side handles
(doca_dpa_dev_rdmi_connection_t, doca_rdmi_dev_poster_t)
that the DPA kernel uses through the device-side headers
(doca_rdmi_dev_connection.h, doca_rdmi_dev_poster.h,
doca_rdmi_dev_cqe.h); the DPA toolchain, kernel build, and
execution model are owned by that skill.
doca-gpi — the GPU-side sister of
this skill. GPI is the channel/queue surface a CUDA kernel
uses to initiate RDMA; RDMI is the DPA-side surface. Both
layer on the same DOCA RDMA / verbs substrate; either may
apply depending on whether the initiator is on the DPA or on
the GPU.
doca-public-knowledge-map — the
routing table for every public DOCA documentation source and
the on-disk layout of an installed DOCA package.
doca-setup — env preparation,
install verification, and the I have no install yet path with
the public NGC DOCA container.
doca-programming-guide —
general DOCA programming patterns shared by every library: the
canonical pkg-config + meson build pattern, the universal
modify-a-shipped-sample first-app workflow, the universal
Core-context lifecycle, the cross-library DOCA_ERROR_*
taxonomy. This skill layers RDMI specifics on top.
doca-debug — the cross-cutting
debug ladder (install / version / build / link / runtime /
program / driver). RDMI-specific debug overlays on top of it.
doca-hardware-safety —
the bundle-wide hardware-safety meta-policy. The ## Safety policy overlay in CAPABILITIES.md cross-links it.
doca-version — the version
detection / four-way match rule every per-artifact ## Version compatibility anchor builds on. This skill quotes
the RDMI-specific overlay only.
doca-structured-tools-contract —
the JSON-schema contracts for the agent-preferred structured
helpers (env probe, capability snapshot, version-matrix
lookup); the ## Command appendix in TASKS.md defers to
them before falling back to the manual chain.
1---2license: Apache-2.03name: doca-rdmi4description: >5 Use this skill when the user is doing hands-on DOCA RDMI (RDMA6 Initiator) programming — picking doca-rdmi vs doca-rdma for an7 accelerator-initiated one-sided RDMA flow, standing up a8 doca_rdmi_connection or doca_rdmi_poster, attaching a9 doca_dpa_completion or doca_verbs_cq before doca_ctx_start(),10 retrieving the DPA-side handle for a DPA kernel, auditing whether11 a doca_rdmi_* symbol is EXPERIMENTAL on this DOCA, or debugging12 DOCA_ERROR_* returns from RDMI calls. Trigger even when the user13 does not say "DOCA RDMI" or "initiator" — implicit phrasings14 include "my DPA kernel needs to post RDMA writes to a remote15 responder", "DPA kernel sees no completions", "function not found16 on doca_rdmi_* at link time", "DOCA_ERROR_BAD_STATE from17 completion attach", or "the DPA posted but the work request never18 arrived". Refuse and route elsewhere for two-sided or host-CPU19 RDMA, the DPA programming model, GPU-side RDMA initiation, or20 general RDMA/IB/RoCE concepts — those belong to other skills.21metadata:22 source: https://skillmd.com/skills/nvidia/doca-rdmi23 kind: library24compatibility: >25 Requires DOCA SDK installed at /opt/mellanox/doca on Linux26 (Ubuntu 22.04/24.04 or RHEL/SLES) with a BlueField DPU or27 ConnectX NIC attached, plus the DOCA DPA toolchain and a28 DPA-capable BlueField when the data path runs on the DPA. Reads29 the user's local install via `pkg-config doca-rdmi` (alongside30 doca-common, doca-verbs, doca-dpa) and inspects31 /opt/mellanox/doca/{lib,include,samples}.32---3334# DOCA RDMA Initiator3536**Where to start:** This skill assumes DOCA is already installed and37the user is doing **hands-on RDMI work** on a host or BlueField with38the DOCA package set that ships the `doca-rdmi` library. Open39[`TASKS.md`](TASKS.md) if the user wants to *do* something40(install / configure / build / modify / run / test / debug / use);41open [`CAPABILITIES.md`](CAPABILITIES.md) when the question is42*what can RDMI express on this version* — the object model, the43DPA-side handle types, the relationship to `doca-rdma`, the44EXPERIMENTAL-tag policy, and the safety overlay.4546**End-to-end "walk me through doca-rdmi" questions are answerable47entirely from this skill.** Go straight to48[`TASKS.md ## end-to-end (quickref)`](TASKS.md#end-to-end-quickref),49which carries the self-contained install-check → device/cap50discovery → sample → `pkg-config` build → run → debug walkthrough51with the exact commands. You do **not** need to open `doca-setup` or52`doca-programming-guide` to answer an RDMI build/run/debug question.53Route to [`doca-setup`](../../doca-setup/SKILL.md) when the required54DOCA prerequisites are absent, partial, or version-mismatched.5556## Example questions this skill answers well5758The CLASSES of RDMI questions this skill is built to answer, each59with one worked example. The agent should treat the *class* as the60load-bearing piece — the worked example is a single instance.6162- **"Should I use `doca-rdmi` or `doca-rdma` for this case?"** —63 worked example: *"I have a DPA kernel that needs to fire 1 MB64 RDMA writes at a remote responder; which library?"*. Answered by65 the *initiator-side vs general-purpose* selection rule in66 [`CAPABILITIES.md ## Capabilities and modes`](CAPABILITIES.md#capabilities-and-modes)67 surface-selection table + the routing back to68 [`doca-rdma`](../doca-rdma/SKILL.md) when the use case is69 two-sided or host-CPU initiated.70- **"How do I bring up an RDMI connection on the DPA datapath?"** —71 worked example: *"create a `doca_rdmi_connection`, attach a DPA72 completion context, hand the DPA-side handle to my kernel"*.73 Answered by the connection-object lifecycle in74 [`CAPABILITIES.md ## Capabilities and modes`](CAPABILITIES.md#capabilities-and-modes)75 + the configure walk in76 [`TASKS.md ## configure`](TASKS.md#configure).77- **"How do connection and poster relate — when do I need both?"**78 — worked example: *"my application receives work requests AND79 posts RDMA writes; do I need a `doca_rdmi_connection` plus a80 `doca_rdmi_poster`, or one of them?"*. Answered by the81 two-object model in82 [`CAPABILITIES.md ## Capabilities and modes`](CAPABILITIES.md#capabilities-and-modes)83 + the modify-from-sample slot table in84 [`TASKS.md ## modify`](TASKS.md#modify).85- **"How do I drive completions on the DPA side?"** — worked86 example: *"hook the connection to a `doca_dpa_completion` so my87 kernel polls completions directly"*. Answered by the DPA-side88 completion-attach pattern in89 [`CAPABILITIES.md ## Capabilities and modes`](CAPABILITIES.md#capabilities-and-modes)90 + the run-side wiring in91 [`TASKS.md ## run`](TASKS.md#run), cross-linked into92 [`doca-dpa`](../doca-dpa/SKILL.md) for the DPA programming93 surface itself.94- **"Is the symbol I want available — and is it stable enough to95 ship?"** — worked example: *"is `doca_rdmi_poster_post` GA on96 my installed DOCA, or still EXPERIMENTAL?"*. Answered by the97 EXPERIMENTAL-tag policy in98 [`CAPABILITIES.md ## Version compatibility`](CAPABILITIES.md#version-compatibility)99 + the version-discovery rule100 (`pkg-config --modversion doca-rdmi`) pinned in101 [`TASKS.md ## configure`](TASKS.md#configure).102- **"What does this `DOCA_ERROR_*` from a `doca_rdmi_*` call103 mean?"** — worked example: *"`DOCA_ERROR_BAD_STATE` from104 `doca_rdmi_connection_dpa_completion_attach`"*. Answered by the105 RDMI overlay on the cross-library taxonomy in106 [`CAPABILITIES.md ## Error taxonomy`](CAPABILITIES.md#error-taxonomy)107 + the layered ladder in [`TASKS.md ## debug`](TASKS.md#debug)108 that escalates to [`doca-debug`](../../doca-debug/SKILL.md).109110## Audience111112This skill serves **external developers building DPA-resident DOCA113applications that need to *initiate* one-sided RDMA operations114against a remote responder** — i.e., users whose accelerator-side115code wants to post sends, writes, or reads directly from the116accelerator without round-tripping through the host CPU. The117canonical caller is a DPA kernel that has been compiled with118`doca-dpacc-compiler` and runs on the BlueField DPA datapath; a119GPU-side caller that drives the DPU's RDMA queues is the120sister case routed to [`doca-gpi`](../doca-gpi/SKILL.md). This121skill is *not* for NVIDIA developers contributing to DOCA RDMI122itself, and it is not the right surface for general host-CPU123two-sided RDMA — that belongs to124[`doca-rdma`](../doca-rdma/SKILL.md).125126## Language scope127128DOCA RDMI ships as a C library with the `pkg-config` module name129`doca-rdmi`. The library's *host-side* surface130(`doca_rdmi_connection_*`, `doca_rdmi_poster_*`) is C; the *DPA-side*131surface that the accelerator kernel uses is also C, compiled against132the DOCA DPA toolchain documented in133[`doca-dpa`](../doca-dpa/SKILL.md). Other-language consumers (Rust,134Go, Python, …) consume the host-side `*.so` through FFI; the skill's135contribution in that case is to keep the connection / poster136lifecycle, the EXPERIMENTAL-tag policy, the DPA-side handoff rules,137and the safety overlay language-neutral, and to route the agent to138the public C ABI as the authoritative surface that any wrapper will139eventually call. The DPA-side surface is *not* wrappable in another140language — it is compiled and linked into the DPA binary itself.141142## When to load this skill143144Load this skill when the user is doing **hands-on DOCA RDMI work**145on a host or BlueField with DOCA installed. Concretely:146147- Deciding between `doca-rdmi` and `doca-rdma` for a new148 one-sided RDMA workload that runs from the DPA datapath.149- Creating a `doca_rdmi_connection` or `doca_rdmi_poster`,150 attaching a `doca_dpa_completion` or a `doca_verbs_cq`, and151 starting the context on the DPA datapath.152- Wiring the DPA-side handle returned by153 `doca_rdmi_connection_get_dpa_handle` /154 `doca_rdmi_poster_get_dpa_handle` into a DPA kernel that calls155 the matching device-side header156 (`doca_rdmi_dev_connection.h`, `doca_rdmi_dev_poster.h`,157 `doca_rdmi_dev_cqe.h`).158- Acknowledging receive completions on the host side via159 `doca_rdmi_connection_recv_ack` after the DPA kernel consumed160 them.161- Auditing which RDMI symbols are EXPERIMENTAL on the installed162 DOCA version, before declaring an RDMI-using component163 production-stable.164- Debugging a `DOCA_ERROR_*` returned by a `doca_rdmi_*` call and165 deciding whether the cause is a configuration mistake, a166 lifecycle ordering bug, an unsupported capability on this device,167 or a layer below DOCA.168169Do **not** load this skill for general DOCA orientation, install of170DOCA itself, or two-sided host-CPU RDMA questions. For those, use171[`doca-public-knowledge-map`](../../doca-public-knowledge-map/SKILL.md),172[`doca-setup`](../../doca-setup/SKILL.md), and173[`doca-rdma`](../doca-rdma/SKILL.md) respectively.174175## What this skill provides176177This is a **thin loader**. The body keeps only the orientation178needed to pick the right next file. The substantive RDMI-specific179material lives in two companion files:180181- `CAPABILITIES.md` — what RDMI can express on this version: the182 `doca_rdmi_connection` and `doca_rdmi_poster` object model, the183 DPA-side completion-attach pattern, the relationship to184 `doca-verbs` (RDMI builds on a `doca_verbs_context`) and to185 `doca-dpa` (the accelerator-side datapath), the EXPERIMENTAL-tag186 rule for version handling, the RDMI overlay on the cross-library187 `DOCA_ERROR_*` taxonomy, the observability surface (completion188 events on the PE / DPA-side completions), and the safety policy189 that gates posting work from an accelerator kernel into a remote190 responder's memory.191- `TASKS.md` — step-by-step workflows for the eight in-scope verbs:192 `install`, `configure`, `build`, `modify`, `run`, `test`,193 `debug`, `use`. Plus a `## rollback` overlay (RDMI-specific194 five-step teardown for the verbs / connection / DPA-attach /195 MR stack) and the 5-phase universal debug-loop instantiation196 appended to `## debug`. Plus a `Deferred task verbs` block197 that points out-of-scope questions at the right next skill.198199The skill assumes a host or BlueField where DOCA is already200installed at the standard location and the user has the privileges201their public install profile expects. It does not cover installing202DOCA itself — that path goes through203[`doca-setup`](../../doca-setup/SKILL.md).204205## What this skill deliberately does not ship206207This skill is **agent guidance**, not a samples or templates208bundle. To keep the boundary clean, it deliberately does not209contain — and pull requests should not add:210211- **Pre-written DOCA RDMI application source code, in any212 language.** The agent's job is to route the user to verified213 reference code on the user's installed DOCA and to prescribe a214 minimum-diff modification via the universal modify-a-sample215 workflow in216 [`doca-programming-guide`](../../doca-programming-guide/SKILL.md),217 layered with the RDMI-specific overrides in218 [`TASKS.md ## modify`](TASKS.md#modify). Because every RDMI219 symbol is EXPERIMENTAL at the time of writing, the skill220 refuses to author RDMI source code from documentation prose —221 the API can change between releases and the resulting code may222 not even compile.223- **Standalone build manifests** (`meson.build`, `CMakeLists.txt`,224 `Cargo.toml`, …) parked inside the skill. The agent constructs225 the build manifest *in the user's project directory* against the226 user's installed DOCA, where `pkg-config --modversion doca-rdmi`227 is the source of truth.228- **DPA-side kernel templates.** The DPA-side surface is owned by229 [`doca-dpa`](../doca-dpa/SKILL.md); RDMI's DPA-side headers are230 *consumed by* the DPA programming model documented there. This231 skill names the RDMI-specific handoff (the DPA handle type, the232 completion-attach call) but does not author DPA kernels.233- **A `samples/`, `bindings/`, or `reference/` subtree** of any234 kind. A mock or incomplete artifact in this skill's tree, even235 one labeled "reference", is misleading: users will read it as236 buildable.237238## Loading order2392401. Read this `SKILL.md` first to confirm the user's question is in241 scope.2422. **For the RDMI object model, the DPA-side handoff pattern, the243 EXPERIMENTAL-tag policy, the error taxonomy, observability, and244 safety policy, see [CAPABILITIES.md](CAPABILITIES.md).**2453. **For step-by-step workflows — install, configure, build,246 modify, run, test, debug, use — see [TASKS.md](TASKS.md).**247248Both companion files cross-link to each other and to249[`doca-public-knowledge-map`](../../doca-public-knowledge-map/SKILL.md)250whenever the right answer is "look it up in the public docs or the251installed package layout" rather than "RDMI-specific guidance".252253## Related skills254255- [`doca-rdma`](../doca-rdma/SKILL.md) — the higher-level RDMA256 library covering two-sided and host-CPU-initiated RDMA. RDMI is257 the focused initiator-side surface; doca-rdma is the right258 answer for the majority of RDMA use cases. The selection table259 in [`CAPABILITIES.md ## Capabilities and modes`](CAPABILITIES.md#capabilities-and-modes)260 is the load-bearing decision aid.261- [`doca-dpa`](../doca-dpa/SKILL.md) — the DOCA DPA programming262 surface. RDMI returns DPA-side handles263 (`doca_dpa_dev_rdmi_connection_t`, `doca_rdmi_dev_poster_t`)264 that the DPA kernel uses through the device-side headers265 (`doca_rdmi_dev_connection.h`, `doca_rdmi_dev_poster.h`,266 `doca_rdmi_dev_cqe.h`); the DPA toolchain, kernel build, and267 execution model are owned by that skill.268- [`doca-gpi`](../doca-gpi/SKILL.md) — the GPU-side sister of269 this skill. GPI is the channel/queue surface a CUDA kernel270 uses to initiate RDMA; RDMI is the DPA-side surface. Both271 layer on the same DOCA RDMA / verbs substrate; either may272 apply depending on whether the initiator is on the DPA or on273 the GPU.274- [`doca-public-knowledge-map`](../../doca-public-knowledge-map/SKILL.md) — the275 routing table for every public DOCA documentation source and276 the on-disk layout of an installed DOCA package.277- [`doca-setup`](../../doca-setup/SKILL.md) — env preparation,278 install verification, and the *I have no install yet* path with279 the public NGC DOCA container.280- [`doca-programming-guide`](../../doca-programming-guide/SKILL.md) —281 general DOCA programming patterns shared by every library: the282 canonical `pkg-config` + meson build pattern, the universal283 modify-a-shipped-sample first-app workflow, the universal284 Core-context lifecycle, the cross-library `DOCA_ERROR_*`285 taxonomy. This skill layers RDMI specifics on top.286- [`doca-debug`](../../doca-debug/SKILL.md) — the cross-cutting287 debug ladder (install / version / build / link / runtime /288 program / driver). RDMI-specific debug overlays on top of it.289- [`doca-hardware-safety`](../../doca-hardware-safety/SKILL.md) —290 the bundle-wide hardware-safety meta-policy. The `## Safety291 policy` overlay in `CAPABILITIES.md` cross-links it.292- [`doca-version`](../../doca-version/SKILL.md) — the version293 detection / four-way match rule every per-artifact `##294 Version compatibility` anchor builds on. This skill quotes295 the RDMI-specific overlay only.296- [`doca-structured-tools-contract`](../../doca-structured-tools-contract/SKILL.md) —297 the JSON-schema contracts for the agent-preferred structured298 helpers (env probe, capability snapshot, version-matrix299 lookup); the `## Command appendix` in `TASKS.md` defers to300 them before falling back to the manual chain.301