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,
SkillScore95Maintained
Automatic
◆Coding pack
Last verified 8/12/2026
What it changes
Passed 21 of 22 test cases with the skill, and 13 of 22 without it.
Without skill59%
With skill95%
Checks it passed that the model alone missed
Directs escalation to the doca-debug skill.
Identifies the pkg-config module name as doca-compress.
Model gemini-3.6-flashMeasured 8/12/2026v121 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 8
Prompt
I am creating a Makefile for my C application using pkg-config to discover compilation flags for the compression library. What is the exact package module name?
What was checked, without and with the skill
Checked
Without skill
With skill
Identifies the pkg-config module name as doca-compress.
Missed
Passed
case-11 · 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.md269 linessingle file
DOCA Compress
Where to start: This skill assumes DOCA is already installed and
the user is doing hands-on Compress work (bulk DEFLATE
compression or decompression) on a BlueField / ConnectX / host
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
DOCA Compress express on this version. If the user has not
installed DOCA yet, route to
doca-setup first. If the user is
asking "should I even offload this compression to the
accelerator?", the size-threshold path-selection rule in
CAPABILITIES.md ## Capabilities and modes
is the first stop — bulk compress is the canonical fit, tiny
one-shot is not.
Example questions this skill answers well
The CLASSES of DOCA Compress 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 offload this compression to DOCA Compress, or just
zlib/zstd on the CPU?" — worked example: "I am compressing a
4 MiB log buffer before writing it to storage; is doca-compress
worth the setup vs zlib on the CPU?". Answered by the
size-threshold path-selection rule in
CAPABILITIES.md ## Capabilities and modes
the "when NOT to use doca-compress" bullets in
CAPABILITIES.md ## Safety policy.
"Does my device support the compress (or decompress) task I
want, and how big a buffer can it move per submission?" —
worked example: "is doca_compress_task_compress_deflate on
this BlueField, and what is the max source size per task?".
Answered by the per-task capability-query rule
(doca_compress_cap_task_compress_deflate_is_supported,
_decompress_deflate_is_supported, the matching
_get_max_buf_size queries) in
Use this skill when the user is doing hands-on DOCA Device Emulation on a BlueField DPU — exposing a custom emulated PCIe device the host sees as a real peripheral while DPU-side code runs the backend, picking the sub-library (PCI Generic, virtio-net, virtio-fs), wiring the per-sub-library Core context plus doorbell / DMA primitives, querying `doca_devemu_*_cap_*`, or debugging DOCA_ERROR_* from a `doca_devemu_*` call. Trigger even when the user does not say "devemu" — typical implicit phrasings