doca-telemetry SKILL.md skillA
doca-telemetry from nvidia/skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add nvidia/skills/doca-telemetry@git:20261028.3d06e7ePins git:20261028.3d06e7e in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- nvidia/skills
- Path
skills/doca-telemetry/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261028.3d06e7e, committed Oct 28, 2026
- First version recorded
- Jul 17, 2026
- Size
- 15,020 bytes
- Repository stars
- 3,871
- License
- Apache-2.0
Use this skill to read DOCA hardware-counter events from a `doca_dev` through the per-domain Telemetry reader libraries: `doca_telemetry_pcc`, `_dpa`, `_diag`, `_adp_retx`, `_phy`, and `_pci`. It covers capability checks, context creation, startup, and per-domain reads or samples. Trigger for implicit requests such as "read PCC counters from my BlueField app", "sample DPA counter exports", or "expose PHY, PCI, or DIAG counters from this doca_dev". This is the counter-reader surface, not a…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# DOCA Telemetry ## Examples - **"Build a second program that RECEIVES the events my exporter app publishes."** No DOCA library consumes exporter events, and this skill is not that library: `doca-telemetry` reads a device's hardware counters. The app links `doca-telemetry-exporter` to publish; the receiver is the DOCA Telemetry Service over IPC (`doca-dts`), or the exporter's file output for a local smoke. Do not invent a consume or collector API. Then: the publishing app owns the schema; check the IPC path with `doca_telemetry_exporter_check_ipc_status`; smoke one event with field values intact (file output) before bulk; when reporting cannot keep up, drop or aggregate on the hot path, never block. - **"Read PCC counters from my BlueField app."** — this is in scope. Use the per-domain Telemetry reader; do not stand up DTS or an exporter here. Sequence: `doca_telemetry_pcc_cap_is_supported` on the device, create the PCC context on the open `doca_dev` (`doca_telemetry_pcc_rep_create` for a representor), start it, read once with `doca_telemetry_pcc_get_counters`, then stop and destroy. Reads before start return `DOCA_ERROR_BAD_STATE`. …
Read the whole file at its exact version.
How to install
mdr add nvidia/skills/doca-telemetry@sha256:69f195b910a092c5The line at the top of this page pins the label git:20261028.3d06e7e, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_wkwxrzufl3tq3oi7)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Jul 17, 2026 and Oct 28, 2026, about one every 26 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261028.3d06e7e latest | 2026-10-28 | 3d06e7e | 15,020 B | A | view · diff |
| git:20261022.a4cf47e | 2026-10-22 | a4cf47e | 15,083 B | A | view · diff |
| git:20261014.bbb601a | 2026-10-14 | bbb601a | 15,061 B | A | view · diff |
| git:20260727.a5736e4 | 2026-07-27 | a5736e4 | 11,129 B | A | view · diff |
| git:20260717.f64fa0e | 2026-07-17 | f64fa0e | 11,251 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (15020 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
nvidia/skills · 3,871 stars · license Apache-2.0 · pushed 2026-11-05 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_wkwxrzufl3tq3oi7 GET https://markdownregistry.com/api/v1/resolve?ref=nvidia/skills/doca-telemetry GET https://markdownregistry.com/api/v1/blob/69f195b910a092c519ee20221ac9d1498b3a3724deb31b600946c207b8cabda7
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.