Use when reading DOCA hardware-counter events from a docadev via the per-domain DOCA Telemetry reader libraries — docatelemetrypcc, dpa, diag, adpretx, phy, pci. This is the counter-READER surface — there is no NetFlow / IPFIX / local-socket collector framework here; the bundle previously framed it that way and that framing is wrong. Each domain ships its own docatelemetry{domain} API: cap-query capissupported(devinfo), create() on a docadev, start(), then per-domain read / sample. Trigger even when the user does not say "DOCA Telemetry" — typical implicit phrasings: "read PCC counters from my BlueField app", "sample DPA counter exports", "expose PHY / PCI / DIAG counters from this docadev". Refuse and route elsewhere for the publishing / export side (doca-telemetry-exporter), DOCA Telemetry Service (DTS) as deployed (out of scope), NetFlow / IPFIX collectors, and plain stdout logging.
Install with
Claude CodeCodexCursorGitHub CopilotGemini CLI
Supported by the Atlas install prompt. Skill-specific requirements vary.
Skill stats
Skills1CategoryGeneralStars0
About this skill
Use when reading DOCA hardware-counter events from a docadev via the per-domain DOCA Telemetry reader libraries — docatelemetrypcc, dpa, diag, adpretx, phy, pci. This is the counter-READER surface — there is no NetFlow / IPFIX / local-socket collector framework here; the bundle previously framed it that way and that framing is wrong. Each domain ships its own docatelemetry{domain} API: cap-query capissupported(devinfo), create() on a docadev, start(), then per-domain read / sample. Trigger even when the user does not say "DOCA Telemetry" — typical implicit phrasings: "read PCC counters from my BlueField app", "sample DPA counter exports", "expose PHY / PCI / DIAG counters from this docadev". Refuse and route elsewhere for the publishing / export side (doca-telemetry-exporter), DOCA Telemetry Service (DTS) as deployed (out of scope), NetFlow / IPFIX collectors, and plain stdout logging.
Quick start
Copy the install prompt. Use the green button above this README.
Send it to your agent. Paste it into your coding agent’s chat and send.
Review the setup. Your agent checks the skill’s instructions, requirements, and installation scope.
Use this skill when reading **DOCA hardware-counter events** from a `doca_dev` via the per-domain DOCA Telemetry reader libraries — `doca_telemetry_pcc`, `_dpa`, `_diag`, `_adp_retx`, `_phy`, `_pci`. This is the **counter-READER** surface — there is no NetFlow / IPFIX / local-socket collector framework here; the bundle previously framed it that way and that framing is wrong. Each domain ships its own `doca_telemetry_{domain}_*` API: cap-query `_cap_is_supported(devinfo)`, `_create()` on a `doca_dev`, `_start()`, then per-domain read / sample. Trigger even when the user does not say "DOCA Telemetry" — typical implicit phrasings: "read PCC counters from my BlueField app", "sample DPA counter exports", "expose PHY / PCI / DIAG counters from this `doca_dev`". Refuse and route elsewhere for the publishing / export side (`doca-telemetry-exporter`), DOCA Telemetry Service (DTS) as deployed (out of scope), NetFlow / IPFIX collectors, and plain stdout logging.
About this listing
Category
General
Reported license
Apache-2.0
Listing language (estimated)
English
Review status
Not individually reviewed
Agent compatibility
Atlas installation supports Claude Code, Codex, and Cursor. Skill-specific dependencies and features are checked during setup.
Claude Code
Codex
Cursor
GitHub Copilot
Gemini CLI