O11y Dev Opentelemetry Skill
o11y-dev-opentelemetry-skill is a Claude Code plugin for the Operate phase that structures AI-assisted OpenTelemetry and production observability engineering.
by o11y-dev · github.com/o11y-dev/opentelemetry-skill
Install when you want Claude Code to guide production-grade OpenTelemetry instrumentation, exporters, and observability rollouts instead of guessing collector configs.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install o11y-dev-opentelemetry-skill@o11y-dev/opentelemetry-skillBuilt to be called by your agent
Skillselion is itself an MCP server. Your agent can pull this entry and a paste-ready install config straight from the API - no copy-paste.
Retrieve this entry with skillselion.get_details("plugin:o11y-dev/opentelemetry-skill") and the paste-ready config with skillselion.get_install_config("plugin:o11y-dev/opentelemetry-skill").
What it does
o11y-dev-opentelemetry-skill is a Claude Code plugin that packages an AI-assisted cognitive architecture for OpenTelemetry and observability engineering. Solo builders and small teams shipping APIs, SaaS, or services use it when they need structured help choosing instrumentation patterns, wiring exporters and collectors, and aligning telemetry with production practices rather than one-off debug prints. The bundle emphasizes progressive disclosure, deployment-aware configurations, and expert framing so your agent can reason about traces, metrics, and logs as a system—not isolated libraries. It fits builders who are past prototype and need repeatable observability as they ship and operate. Install it when you are standardizing OTel across services, onboarding agents to your stack, or reducing mistakes in collector and SDK setup. It complements DevOps and monitoring work on the Skillselion journey without replacing your APM vendor or hosted observability product.
Highlights
- Cognitive architecture for AI-assisted observability engineering with progressive, production-oriented guidance
- Covers OpenTelemetry practices: instrumentation, semantic conventions, and deployment-minded configurations
- Expert-style assistant framing for architectures, disclosure, and engineering tradeoffs
- Community plugin bundle with 1 packaged skill focused on OTel—not a generic logging snippet pack
- Keyword coverage spans deployment, configurations, and production-ready observability workflows
Why builders use it
You know you need traces and metrics in production, but OTel SDKs, collectors, and semantic conventions feel overwhelming and easy to misconfigure.
After install, Claude Code can walk you through observability architectures and production-ready OpenTelemetry configurations with clearer engineering guardrails.
At a glance
- Type - Plugin in DevOps.
- Adoption - 0 installs, 16 stars, 0 votes.
FAQ
Who is o11y-dev-opentelemetry-skill for?
Solo and small-team builders using Claude Code who need structured OpenTelemetry and observability guidance for real deployments.
When should I use o11y-dev-opentelemetry-skill?
Use it when you are designing or fixing instrumentation, collector configs, or production telemetry practices—not for generic coding without an observability goal.
How do I add o11y-dev-opentelemetry-skill to my agent?
Register the plugin from the o11y-dev/opentelemetry-skill repository in Claude Code’s plugin flow, then invoke its packaged skill during observability tasks.
Comments
Share how you use o11y-dev-opentelemetry-skill, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.