Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →nvidia/doca-telemetry-exporter
Use this skill when the user is doing hands-on DOCA Telemetry Exporter programming on a host where DOCA is installed — defining a doca_telemetry_exporter_schema, creating sources, picking counter/gauge/event types, running capability queries before assuming limits, registering schemas before the first emit, or debugging DOCA_ERROR_* failures from the exporter API. Trigger even when the user does not explicitly mention "DOCA Telemetry Exporter" or "doca_telemetry_exporter_*" — typical implicit ph
Passed 18 of 21 test cases with the skill, and 6 of 21 without it.
and 11 more in the full report
13 fixed6 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.
I am drafting a Meson build file for a C program that uses DOCA Telemetry Exporter. I am using dependency('doca-telemetry') in my meson.build file. What is the exact pkg-config module name I should pass to dependency()?
| Checked | Without skill | With skill |
|---|---|---|
| Specifies the pkg-config module name doca-telemetry-exporter. | Missed | Passed |
The instructions your model reads when the skill loads.
Where to start: This skill assumes DOCA is already installed and
the user is doing hands-on telemetry-exporter work — emitting
structured application telemetry (counters / events) from a
DOCA-using program to an external consumer. Open
TASKS.md if the user wants to do something (configure
/ build / modify + rebuild / run / test / debug); open
CAPABILITIES.md when the question is what can
the exporter express on this install. If the user has not installed
DOCA yet, route to doca-setup first.
If the user is confused about whether they want this library or the
DOCA Telemetry Service (the receiver) — read the
exporter-vs-service rule in
CAPABILITIES.md ## Capabilities and modes
before configuring anything.
This library is NOT a DOCA Core context. There is no
doca_ctx_start()for the exporter and no per-doca_devinfocapability-query family (itsdoca_capsdump is a stub). The lifecycle isschema_init→ configure exporters → register type(s) →schema_start→source_create→source_start→ report → flush → destroy.
The CLASSES of telemetry-exporter 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.
CAPABILITIES.md ## Capabilities and modes
role-split table + the path-selection bullet, both of which name
doca-telemetry-exporter as the publisher the application links
and route the receiving / consuming side away from this skill.test cases passed, vs 6 / 21 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.