What problem does it solve? Planning OpenTelemetry instrumentation requires navigating a large, fast-moving documentation set across many languages, and relying on memory leads to wrong package names, outdated attribute names, and missed zero-code options. This Skill provides a curated, verified map of the official OpenTelemetry docs so instrumentation plans are grounded in the actual current documentation. ## Core Features & Use Cases - Per-language reference files: Covers C++, .NET, Erlang/Elixir, Go, Java, JavaScript, Kotlin, PHP, Python, Ruby, Rust, Swift, and community SDKs, each listing every official docs section with what it covers and how to use it. - Cross-language references: Dedicated guides for SDK configuration (OTEL_* environment variables), semantic conventions, generative AI (gen_ai.* spans, metrics, and per-SDK instrumentation libraries), the Collector, and profiling. - Verification rules: Enforces fetching official pages before recommending package names or APIs, with fallback strategies when registry pages render client-side. - Use Case: When instrumenting a Python service that calls OpenAI, open the Python reference for zero-code setup and the GenAI reference to pick the right instrumentation package and content-capture settings, then verify each claim against the linked official page. ## Quick Start Ask the agent to plan OpenTelemetry instrumentation for your service, naming its language and any LLM or agent frameworks it uses.