Use this skill when the user is doing hands-on DOCA DPA host-side work on a BlueField — creating the `doca_dpa` Core context, loading a DPACC-compiled DPA app image (`doca_dpa_app`), creating DPA threads, launching kernels via `doca_dpa_kernel_launch_update_*`, draining `doca_dpa_completion`, running `doca_dpa_cap_*` discovery, choosing between the DPA comm component (inter-DPA messaging) and the DPA verbs component (in-kernel RDMA), or debugging `DOCA_ERROR_*` from `doca_dpa_*`. Trigger even wi
SkillScore77Maintained
Automatic
◆Coding pack
Last verified 8/12/2026
What it changes
Passed 16 of 21 test cases with the skill, and 11 of 21 without it.
Without skill50%
With skill77%
Checks it passed that the model alone missed
Specifies checking host software versioning using pkg-config --modversion doca-dpa.
Specifies the doca_dpa_kernel_launch_update_ API family for updating launch parameters.
Requires that the installed DPACC compiler version strictly matches the host DOCA SDK version.
and 5 more in the full report
6 fixed11 passed either way5 still failing0 broke
Pass-rate lift
+27 pp
Tokens
+191%
Agent turns
0%
Response time
-32%
Model gemini-3.6-flashMeasured 8/12/2026v117 of 22 cases passed with skill · 21 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 5 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 5
Prompt
My host application needs to determine the maximum allowed continuous execution time for a DPA kernel on the installed BlueField device. Which DOCA DPA host capability query function provides this limit?
What was checked, without and with the skill
Checked
Without skill
With skill
Identifies doca_dpa_cap_get_max_kernel_time_alive_supported as the function returning the maximum kernel lifetime.
Missed
Passed
case-19 · gemini-3.6-flash · 8/12/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md356 linessingle file
DOCA DPA
Where to start: This skill assumes DOCA is already installed,
the user's BlueField has a DPA processor and the host can see it
through DOCA, and the user is doing hands-on DPA work from the
host side — i.e. using doca-dpa to load a DPA application
image, launch DPA kernels, and exchange data with the DPA
processor. Open TASKS.md if the user wants to do
something (configure / build / modify / run / test / debug); open
CAPABILITIES.md when the question is what
can the host-side DPA API express on this version + this
BlueField generation. If the user has not installed DOCA yet,
route to doca-setup first; if the
user is asking how to write the DPA-side kernel itself (the
code that runs on the DPA processor, compiled by dpacc), that
is a different scope — route via
doca-public-knowledge-map
to the public DOCA DPA / DPACC / DPA-Comms / DPA-Verbs guides
(this skill does not redefine those DPA-side surfaces).
Example questions this skill answers well
The CLASSES of DPA 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.
"How do I run a piece of compute on the DPA processor from
my host program?" — worked example: "load a DPA kernel that
counts events in a loop and reports the count back to the
host". Answered by the two-side-program model + the
host-side launch workflow in
CAPABILITIES.md ## Capabilities and modes
the bring-up steps in
TASKS.md ## configure.
"Does this BlueField even have a DPA, and which DPA features
does my DOCA install expose?" — worked example: "my host
has a BlueField; can I use the DPA on it for a programmable
control workload?". Answered by the dual-axis capability rule
(BlueField-generation axis via doca_dpa_cap_* against the
Use this skill when the user is doing hands-on DOCA Erasure Coding programming on a BlueField DPU, ConnectX NIC, or host — bringing up a doca_ec context, picking among the create / recover / update tasks, choosing matrix type / N / K / block size, querying doca_ec_cap_* before sizing, setting doca_mmap src/dst permissions, or debugging DOCA_ERROR_* returns from doca_ec_task_*. Trigger even when the user does not name "DOCA Erasure Coding" or "Reed-Solomon" — typical implicit phrasings include "o