Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →nvidia/doca-gpi
Use this skill for hands-on DOCA GPI programming — wiring a GPU-Packet-Initiator context so a CUDA kernel drives RDMA queues directly from GPU memory without host CPU mediation. Covers picking GPI vs doca-gpunetio, the doca_gpi / domain / channel object model, the GPU-side handle handoff (doca_gpu_gpi_channel*), attaching GPU memory to a GPI domain, the domain and channel attribute objects, and debugging DOCA_ERROR_* from doca_gpi_* calls. Trigger even when the user does not explicitly mention "
Passed 19 of 20 test cases with the skill, and 5 of 20 without it.
and 24 more in the full report
15 fixed6 passed either way1 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 13 test cases the skill fixed. Same model, same prompt, with and without the skill.
I am writing a build script for a C application using host GPI calls and compiling CUDA kernels with nvcc. What is the standard pkg-config dependency module name that should be referenced in the Meson build file?
| Checked | Without skill | With skill |
|---|---|---|
| Identifies doca-gpi as the pkg-config module name. | 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 GPI work on a host that has both
a BlueField / ConnectX device and an NVIDIA GPU reachable over
PCIe. 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 GPI express on this version — the domain +
channel object model, the GPU-side handle handoff, the relationship
to doca-gpunetio and doca-verbs, the attribute objects, and the
safety overlay. If the user has not installed DOCA yet, route to
doca-setup first.
The CLASSES of GPI 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-gpi or doca-gpunetio for this case?" —
worked example: "my CUDA kernel needs to post RDMA writes
directly to a remote DPU's memory — do I want the higher-level
Send/Receive surface or the lower-level channel/queue surface?".
Answered by the channel-level vs Send/Receive-level selection
rule in
CAPABILITIES.md ## Capabilities and modes
surface-selection table.CAPABILITIES.md ## Capabilities and modes
TASKS.md ## configure.doca_gpi_gpu_channel_get
returns a doca_gpu_gpi_channel* — how do I get that into my
CUDA kernel's argument list?". Answered by the GPU-handofftest cases passed, vs 5 / 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.