Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →nvidia/doca-dpdk-bridge
Use this skill when the user has an existing DPDK application and is adding DOCA capabilities in-place — most commonly DOCA Flow hardware steering — without rewriting the data-plane in DOCA-native form: binding a DPDK port id to a `doca_dev` (`doca_dpdk_port_probe` / `doca_dpdk_port_as_dev`), converting `rte_mbuf` ↔ `doca_buf`, querying `doca_dpdk_cap_is_rep_port_supported`, or debugging `DOCA_ERROR_*` from a bridge call. Trigger even without "DOCA DPDK Bridge": "how do I add DOCA Flow to my DPD
Passed 10 of 19 test cases with the skill, and 4 of 19 without it.
and 10 more in the full report
7 fixed5 passed either way10 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 5 test cases the skill fixed. Same model, same prompt, with and without the skill.
We are architecting a new line-rate packet generation tool from scratch and evaluating whether to use DPDK or DOCA native queue interfaces (`doca_eth_rxq` / `doca_eth_txq`). Which skill guidance should be loaded for fresh DOCA packet I/O development?
| Checked | Without skill | With skill |
|---|---|---|
| Directs the user to `doca-eth` for new projects seeking fresh DOCA-native packet I/O performance. | Missed | Passed |
| Explains that the bridge is designed specifically for interop with existing DPDK applications, not fresh starts. | Missed | Passed |
The instructions your model reads when the skill loads.
Where to start: This skill assumes DOCA is already installed,
DPDK is already installed, the user has an existing DPDK
application, and they want to add DOCA capabilities to it
in-place (most commonly DOCA Flow for hardware steering)
without migrating the data-plane to DOCA-native APIs. Open
TASKS.md if the user wants to do something
(configure / build / modify / run / test / debug); open
CAPABILITIES.md when the question is what
the bridge can express on this version. If the user has not
installed DOCA yet, route to
doca-setup first. If the user is
starting fresh (no DPDK code yet) and just wants line-rate
packet I/O against DOCA, route to
doca-eth instead — the bridge exists
for the interop case, not the start-fresh case.
The CLASSES of DOCA DPDK Bridge 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.
rte_eth_*
ports; I want to install DOCA Flow steering rules on those
ports for HW offload". Answered by the bridge-vs-native
selection rule in
CAPABILITIES.md ## Capabilities and modes
TASKS.md ## configure step 3.rte_eth_dev_*; how does
DOCA see it". Answered by the DPDK-port-id ↔ doca_dev
mapping (doca_dpdk_port_probe / doca_dpdk_port_as_dev) in
CAPABILITIES.md ## Capabilities and modes
bridge-objects table + the binding workflow intest cases passed, vs 4 / 19 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.