Is Doca Telemetry safe and trustworthy?

tashan scores Doca Telemetry on public evidence — it is currently active. Audit scope: OSV advisories, install-time scripts, build provenance and declared permission surface. We do not review source code or execute the capability.

How do I install Doca Telemetry?

Drop the skill folder into ~/.claude/skills/ (user scope) or .claude/skills/ (project scope).

Who maintains Doca Telemetry?

30 GitHub contributors, source: NVIDIA/skills.

‹ The Index

Doca Telemetry

skill

Author’s activation text, quoted as published

Use this skill to read DOCA hardware-counter events from a docadev through the per-domain Telemetry reader libraries: docatelemetrypcc, dpa, diag, adpretx, 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 docadev". This is the counter-reader surface, not a NetFlow, IPFIX, or local-socket collector. Route publishing and export to doca-telemetry-exporter; route deployed DOCA Telemetry Service (DTS), collectors, and plain stdout logging elsewhere.

Works with: Claude Code (native) · Cursor, Codex CLI (manual)
native: this artifact type is that client's own format

Install (Claude Code):

cp -r doca-telemetry ~/.claude/skills/

Adoption: 1 repos
Upkeep: 96.0
Freshness: 92.0
Evidence coverage: 84% of the inputs this score can use — the rest are unknown, and the score is discounted for it
Health: active
Contributors: 30
License: Apache-2.0

Security audit

Not scanned yet. We audit npm-published capabilities for known advisories, install-time scripts and permission surface; this one has no npm package we can resolve, or has not reached the queue.

Its own instructions

Its SKILL.md says when not to and covers setup.

Read from the capability’s own SKILL.md. This is not a grade and does not compare to the instruction-depth verdict on an MCP server — a skill has no tools to document, so that rubric does not apply to it.

You searched for one. Check the rest of your stack:

npx tashan-cli doctor

Reads the config already on your machine and names what is dead, deprecated or running code at install time. No account, nothing uploaded.

tashan Pro$6/mo

Pro adds the history to tashan doctor, so a run over your own config says which of yours gained an advisory, started running an install script, or lost its last maintainer — and what to move to.

Every score since we started measuring, for any capability
The named replacement when something you run is dying — not just that it is
tashan doctor over the config you already have, on your machine

Start a 7-day trial › Everything measured on this page stays free.

source ↗ · skill:NVIDIA/doca-telemetry

Everything on this page is public evidence and free. What it cannot know is whether you run this — check your whole config, free, in the browser. tashan Pro adds the series behind each row and names a replacement for anything dying.

Already running this? Check your whole config — free, in your browser, nothing installed. Or npx tashan-cli doctor locally, which sends nothing at all.

Measured 2026-08-20 · scorer s5 · how · something wrong here?