Install any skill in seconds. Free to start, no credit card required.
Get Started Free →nvidia/doca-rdmi
Use this skill when the user is doing hands-on DOCA RDMI (RDMA Initiator) programming — picking doca-rdmi vs doca-rdma for an accelerator-initiated one-sided RDMA flow, standing up a doca_rdmi_connection or doca_rdmi_poster, attaching a doca_dpa_completion or doca_verbs_cq before doca_ctx_start(), retrieving the DPA-side handle for a DPA kernel, auditing whether a doca_rdmi_* symbol is EXPERIMENTAL on this DOCA, or debugging DOCA_ERROR_* returns from RDMI calls. Trigger even when the user does n
Passed 15 of 20 test cases with the skill, and 3 of 20 without it.
and 20 more in the full report
13 fixed3 passed either way6 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 12 test cases the skill fixed. Same model, same prompt, with and without the skill.
After my DPA accelerator kernel finishes processing received network messages on the DPA datapath, what host-side C API call must be invoked to acknowledge receive completion back to the library?
| Checked | Without skill | With skill |
|---|---|---|
| Specifies doca_rdmi_connection_recv_ack for host-side receive acknowledgment. | Missed | Passed |
The instructions your model reads when the skill loads.
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.
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.
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.doca_rdmi_connection, attach a DPA
completion context, hand the DPA-side handle to my kernel".
Answered by the connection-object lifecycle intest cases passed, vs 3 / 20 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.