Opentelemetry Skill
Design OpenTelemetry collectors, pipelines, sampling, and instrumentation—including observability for AI coding agents in production.
Overview
OpenTelemetry skill is an agent skill most often used in Operate (also Build integrations, Ship perf) that configures collectors, pipelines, instrumentation, and AI agent observability.
Install
npx skills add https://github.com/o11y-dev/opentelemetry-skill --skill SKILL.mdWhat is this skill?
- Collector configuration and end-to-end pipeline design
- Application instrumentation, sampling, and cardinality management
- OTTL transformations and securing telemetry export paths
- Production guidance for logs, metrics, and traces at scale
- AI coding agent observability for Claude Code, Codex, Gemini CLI, and Copilot
Adoption & trust: 28 GitHub stars.
What problem does it solve?
You lack a coherent OpenTelemetry setup and cannot trust traces, metrics, or logs—or agent runs—in production.
Who is it for?
Indie SaaS and agent builders instrumenting services and coding-agent workflows with vendor-neutral OpenTelemetry.
Skip if: Teams that only need a hosted APM one-liner with zero collector ownership, or pure product copy with no runtime telemetry.
When should I use this skill?
Configuring collectors, designing pipelines, instrumenting applications, sampling, managing cardinality, securing telemetry, writing OTTL, or setting up AI coding agent observability.
What do I get? / Deliverables
You get collector and instrumentation designs with sampling, security, and OTTL patterns that produce actionable production telemetry.
- Collector and pipeline configuration outline
- Instrumentation and sampling recommendations
- OTTL or security hardening notes for export paths
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Production telemetry is owned in Operate, but the same skill applies while instrumenting apps during Build and hardening telemetry before Ship. Monitoring is the canonical shelf for collectors, cardinality control, and ongoing trace/log/metric operations.
Where it fits
Add OTLP exporters and manual spans to a new API before anyone hits production traffic.
Tune sampling and drop high-cardinality labels so launch-day metrics stay readable.
Redesign a failing collector pipeline and OTTL filters after an incident.
Correlate product funnel events with trace IDs for solo-founder growth debugging.
How it compares
Deep OpenTelemetry operations skill—not a thin wrapper around a single SaaS APM signup.
Common Questions / FAQ
Who is opentelemetry-skill for?
Solo and indie builders configuring collectors, pipelines, and instrumentation who also may observe AI coding agents in dev or prod.
When should I use opentelemetry-skill?
Use in Operate monitoring for live pipelines; in Build integrations when adding SDK instrumentation; in Ship perf when tuning sampling before launch; when securing exports or writing OTTL.
Is opentelemetry-skill safe to install?
Review the Security Audits panel on this page—telemetry skills often imply network access and handling of potentially sensitive trace and log data.
SKILL.md
READMESKILL.md - Opentelemetry Skill
Expert OpenTelemetry guidance for collector configuration, pipeline design, and production telemetry instrumentation. Use when configuring collectors, designing pipelines, instrumenting applications, implementing sampling, managing cardinality, securing telemetry, writing OTTL transformations, or setting up AI coding agent observability (Claude Code, Codex, Gemini CLI, GitHub Copilot). # opentelemetry-skill { "name": "opentelemetry-skill", "description": "Expert OpenTelemetry guidance for collector configuration, pipeline design, and production telemetry instrumentation. Use when configuring collectors, designing pipelines, instrumenting applications, implementing sampling, managing cardinality, securing telemetry, writing OTTL transformations, or setting up AI coding agent observability (Claude Code, Codex, Gemini CLI, GitHub Copilot)." }