Individual skill
doca-telemetry
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 NetFlow, IPFIX, or local-socket collector. Route publishing and export to `doca-telemetry-exporter`; route the deployed DOCA Telemetry Service to `doca-dts`, and collectors and plain stdout logging elsewhere.
skills/doca-telemetry/SKILL.md
Source commit 25340619336e89bcc40365c28bfe9e790430468e
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 2, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 3,889
- Repository last updated
- Nov 6, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-skills Repository topic
- agentic-ai Repository topic
- ai-agents Repository topic
- claude-code Repository topic
- codex Repository topic
- coding-agents Repository topic
- cuda Repository topic
- developer-tools Repository topic
- llm Repository topic
- omniverse Repository topic
- doca Declared skill tag
- telemetry Declared skill tag
- counters Declared skill tag
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
BENCHMARK.mddoc · 10,148 bytesCAPABILITIES.mddoc · 27,241 bytesSKILL.mdcore · 15,020 bytesSKILL.mdcore · 15,020 bytesSKILL.mdcore · 15,020 bytesSKILLCARD.yamlasset · 2,841 bytesTASKS.mddoc · 30,433 bytesevals/evals.jsonasset · 2,534 bytesreferences/details.mddoc · 6,770 bytesskill-card.mddoc · 5,457 bytesskill.oms.sigasset · 5,477 bytes
Read excerpt
# 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.