ollygarden/opentelemetry-agent-skills

otel-sdk-versions

OpenTelemetry SDK and package version lookup across languages. Use when choosing the latest compatible released OpenTelemetry SDK or package version and locating setup docs or examples.

First seen Apr 30, 2026

Installation

$ npx skills add ollygarden/opentelemetry-agent-skills --skill otel-sdk-versions

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from ollygarden/opentelemetry-agent-skills · top by installs.

npx skills add ollygarden/opentelemetry-agent-skills

Browse all from ollygarden/opentelemetry-agent-skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 97
License LICENSE
Default branch main
Open issues 4
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,950 B
  • docs SUMMARY.md 210 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 86 installs

SKILL.md

OpenTelemetry SDK Versions

Use this skill when you need the latest released OpenTelemetry SDK or package version for a language.

Workflow

  1. Open references/generated/otel-version-index.md.
  • identify the row for the project language and package
  • use the bundled table as the default source of truth for supported languages in this repository
  1. Choose the version deliberately.
  • prefer the latest released version when it is compatible with the project
  • if the latest release is not compatible, choose the latest compatible version and state the compatibility reason explicitly
  • reuse that decision for the rest of the task unless the language, package, or constraints change
  1. Resolve companion packages from the release source.
  • the index covers one primary SDK package per language
  • if the task requires additional packages from the same ecosystem (exporters, instrumentations, resource detectors), look up their versions from the release source — do not infer or reuse the primary package version
  • sub-packages within the same project often share a version line but not always; confirm each package individually
  1. Use the linked follow-up sources when needed.
  • use the Release Source column to confirm the package or repo
  • use the Setup Docs column for SDK setup guidance
  • use the Examples column for implementation references when examples are available
  1. Handle gaps explicitly.
  • if the requested language or package is not in the bundled index, say that the index does not cover that exact package
  • then fall back to the official release source and official docs for that package
  • do not assume an unreleased, prerelease, or incompatible version is acceptable without saying so