Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →nvidia/doca-pcc
Use this skill when the user is doing hands-on host-side DOCA PCC work to load a CUSTOM Programmable Congestion Control algorithm onto a BlueField DPU — creating per-port `doca_pcc` contexts, loading a `dpacc`-compiled `doca_pcc_app` onto the `doca_dev` for the RoCE-bearing port, parameterizing it, walking triple-axis capability discovery (DOCA cap-query + DPA-capable BlueField + firmware custom-PCC slot enabled), or debugging `DOCA_ERROR_*` from `doca_pcc_*`. Trigger even without explicit "DOCA
Passed 17 of 21 test cases with the skill, and 8 of 21 without it.
and 10 more in the full report
11 fixed7 passed either way3 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
Where is the canonical helper shell script for reading runtime PCC diagnostic counters located inside the DOCA installation tree?
| Checked | Without skill | With skill |
|---|---|---|
| Identifies `tools/pcc_counters/` as the directory path for the diagnostic counter script. | Missed | Passed |
The instructions your model reads when the skill loads.
Where to start: This skill assumes DOCA is already installed,
the user's BlueField has a DPA processor that the host can see
through DOCA, the BlueField firmware has the custom-PCC slot
enabled, and the user is doing hands-on custom PCC work from
the host side — i.e. using doca-pcc to load a DPA-side
congestion control algorithm onto the BlueField, attach it to a
port handling RDMA / RoCE traffic, and parameterize it from the
host. 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 PCC API express on this version + this
BlueField generation + this firmware. If the user has not
installed DOCA yet, route to
doca-setup first; if the user is
asking how to write the DPA-side congestion-control algorithm
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 PCC programming guide and to
doca-dpa for the host-side DPA
lifecycle this skill builds on. If the user only wants to
inspect PCC counters at runtime without writing a custom
algorithm, that is the pcc_counters CLI tool — route via
doca-public-knowledge-map ## DOCA tools;
this skill is for custom algorithms only.
The CLASSES of PCC 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.
test cases passed, vs 8 / 21 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.