ollygardenollygarden/opentelemetry-agent-skills/skills/otel-sdk-versions/SKILL.md

otel-sdk-versions

Skill125 starsChanged 4 months agoApache-2.0View on GitHub

OpenTelemetry release version lookup for SDKs across languages and for the Collector (core, contrib, distributions, builder/OCB), the declarative configuration schema, semantic conventions, and Weaver. Use when choosing the latest compatible released OpenTelemetry SDK, package, or component version, when asked what the latest release of one of these is, and when locating setup docs or examples. Not for Collector build manifests or upgrade-risk assessment.

In this repository19 other files it gives its agents.
- AGENTS.mdAGENTS.md
- otel-browserSkill
- otel-collector-builderSkill
- otel-collectorSkill
- otel-declarative-configSkill
- otel-dotnetSkill
- otel-goSkill
- otel-javaSkill
- otel-jsSkill
- otel-ottlSkill
- otel-profilesSkill
- otel-pythonSkill
- otel-rubySkill
- otel-semantic-conventionsSkill
- otel-span-events-to-logs-migrationSkill
- otel-telemetry-emissionsSkill
- otel-telemetrygenSkill
- otel-upgradeSkill
- otel-weaverSkill

The file

We split this skill into the rules it gives an agent

10 rules. About 0 are common, 10 are distinctive, and 0 are very specific to this project.

≈0
Common · estimate
Many files like this have a rule of this kind.
≈10
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Distinctive:
use the bundled tables as the default source of truth for what they cover
line 12
Distinctive:
prefer the latest released version when it is compatible with the project
line 17
Distinctive:
if the latest release is not compatible, choose the latest compatible version and state the compatibility reason explicitly
line 18
Distinctive:
if the task requires additional packages from the same ecosystem (exporters, instrumentations, resource detectors, Collector components), …
line 22
Distinctive:
Use the linked follow-up sources when needed.
line 26
Distinctive:
use the Release Source or Release column to confirm the package, repo, or release notes
line 27
Distinctive:
use the Setup Docs column for SDK setup guidance
line 28
Distinctive:
use the Examples column for implementation references when examples are available
line 29
Distinctive:
if the requested language, package, or component is not in the bundled index, say that the index does not cover it
line 32
Distinctive:
do not assume an unreleased, prerelease, or incompatible version is acceptable without saying so
line 34

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.

Files

SKILL.md

OpenTelemetry SDK Versions

Workflow

Open references/generated/otel-version-index.md.

the SDKs table has one primary SDK package per language; the Components table covers the Collector (core, contrib, distributions, builder), the configuration schema, semantic conventions, and Weaver
use the bundled tables as the default source of truth for what they cover
its "Versions last changed" date is the last day any row changed
offline, give each version with that date: "<version> as of <date>; a newer release may exist". Never call it the current latest

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

Resolve companion packages from the release source.

if the task requires additional packages from the same ecosystem (exporters, instrumentations, resource detectors, Collector components), 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
Collector components in one build must match the core release line its builder uses, which can trail core; see otel-collector-builder for manifest pinning

Use the linked follow-up sources when needed.

use the Release Source or Release column to confirm the package, repo, or release notes
use the Setup Docs column for SDK setup guidance
use the Examples column for implementation references when examples are available

Handle gaps explicitly.

if the requested language, package, or component is not in the bundled index, say that the index does not cover it
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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

It worked
Partly
It didn't

What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free