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 phrasings include "publishing counters from my DOCA app", "emit returns AGAIN under bulk load", "consumer sees nothing but emit reports success", "NOT_FOUND on first submit", or "should I link the exporter or the telemetry service". Refuse and route elsewhere for the receiving DOCA Telemetry Service, plain stdout logging via doca_log, non-DOCA Prometheus scrape sinks, or real-time event subscription back into the app via doca-comch — those belong to other skills.
Security AStatic scan found no risk patternsHow grading works ›
From the source SKILL.md
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](TASKS.md) if the user wants to do something (configure / build / modify / run / test / debug); open [CAPABILITIES.md](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](../../doca-setup/SKILL.md) first. If the user is confused about whether they want this…
What this skill does
Doca Telemetry Exporter is a community-contributed Claude Code skill in the observability sub-category. It ships as a SKILL.md file that Claude Code auto-discovers under ~/.claude/skills/doca-telemetry-exporter/ and loads when your prompt matches the skill's trigger.
Who uses this skill
The Doca Telemetry Exporter Claude Code skill is built for software engineers, backend developers, full-stack teams, and technical leads building and maintaining production systems. It's part of ClaudSkills (also referred to as Claude Skills or Claude Code Skills) — the open community-curated registry of 159,000+ SKILL.md files for Anthropic's Claude Code agent and the wider Claude ecosystem (Claude API, Claude Agent SDK).
How to install
Free
Manual install (2 steps)
mkdir -p ~/.claude/skills/doca-telemetry-exporter
curl -L https://claudskills.com/skills/doca-telemetry-exporter/SKILL.md \
-o ~/.claude/skills/doca-telemetry-exporter/SKILL.md
Or just download SKILL.md directly and drop it into ~/.claude/skills/doca-telemetry-exporter/. Claude Code auto-discovers it on next session.
Skills live at ~/.claude/skills/doca-telemetry-exporter/SKILL.md on macOS/Linux, or %USERPROFILE%\.claude\skills\doca-telemetry-exporter\SKILL.md on Windows. See the full install guide for step-by-step instructions.
Telegram
📱 Install from your phone or desktop Telegram
Open @claudskills_bot on Telegram, tap Open Desktop App, and the desktop app installs this skill for you. Or share the bot link with a colleague — they get the same one-tap install. Learn more →
Pro
One-click install via the desktop app
The ClaudSkills desktop app installs any skill directly into ~/.claude/skills/ with one click — no terminal required. Pro starts at $9/mo or $149 lifetime.
Pro
For the full experience including quality scoring and one-click install features for each skill — upgrade to Pro.
Frequently asked questions
How do I install the Doca Telemetry Exporter Claude Code skill?
Install via the ClaudSkills desktop app (one click) or copy
SKILL.md from the source repository to
~/.claude/skills/doca-telemetry-exporter/SKILL.md and restart Claude Code. Both flows are detailed at
claudskills.com/install/.
What does the Doca Telemetry Exporter skill do?
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 phrasings include "publishing counters from my DOCA app", "emit returns AGAIN under bulk load", "consumer sees nothing but emit reports success", "NOT_FOUND on first submit", or "should I link the exporter or the telemetry service". Refuse and route elsewhere for the receiving DOCA Telemetry Service, plain stdout logging via doca_log, non-DOCA Prometheus scrape sinks, or real-time event subscription back into the app via doca-comch — those belong to other skills.
Is this skill free to install?
Yes. ClaudSkills is an open registry — every skill keeps its source repository's license, and manual install via copy is free. ClaudSkills Pro ($9/mo, $79/yr, or $149 one-time) adds one-click install via the desktop app and a multi-signal Quality Score.
When should I use the Doca Telemetry Exporter skill?
Use Doca Telemetry Exporter when your Claude Code task falls under the Engineering category — specifically in the observability area. Claude Code auto-discovers installed skills and invokes the right one based on the task description, so you can also ask Claude directly (e.g. "use Doca Telemetry Exporter" or describe the task and let Claude pick). Browse related skills at
/category/engineering/.
What is a Claude Code skill and how does the Doca Telemetry Exporter skill fit in?
A Claude Code skill is a
SKILL.md file that lives under
~/.claude/skills/<name>/ and tells the Claude Code CLI agent how to perform a specific task (instructions, prompts, allowed tools). Skills are auto-discovered at session start. Doca Telemetry Exporter is one of 67,000+ skills indexed in the open ClaudSkills catalog, classified under the Engineering category. Learn more at
/learn/what-is-a-claude-skill/.
Attribution & license
Cite this skill
If you reference this skill in a blog post, paper, or documentation, you can cite it as:
APA
NVIDIA. (2026). Doca Telemetry Exporter [Claude Code skill]. ClaudSkills. https://claudskills.com/skills/doca-telemetry-exporter/
BibTeX
@misc{doca-telemetry-exporter-2026,
author = {NVIDIA},
title = {Doca Telemetry Exporter [Claude Code skill]},
year = {2026},
publisher = {ClaudSkills},
url = {https://claudskills.com/skills/doca-telemetry-exporter/}
}Embed this skill
Promote, attribute, or link this skill from your own README, blog post, or documentation. All three snippets are free to use — no sign-up, no API key. More distribution surfaces →
Badge
[](https://claudskills.com/skills/doca-telemetry-exporter/?utm_source=badge&utm_medium=readme&utm_campaign=skill_badge)
<script>
<script src="https://claudskills.com/embed/doca-telemetry-exporter.js" async></script>
<iframe>
<iframe src="https://claudskills.com/embed/doca-telemetry-exporter.html" width="100%" height="160" frameborder="0" loading="lazy" title="ClaudSkills: Doca Telemetry Exporter"></iframe>
Security scan
Grade A · scanned 2026-07-24 — free static scan against the OWASP Agentic Skills Top 10.
The scan flagged 1 of 10 categories (filesystem), including lower-severity patterns. Patterns shown inside code fences are weighted as examples rather than instructions — read the grading methodology for what this does and does not guarantee.
- ✓ Prompt injection
- ✓ Data exfiltration
- ✓ Supply chain
- ✓ Reverse shell
- ✓ Credentials
- ✓ Execution
- ⚠ Filesystem
- ✓ Persistence
- ✓ Obfuscation
- ✓ Network
Show this grade on your repo (click to copy):
[](https://claudskills.com/skills/doca-telemetry-exporter/#security)
More Engineering skills
Browse all Engineering skills in the ClaudSkills registry, or explore these other picks from the same category:
Part of Acreator Store — Adam Lankamer's AI tools:
PerfectStudio ·
Ucaption ·
UTagger ·
AutoXPoster ·
TestYourSkills ·
AutomationFlows ·
Au Naturel ·
Telegram @acreatorstore