Otel Sdk Versions logo

Otel Sdk Versions

Organization
ollygarden
otel-sdk-versions

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.

Overview

Publisherollygarden
Repositoryopentelemetry-agent-skills
Skill nameotel-sdk-versions
Stars
119
Forks
13
Bundled files
1
LicenseApache-2.0
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 1 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by ollygarden on GitHub. Read the source before you install it.

Installation

Install the Otel Sdk Versions AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/ollygarden/opentelemetry-agent-skills/tree/main/skills/otel-sdk-versions
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/ollygarden/opentelemetry-agent-skills.git /tmp/opentelemetry-agent-skills
mkdir -p .claude/skills
cp -r /tmp/opentelemetry-agent-skills/skills/otel-sdk-versions .claude/skills/otel-sdk-versions
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Otel Sdk Versions in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Otel Sdk Versions on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Otel Sdk Versions is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

OpenTelemetry SDK Versions

Workflow

  1. 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
  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.
  • 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
  1. 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
  1. 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

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Otel Sdk Versions AI skill do?

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.

Why use Otel Sdk Versions on TypingMind?

Because you install it once and use it with any model. Otel Sdk Versions is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Otel Sdk Versions in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/ollygarden/opentelemetry-agent-skills/tree/main/skills/otel-sdk-versions. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Otel Sdk Versions?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Otel Sdk Versions?

As many as you like. As long as a model supports skills, you can use Otel Sdk Versions with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Otel Sdk Versions AI skill free?

Yes. It is published on GitHub by ollygarden under the Apache-2.0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇