Use this skill to deploy and operate a CollectX (clx) based DOCA telemetry collector on a host or BlueField — wiring providers / counters into the collector, running the collection daemon, and shaping its exporters (Prometheus pull, Fluent Bit push, NetFlow, file / IPC) so the metrics actually leave the box. Trigger even when the user never says CollectX or clx — implicit phrasings: {collector emits nothing downstream}, {add a provider to the clx collector}, {turn on the Prometheus endpoint}, {s
SkillScore77Maintained
Automatic
◆DevOps & SRE pack
Last verified 8/12/2026
What it changes
Passed 17 of 22 test cases with the skill, and 7 of 22 without it.
Without skill32%
With skill77%
Checks it passed that the model alone missed
Routes productized DTS container questions to public documentation.
Directs the user to public DOCA documentation for DTS container manifests.
States the four-surface telemetry decomposition before giving diagnostic steps.
and 15 more in the full report
10 fixed7 passed either way5 still failing0 broke
Pass-rate lift
+45 pp
Tokens
+88%
Agent turns
0%
Response time
-26%
Model gemini-3.6-flashMeasured 8/12/2026v117 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 10
Prompt
The CollectX collector is running and providers are emitting counter rows, but the exporter outputs empty metric streams. What pipeline stage is likely mismatched?
What was checked, without and with the skill
Checked
Without skill
With skill
Identifies schema mapping between provider counter rows and exporter fields as the failing stage.
Missed
Passed
Recommends inspecting schema mapping definitions against provider output definitions.
Missed
Passed
case-11 · gemini-3.6-flash · 8/12/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md197 lines2 files
DOCA CollectX telemetry deployment
Where to start: This skill is the bundle's home for
operating a CollectX (clx) based telemetry collector — the
collection framework that gathers provider counters into a
schema and ships them out through one or more exporters. It is a
deployment / operation skill, parallel to
doca-bare-metal-deployment
and doca-container-deployment:
it owns the runtime shape of a telemetry collector on the
operator's host or BlueField, not the library APIs the operator's
own program calls. If the user wants to stand up, wire, or debug
a collector and its exporters, open TASKS.md and
start at ## configure. If the question is
what surfaces does the collector even have and where is the
scope boundary, start at CAPABILITIES.md.
If the user has not installed DOCA yet, route to
doca-setup first.
The scope boundary (read this before anything else)
CollectX (clx) is NVIDIA's telemetry collection framework. It
underpins the DOCA Telemetry Service (DTS) — and DTS
as-deployed (the productized, NGC-shipped / kubelet-started
service container) is out of scope for this bundle per
AGENTS.md Non-goal #7.
This skill therefore draws a hard line and the agent MUST state
it up front:
In scope here: the CollectX collection mechanism as a
class (providers / counters → schema → collector daemon →
exporters), and the operator deploying / running / debugging a
collector that they own, plus the operator's own usage of the
two in-bundle telemetry libraries when those feed or
consume the collector.
Routed to the DOCA telemetry libraries: the
hardware-counter reader API is owned by
doca-telemetry; the
application-side publisher API (emit counters / events from
a DOCA program) is owned by
Use this skill whenever the user is doing hands-on DOCA programming on a BlueField DPU or ConnectX NIC and needs the foundation primitives every per-library context rests on — walking the doca_ctx lifecycle, discovering doca_dev / doca_devinfo and gating on doca_*_cap_* before trusting a feature, wiring doca_mmap / doca_buf_inventory / doca_buf for zero-copy I/O across libraries, driving doca_pe for completions, or DOCA Log's two-tier (--sdk-log-level vs app-side) model. Trigger even when the us