Otel Semantic Conventions

Handles OpenTelemetry attribute selection and placement so you don't end up with custom attributes that should have been in the registry or metric attributes that explode cardinality. Walks you through the attribute registry lookup, stability checks, and the resource versus span placement decision. The examples are practical: shows you why http.request.method beats custom.http.verb, why service.name belongs on resources not spans, and why user IDs will wreck your metrics if you're not careful. Built by dash0, so it includes their derived attributes and feature dependencies alongside the standard conventions. Good for code reviews and migration work when you're moving between semconv versions.

skills.sh installs: 727
GitHub stars: 99
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add dash0hq/agent-skills --skill otel-semantic-conventions --agent claude-code

Installs into .claude/skills of the current project.

Files

OpenTelemetry Semantic Conventions

This skill governs correct selection, placement, and validation of telemetry attributes and metric instruments according to the OpenTelemetry Semantic Conventions specification. For span naming, span kinds, and span status codes, see the otel-instrumentation skill.

The Attribute Registry is the single source of truth for all defined attributes.