Help us improve
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
By ollygarden
Author, debug, and validate OpenTelemetry Collector component YAML configs with SDK setup guidance across Go, Java, and Node.js, plus OTTL writing, version lookups, semantic convention queries, span-to-log migration, synthetic telemetry generation, and Weaver registry authoring with codegen.
npx claudepluginhub ollygarden/opentelemetry-agent-skills --plugin otel-javaOpenTelemetry Collector component configuration. Use when authoring, reviewing, or debugging Collector YAML for a specific receiver, processor, exporter, connector, or extension — config keys, defaults, validation rules, signal support, stability levels, and component-level gotchas. Triggers on questions about specific components such as `log_dedup` / `logdedup`, `interval` (metric aggregation), and other Collector components covered in `components/`.
OpenTelemetry declarative YAML configuration for SDK setup. Use when configuring OpenTelemetry SDK providers (tracer, meter, logger), setting up OTLP exporters, defining sampling strategies, or writing otel config files. Triggers on "otel config", "OpenTelemetry YAML", "declarative configuration", "otelconf", "OTEL_CONFIG_FILE", "file_format", "configure tracing/metrics/logs export", or when the user is setting up telemetry pipelines via config files rather than code.
OpenTelemetry in Go — SDK setup, API surface, breaking changes, contrib instrumentation libraries (otelhttp, otelgrpc, otelmongo), and performance tuning. Use when adding, reviewing, or configuring OpenTelemetry in a Go service. Triggers on "setup otel in go", "go telemetry", "go tracing", "otelconf go", "otelhttp", "otelgrpc", "TracerProvider go", "MeterProvider go", or any Go-related OTel question.
OpenTelemetry in Java — Javaagent zero-code instrumentation, Spring Boot Starter, manual autoconfigure SDK, declarative YAML configuration, BOM dependency management. Use when adding, reviewing, or configuring OpenTelemetry in a Java service. Triggers on "setup otel in java", "java telemetry", "javaagent", "Spring Boot otel", "GlobalOpenTelemetry", "AutoConfiguredOpenTelemetrySdk", "TracerProvider java", or any Java-related OTel question.
OpenTelemetry in Node.js / JavaScript / TypeScript — NodeSDK, declarative YAML configuration, auto-instrumentations, ESM vs CJS import patterns. Use when adding, reviewing, or configuring OpenTelemetry in a Node.js service. Triggers on "setup otel in node", "js telemetry", "node tracing setup", "NodeSDK", "auto instrumentation node", "TracerProvider node", or any Node.js-related OTel question.
Share bugs, ideas, or general feedback.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
OpenTelemetry skills and reference documentation for AI coding assistants
Set up distributed tracing for microservices
Skills, agents, and workflows for Honeycomb observability — query patterns, production investigations, SLOs, OpenTelemetry instrumentation, and Beeline migration. Designed to complement the Honeycomb MCP server.
Editorial "Observability & Monitoring" bundle for Claude Code from Antigravity Awesome Skills.
OpenTelemetry instrumentation patterns, semantic conventions, and testing
Observability engineering agents providing expertise in tracing, monitoring, and logging
Public OllyGarden AI skills for Rose and the broader ecosystem
This repository contains reusable agent skills for OpenTelemetry.
The skills are non-opinionated by design — there are many valid ways to use OpenTelemetry, and prescribing conventions is out of scope.
They are designed for token-efficient, agent-friendly retrieval: small fetch tables, lookup indexes, and scripts that point at upstream sources of truth instead of copying docs into context. The agent finds what it missed during training; answers stay current as the project evolves.
Install all skills:
npx skills add https://github.com/ollygarden/opentelemetry-agent-skills
Or install a single skill by pointing at its folder, e.g.:
npx skills add https://github.com/ollygarden/opentelemetry-agent-skills/tree/main/skills/otel-go
Register the repository as a plugin marketplace:
/plugin marketplace add ollygarden/opentelemetry-agent-skills
Install a skill:
/plugin install <skill-name>@opentelemetry-agent-skills
For example:
/plugin install otel-go@opentelemetry-agent-skills
Each skill is a self-contained folder under skills/, named to match its name: field per
the agentskills.io specification. Language-specific
skills bundle task-focused references; language-agnostic skills sit alongside them.
skills/
otel-go/
SKILL.md # name: otel-go
references/ # declarative-setup, api, instrumentation-libraries, performance, breaking-changes
otel-java/
SKILL.md
references/
otel-js/
SKILL.md
references/
otel-collector/
SKILL.md
components/ # one file per Collector component (log_dedup, interval, …)
otel-declarative-config/
otel-ottl/
otel-sdk-versions/
otel-semantic-conventions/
otel-span-events-to-logs-migration/
otel-telemetrygen/
otel-weaver/
Language-agnostic skills:
| Skill | Path | Use When |
|---|---|---|
otel-collector | skills/otel-collector/ | Configuring OpenTelemetry Collector components — config keys, defaults, validation, signal support, stability, and gotchas. Progressive disclosure via components/<type>.md; currently covers log_dedup and interval processors. |
otel-declarative-config | skills/otel-declarative-config/ | Configuring OpenTelemetry SDK providers via a single YAML file (otelconf, OTEL_CONFIG_FILE, file_format). Points at the upstream schema, env-var substitution rules, and configuration precedence. |
otel-ottl | skills/otel-ottl/ | Authoring or reviewing OTTL statements for transform, filter, routing, and tail_sampling processors; debugging OTTL syntax and semantics; transforming traces, metrics, logs, and profiles in the Collector. |
otel-sdk-versions | skills/otel-sdk-versions/ | Choosing the latest compatible released OpenTelemetry SDK or package version for a language and finding setup docs or examples. |
otel-semantic-conventions | skills/otel-semantic-conventions/ | Selecting released semantic convention groups, attributes, and span naming rules; checking compliance; looking up exact upstream entries via the bundled query script. |
otel-span-events-to-logs-migration | skills/otel-span-events-to-logs-migration/ | Migrating instrumentation from the deprecated Span Event API (AddEvent, RecordException) to the Logs API following the OTEP 4430 deprecation plan. |
otel-telemetrygen | skills/otel-telemetrygen/ | Constructing telemetrygen commands for generating synthetic traces, metrics, and logs; load-testing collectors; validating OTTL transforms, tail sampling, and filter rules. |
otel-weaver | skills/otel-weaver/ | Authoring an OpenTelemetry Weaver registry, writing Jinja2 templates, generating language bindings, and wiring weaver registry check/generate/diff into CI. |
Language-specific skills:
| Skill | Path | Use When |
|---|---|---|
otel-go | skills/otel-go/ | OpenTelemetry in Go: declarative SDK setup with otelconf, API surface, contrib instrumentation libraries (otelhttp, otelgrpc, etc.), performance tuning, and breaking-change audits. |
otel-java | skills/otel-java/ | OpenTelemetry in Java: Javaagent zero-code instrumentation, Spring Boot Starter, manual autoconfigure SDK, declarative YAML configuration, and BOM dependency management. |
otel-js | skills/otel-js/ | OpenTelemetry in Node.js / JavaScript / TypeScript: NodeSDK setup, declarative YAML configuration via @opentelemetry/configuration, auto-instrumentations, and ESM vs CJS import patterns. |
Contributions are welcome. When adding or updating skills, please follow these guidelines: