Otel Semantic Conventions

Organization

ollygarden

otel-semantic-conventions

OpenTelemetry semantic convention lookup and naming guidance. Use when selecting released semantic convention groups, attributes, or span naming rules, when checking semantic convention compliance, or checking which semantic-conventions version a language SDK's semconv package exposes.

Overview

Publisher	ollygarden
Repository	`opentelemetry-agent-skills`
Skill name	`otel-semantic-conventions`
Stars	119
Forks	13
Bundled files	6
License	Apache-2.0
Links	Skill source Repository Homepage

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.
6 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 Semantic Conventions AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

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.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/ollygarden/opentelemetry-agent-skills/tree/main/skills/otel-semantic-conventions
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/ollygarden/opentelemetry-agent-skills/tree/main/skills/otel-semantic-conventions

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

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-semantic-conventions .claude/skills/otel-semantic-conventions

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Otel Semantic Conventions 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 Semantic Conventions 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 Semantic Conventions 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 Semantic Conventions

Use this skill when you need released semantic convention guidance for naming, attributes, or compliance checks.

Workflow

Start with released semantic conventions, not model memory.

do not load the full semantic convention spec into context
use the bundled lookup script to query only the needed released group or attribute
for local verification against a checked-out upstream repo, set OTEL_SEMCONV_REPO=/path/to/semantic-conventions

Choose the closest released group before inventing custom keys.

identify the boundary type such as http, db, messaging, rpc, or network
pick one primary group first, then add related groups only when they add needed context
for gen_ai.*, OpenAI, or MCP conventions, use open-telemetry/semantic-conventions-genai; it has no tagged release as of 2026-10-25, so cite the commit and label the guidance unreleased (the lookup script does not cover it); the core repository keeps only deprecated GenAI-era stubs after v1.42.0
see references/semconv-selection.md
to target a version a language's semconv package actually exposes (works offline, dated), see references/sdk-semconv-packages.md

Query only the released guidance you need.

list groups: ./scripts/query-otel-semantic-conventions.sh --groups
inspect one group: ./scripts/query-otel-semantic-conventions.sh http
inspect one kind: ./scripts/query-otel-semantic-conventions.sh http spans
inspect one exact attribute or entry: ./scripts/query-otel-semantic-conventions.sh http http.request.method
see references/otel-semantic-conventions.md
after changing the parser, run OTEL_SEMCONV_REPO=/path/to/semantic-conventions bash ./scripts/test-query-otel-semantic-conventions.sh

Apply the released naming and attribute rules directly.

use required and recommended attributes before optional ones
derive semconv-governed span names directly from the released naming rule
do not prepend or append protocol labels, hostnames, product names, business hints, or other custom prose to semconv-governed span names
if the released naming rule does not provide a low-cardinality target, use the simpler fallback allowed by that convention
if no released key exists, use a stable custom namespace and keep values bounded

Return the result with exact source context.

include the group name, released version, and source URL from the script output
call out any concrete compatibility limitation if the implementation cannot fully match the released guidance

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 Semantic Conventions AI skill do?

Why use Otel Semantic Conventions on TypingMind?

Because you install it once and use it with any model. Otel Semantic Conventions 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 Semantic Conventions in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/ollygarden/opentelemetry-agent-skills/tree/main/skills/otel-semantic-conventions. 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 Semantic Conventions?

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 Semantic Conventions?

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

Is the Otel Semantic Conventions 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

Release Openclaw Mac

openclaw

OrganizationPopular

Run or recover OpenClaw macOS release signing, notarization, appcast, and asset promotion.

Release Openclaw Maintainer

openclaw

OrganizationPopular

Prepare, publish, recover, or verify OpenClaw beta, stable, and extended-stable releases, including approved backports.

Release Openclaw Plugin Testing

openclaw

OrganizationPopular

Plan and run pre-release OpenClaw plugin validation across bundled plugins, package artifacts, lifecycle commands, doctor/fix, config round-trip, gateway startup, SDK compatibility, Docker E2E,…

Solid

Write, port, review, or test Solid 2 UI in OpenClaw (Control UI, plugin views, Canvas hosts), including state ownership, Lit interop during the migration, native overlays, testing, performance, and…

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

OpenTelemetry Semantic Conventions

Workflow

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now