Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →nvidia/doca-telemetry-utils
Use this skill when the user is invoking `doca_telemetry_utils` on a host with DOCA installed — discovering the diagnostic-counter schema, translating counter names to binary Data IDs, validating per-device counter support before committing a DOCA Telemetry exporter config, or reverse-resolving a captured Data ID. Trigger even when the user does not explicitly mention "doca_telemetry_utils" or "Data ID" — typical implicit phrasings include "my exporter ships but the collector sees nothing", "thi
Passed 18 of 21 test cases with the skill, and 5 of 21 without it.
and 16 more in the full report
14 fixed5 passed either way3 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 13 test cases the skill fixed. Same model, same prompt, with and without the skill.
We are writing an automated host environment verification script for BlueField operators. Where on disk is the host-side DOCA Telemetry utility CLI binary located, and what is its exact executable name?
| Checked | Without skill | With skill |
|---|---|---|
| Identifies `/opt/mellanox/doca/tools/doca_telemetry_utils` as the location of the executable. | Missed | Passed |
The instructions your model reads when the skill loads.
Where to start: This is a tool skill for invoking
doca_telemetry_utils — the documented host-side CLI that
supports a DOCA Telemetry exporter / collector pipeline by
discovering the counter schema, translating counter names ↔
Data IDs, and probing per-device counter support. Open
TASKS.md and start at
## install for the host-side
prerequisites and ## run for the
three documented invocation classes
(enumerate / name→ID / ID→name). Open
CAPABILITIES.md when the question is
what does this tool actually discover about the telemetry
schema, how does it pair with the developer-side
doca-telemetry and
exporter libraries, how do I confirm a device supports a
counter before committing an exporter config to it, or
why does my exporter pipeline silently drop a metric.
This skill is the operator-side support tool for a
DOCA Telemetry deployment. It is NOT the developer-side
collector library (that is
doca-telemetry),
NOT the developer-side publisher library (that is
doca-telemetry-exporter — see
doca-telemetry ## Related skills),
and NOT a DOCA Telemetry Service (DTS) deployment guide
(route via
doca-public-knowledge-map).
Three separate surfaces; conflating them is the most
common telemetry first-touch error.
The CLASSES of doca_telemetry_utils 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.
test cases passed, vs 5 / 21 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.