Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →nvidia/doca-common
Use this skill whenever the user is doing hands-on DOCA programming on a BlueField DPU or ConnectX NIC and needs the foundation primitives every per-library context rests on — walking the doca_ctx lifecycle, discovering doca_dev / doca_devinfo and gating on doca_*_cap_* before trusting a feature, wiring doca_mmap / doca_buf_inventory / doca_buf for zero-copy I/O across libraries, driving doca_pe for completions, or DOCA Log's two-tier (--sdk-log-level vs app-side) model. Trigger even when the us
Passed 17 of 23 test cases with the skill, and 15 of 23 without it.
2 fixed15 passed either way6 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 2 test cases the skill fixed. Same model, same prompt, with and without the skill.
I am writing a custom C application that needs to share registered user-space memory across multiple DOCA acceleration libraries. Can you outline the exact sequence of API initialization and cleanup steps required for zero-copy memory buffers? Please format your answer as a numbered lifecycle guide detailing the sequence of resource allocation, mapping, inventory creation, and tear-down.
| Checked | Without skill | With skill |
|---|---|---|
| Includes doca_mmap setup in the buffer lifecycle sequence. | Passed | Passed |
| Includes doca_buf_inventory setup for buffer allocation. | Passed | Passed |
| Includes doca_pe_connect_ctx to integrate the progress engine with the context. | Missed | Passed |
The instructions your model reads when the skill loads.
Where to start: This skill is the foundation every DOCA app
loads first — before doca-flow, doca-rdma, doca-eth, doca-comch, or
any other higher-level library. Every doca_<library>_* context is
built on top of doca_ctx, every device handle is a doca_dev
discovered through doca_devinfo, every zero-copy buffer is a
doca_buf from a doca_buf_inventory over a doca_mmap, every
task completion drains through a doca_pe, and every log line emits
through doca_log. Open CAPABILITIES.md when
the question is what does Common express on this install; open
TASKS.md when the user wants to do something
(configure / build / modify / run / test / debug). If the user has
not installed DOCA yet, route to
doca-setup first. If the user is
already past the foundation and asking a library-specific question
(e.g. "how do I program a Flow pipe"), load the matching per-library
skill alongside this one — they cross-link back here for the shared
primitives.
The CLASSES of doca-common 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.
TASKS.md ## configure +
CAPABILITIES.md ## ctx +
CAPABILITIES.md ## dev +
CAPABILITIES.md ## progress engine.doca_eth_txq but the docs hint at a feature only on certain
firmware bands". Answered by the capability-discovery rule
(doca_devinfo_create_list → doca_*_cap_* against the activetest cases passed, vs 15 / 23 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.