Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →nvidia/doca-pcc-counters
Use this skill when the user is invoking the DOCA PCC Counters tool — the `pcc_counters.sh` bash script under the DOCA tools directory — to arm and read the fixed firmware/hardware PCC (Programmable Congestion Control) diagnostic counters (CNP, RTT, WRED-drop, etc.) on a ConnectX / BlueField device via mst + the mlx5 debugfs `diag_cnt` interface. The script takes two positional args — `set | query` and an mst device path — with no `--help` or subcommands. Trigger even without "pcc_counters.sh" o
Passed 19 of 21 test cases with the skill, and 5 of 21 without it.
and 19 more in the full report
15 fixed5 passed either way2 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 14 test cases the skill fixed. Same model, same prompt, with and without the skill.
I want to pass `--interval 5 --watch` flags to `pcc_counters.sh` to poll the counters continuously. What is the syntax for flag options in this utility?
| Checked | Without skill | With skill |
|---|---|---|
| states that pcc_counters.sh accepts no command-line flags or subcommands beyond set and query with an mst path | Missed | Passed |
| advises running a shell loop around pcc_counters.sh query for repeated sampling | Missed | Passed |
The instructions your model reads when the skill loads.
pcc_counters.sh)Where to start: This is a tool skill for invoking
pcc_counters.sh — a small bash script that arms and reads the
device's fixed set of firmware / hardware PCC diagnostic
counters (CNP count, RTT-perf, WRED-drop, RTT-gen, handled
events) through the mlx5 debugfs diag_cnt interface. Open
TASKS.md and start at ## run for
the canonical set-then-query sequence, or
## debug when the user reports
"ERROR: Bad Device", "counter stuck at zero", or "the
dump is empty". Open CAPABILITIES.md when
the question is which counters the script reports and how it
reaches them. If the user has not installed DOCA / MFT yet,
route to doca-setup first.
This skill is the firmware / HW PCC counter readout surface.
It is NOT the host-side control library that loads custom
congestion-control kernels onto the DPA (that is
doca-pcc) and it is NOT the
firmware PCC algorithm configuration (that path is firmware
configuration, routed via
doca-public-knowledge-map).
The counters this script reads are device / firmware
diagnostic counters that exist regardless of whether a custom
doca-pcc DPA kernel is running — do not condition them on a
custom kernel being loaded.
The CLASSES of pcc_counters.sh questions this skill is built
to answer, each with one worked example. The class is the
load-bearing piece; the worked example is one instance.
/dev/mst/mt41692_pciconf0".
Answered by the fixed counter set in
CAPABILITIES.md ## Capabilities and modes
set-then-query invocation intest cases passed, vs 5 / 21 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.