Use this skill when the user is doing hands-on DOCA Comch work on a host + BlueField pair — bringing up host ↔ DPU PCIe control-plane messaging, picking server (DPU) vs client (host) roles, choosing slow-path send-task / recv-callback vs fast-path producer / consumer, querying max-msg-size or max-clients capabilities, registering connection callbacks, or debugging DOCA_ERROR_* returns from the Comch API. Trigger even when the user does not explicitly mention "DOCA Comch" or "Comm Channel" (renam
SkillScore86Maintained
Automatic
◆Coding pack
Last verified 8/12/2026
What it changes
Passed 18 of 21 test cases with the skill, and 11 of 21 without it.
Without skill50%
With skill86%
Checks it passed that the model alone missed
Directs the user to doca-setup to install DOCA
Specifies doca-comch as the exact pkg-config module name
Avoids generating custom ring buffer or DMA code snippets
and 9 more in the full report
8 fixed11 passed either way3 still failing0 broke
Pass-rate lift
+36 pp
Tokens
+89%
Agent turns
0%
Response time
-21%
Model gemini-3.6-flashMeasured 8/12/2026v119 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 7 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 7
Prompt
Our DPU service needs to restrict the maximum number of simultaneous host client connections to 4. Which Comch property setter should be invoked during initialization?
What was checked, without and with the skill
Checked
Without skill
With skill
Names doca_comch_server_set_max_num_clients as the property setter function
Missed
Passed
case-16 · 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.md221 linessingle file
DOCA Comch
Where to start: This skill assumes DOCA is already installed and
the user is doing hands-on Comch work on a BlueField + host
pair with DOCA. 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 Comch express on this version. If the user has not
installed DOCA yet, route to
doca-setup first. If the user is
asking "is Comch even on this DOCA" because the docs they read
mention doca-comm-channel, route to
CAPABILITIES.md ## Version compatibility
for the 2.5 rename.
Example questions this skill answers well
The CLASSES of Comch 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 bring up a Comch channel between host and DPU?" —
worked example: "server side on the DPU, client side on the
host, exchange a first control message". Answered by the
role-selection + lifecycle workflow in
TASKS.md ## configure +
CAPABILITIES.md ## Capabilities and modes
server-vs-client table.
"How do I move bulk data over Comch with low CPU?" — worked
example: "stream a 64 KiB chunk every 100 µs from the host
driver to a DPU agent". Answered by the producer / consumer
fast-path described in
CAPABILITIES.md ## Capabilities and modes
the channel-setup workflow in
TASKS.md ## configure
step 4, with the "slow-path vs fast-path" selection rule.
"What is the maximum message size I can send?" — worked
example: "can I send a 4 MiB control message in one shot?".
Answered by the capability-query rule
(doca_comch_cap_get_max_msg_size) in
Use this skill for hands-on DOCA Compress programming on a BlueField DPU, ConnectX NIC, or host with DOCA — enabling compress-deflate, decompress-deflate, decompress-lz4-stream, or decompress-lz4-block tasks on a doca_compress context (the hardware supports DEFLATE both directions plus LZ4 decompress; LZ4 encode is NOT supported), sizing source / destination doca_buf against the per-task cap query, setting mmap permissions, deciding offload vs CPU zlib / zstd, validating with a round-trip smoke,