How do I install the Opentelemetry skill?

Run npx skillmds@latest add ashish7802/opentelemetry in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Opentelemetry skill do?

OpenTelemetry Skill It is listed under Coding & Dev Tools on SkillMD.

Is Opentelemetry safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Opentelemetry?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Opentelemetry free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Opentelemetry?

ashish7802 (@ashish7802) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Opentelemetry by ashish7802 — Agent Skill

Name: Opentelemetry
Author: ashish7802

File contents

OpenTelemetry Skill

High-quality, ubiquitous, and portable telemetry to enable effective observability.

Ecosystem Graph

graph LR
  opentelemetry["OpenTelemetry"]
  opentelemetry -- "publishes to" --> jaeger
  opentelemetry -- "publishes to" --> prometheus

Quick Start

OpenTelemetry (OTel) provides a vendor-neutral standard for instrumenting code. You instrument once, and route telemetry data to Datadog, Jaeger, or Honeycomb interchangeably via the OTel Collector.

npm install @opentelemetry/api @opentelemetry/sdk-node

Production Patterns

The Collector Architecture

Never send telemetry directly from your application to a backend vendor (e.g., sending traces directly to Honeycomb). Always send data to a local OpenTelemetry Collector (running as a sidecar or daemonset), which batches, compresses, and forwards the data securely.

Architecture & Scaling

Context Propagation

For distributed tracing to work, the unique trace_id must be passed between microservices. OTel achieves this automatically by injecting W3C Trace Context headers into outgoing HTTP/gRPC requests.

Error Recovery

Telemetry SDKs are designed to fail silently. If the Collector goes down, the application will drop traces rather than crashing. Ensure you have infrastructure-level alerts tracking Collector health.

Security Notes

Be extremely careful not to trace raw SQL queries containing PII, or log full HTTP request bodies containing passwords. Utilize OTel Collector processors to redact sensitive fields before data leaves your network.

Relationships

References

OpenTelemetry Docs

Why use this skill

Use this when your agent works with opentelemetry — structured patterns beat pasted docs and prevent common hallucinations.

AI pitfalls

Using outdated SDK or API versions from training data
Inventing environment variable names
Omitting error handling and retry logic

Production checklist

Secrets in environment variables, not source code
Error handling and logging in place
Rate limits and timeouts configured

Related skills

jaeger — publishes to
prometheus — publishes to

Last Verified: 2026-07-02

---name: opentelemetrydescription: OpenTelemetry Skill---# OpenTelemetry Skill> High-quality, ubiquitous, and portable telemetry to enable effective observability.## Ecosystem Graph```mermaidgraph LR opentelemetry["OpenTelemetry"] opentelemetry -- "publishes to" --> jaeger opentelemetry -- "publishes to" --> prometheus```## Quick StartOpenTelemetry (OTel) provides a vendor-neutral standard for instrumenting code. You instrument once, and route telemetry data to Datadog, Jaeger, or Honeycomb interchangeably via the OTel Collector.```bashnpm install @opentelemetry/api @opentelemetry/sdk-node```## Production Patterns### The Collector ArchitectureNever send telemetry directly from your application to a backend vendor (e.g., sending traces directly to Honeycomb). Always send data to a local OpenTelemetry Collector (running as a sidecar or daemonset), which batches, compresses, and forwards the data securely.## Architecture & Scaling### Context PropagationFor distributed tracing to work, the unique `trace_id` must be passed between microservices. OTel achieves this automatically by injecting W3C Trace Context headers into outgoing HTTP/gRPC requests.## Error RecoveryTelemetry SDKs are designed to fail silently. If the Collector goes down, the application will drop traces rather than crashing. Ensure you have infrastructure-level alerts tracking Collector health.## Security NotesBe extremely careful not to trace raw SQL queries containing PII, or log full HTTP request bodies containing passwords. Utilize OTel Collector processors to redact sensitive fields before data leaves your network.## Relationships## References- [OpenTelemetry Docs](https://opentelemetry.io/docs/)## Why use this skillUse this when your agent works with **opentelemetry** — structured patterns beat pasted docs and prevent common hallucinations.## AI pitfalls- Using outdated SDK or API versions from training data- Inventing environment variable names- Omitting error handling and retry logic## Production checklist- [ ] Secrets in environment variables, not source code- [ ] Error handling and logging in place- [ ] Rate limits and timeouts configured## Related skills- [`jaeger`](../jaeger/SKILL.md) — publishes to- [`prometheus`](../prometheus/SKILL.md) — publishes to---> **Last Verified:** 2026-07-02

Frequently asked questions