Agent skill · NVIDIA
doca-pcc-ztr-rttcc-algo
Use this skill when the user is doing hands-on deployment, tuning, or evaluation of the DOCA-shipped Zero-Touch RoCE RTT-based Congestion Control (ZTR RTTCC) reference algorithm on a BlueField-3 DPA — wiring `doca_pcc_dev_ztr_rttcc_algo` into the shipped DOCA PCC sample, picking a variant (vanilla / PM / RX-rate / multipath / window-probeless) at DPACC build time, tuning host-set parameters, or diagnosing `DOCA_PCC_DEV_STATUS_FAIL` from the algorithm. Trigger even when the user does not say 'DOCA PCC' or 'ZTR RTTCC' — typical implicit phrasings: 'my RoCE-v2 flows aren't being throttled', 'PCC sample isn't dispatching to my algo', 'how do I pick the multipath PCC variant', 'set-params returns fail', 'algorithm loaded but counters are flat', or 'do I need a custom CC algorithm on BF3'. Refuse and route elsewhere for writing a custom PCC algorithm from scratch, read-only PCC counter inspection, the host-side `doca-pcc` lifecycle, or firmware-only pre-Programmable PCC — those belong to other skills.
What it needs
About 10k tokens when loaded.
What this skill does
DOCA PCC ZTR RTTCC Algorithm 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 (a BlueField-3-generation device per the README), the BlueField firmware has the custom-PCC slot enabled, the DPACC compiler is installed at a matched version per the DOCA Compatibility Policy, and the user is doing hands-on deployment of the DOCA-shipped ZTR RTTCC reference algorithm on a BlueField port that already carries RoCE-v2 traffic — i.e. either deploying it as the no-config-required baseline, tuning its documented parameters, or evaluating it against a custom algorithm the user intends to write. Open TASKS.md if the user wants to do something (install / configure / build / modify / run / test / debug / use); open CAPABILITIES.md when the question is what does the algorithm express, what are its variants and parameters, what does it ship vs not ship. If the user has not installed DOCA yet, route to doca-setup first; if the user has not stood up the host-side doca-pcc framework yet, route to doca-pcc first (this algorithm is a library consumed by the PCC framework, not a standalone program); if the user only wants to inspect PCC counters at runtime without changing the running algorithm, route to doca-pcc-counters; if the user wants to write their own algorithm from scratch, that is the doca-pcc library plus the public PCC programming guide — this skill is for the shipped reference algorithm specifically. Example questions this skill answers well The CLASSES of ZTR RTTCC 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. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills NVIDIA/doca-pcc-ztr-rttcc-algo