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 PCC" phrasing — implicit forms include "loading my own congestion control onto a BF port", "DOCA_
npx skills add NVIDIA/skills --skill doca-pcc --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
What it does
This skill instructs the agent to assist with hands-on host-side DOCA PCC work, specifically to load a custom congestion-control algorithm onto a BlueField DPU. It covers creating per-port doca_pcc contexts, loading a dpacc-compiled doca_pcc_app onto the doca_dev for the RoCE port, parameterizing the algorithm, and starting the PCC context so it influences RDMA/RoCE traffic. It also checks supported PCC features via doca_pcc_cap_* against the active doca_devinfo, and helps debug DOCA_ERROR_* from doca_pcc_* calls (distinguishing firmware-slot issues, device support, and image compatibility). It encourages designing host-side bindings in non-C languages that drive a custom PCC image built with dpacc, while routing out-of-scope topics to other materials.
How it works
- Initialize a doca_pcc against a doca_dev corresponding to the BlueField port.
- Load the PCC algorithm image (doca_pcc_app) produced by dpacc into the doca_pcc context.
- Parameterize the loaded algorithm using host-side knobs exposed by the PCC, then start the doca_pcc Core context to affect traffic.
- Query capabilities with the doca_pcc_cap_* family against the active doca_devinfo to verify support across BlueField generations and firmware revisions.
- Debug DOCA_ERROR_* errors from doca_pcc_* calls, distinguishing firmware-slot issues, device support, and image compatibility.
- Provide guidance for host-side bindings in non-C languages that drive the PCC workflow, while noting boundaries of scope.
When to use it
Use when performing hands-on host-side DOCA PCC work for a custom congestion-control algorithm, including initializing, loading, parameterizing, running, testing, debugging, and validating capabilities on the target BlueField port.
What it can touch
- The host-side doca_pcc API and related doca_dev context, via host C library with pkg-config module name doca-pcc.
- The loaded doca_pcc_app image produced by dpacc.
- The doca_pcc_cap_* capability query surface and doca_devinfo.
- The DOCA_ERROR_* error taxonomy mapped to doca_pcc_* calls.
Caveats
- Requires DOCA SDK installed at /opt/mellanox/doca and a DPACC-compiled PCC image compatible with the host DOCA version.
- The skill does not provide DPA-side algorithm-body design, default factory PCC details, or pcc_counters tool guidance; those are routed to other materials.
- It enforces that the user understands how to write the DPA-side algorithm with dpacc and how to configure the environment per the safety policy.
# DOCA PCC **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
What does the doca-pcc skill do?
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 PCC" phrasing — implicit forms include "loading my own congestion control onto a BF port", "DOCA_
How do I install it?
Run `npx skills add NVIDIA/skills --skill doca-pcc --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From NVIDIA/skills, a repository with 2,789 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.