otel-semantic-conventions

OpenTelemetry semantic convention lookup and naming guidance. Use when selecting released semantic convention groups, attributes, or span naming rules, or when checking semantic convention compliance.

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

100%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured skill body: concise, fully executable, with a clear five-step workflow and appropriate offloading to verified one-level references. It adds only what Claude would not already know about released semantic conventions.

Dimension	Reasoning	Score
Conciseness	Lean and action-oriented with no concept over-explanation; every line is guidance Claude would not already know, and the v1.42.0 note is routing fact rather than date-bound API switching.	3 / 3
Actionability	Provides concrete, copy-paste-ready commands (e.g. '--groups', 'http', 'http spans', 'http http.request.method'), env-var setup, and specific naming rules rather than abstract direction.	3 / 3
Workflow Clarity	A clearly sequenced five-step workflow with a verification checkpoint in step 5 (return exact source context, call out compatibility limitations); the lookup task is non-destructive so explicit validate-fix-retry loops are not required.	3 / 3
Progressive Disclosure	The body is an overview with well-signaled one-level-deep references to references/semconv-selection.md, references/otel-semantic-conventions.md, and the bundled query script; all referenced paths are real files with detail rather than nested pointers.	3 / 3
	Total	12 / 12 Passed

Description

100%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: third-person, concrete, with an explicit 'Use when' trigger and well-scoped domain language. It cleanly answers what and when with low conflict risk.

Dimension	Reasoning	Score
Specificity	Names multiple concrete actions — 'lookup and naming guidance', 'selecting released semantic convention groups, attributes, or span naming rules', and 'checking semantic convention compliance' — rather than vague language.	3 / 3
Completeness	Explicitly answers both what (lookup and naming guidance) and when via the 'Use when selecting...' trigger clause, matching the top anchor.	3 / 3
Trigger Term Quality	Includes natural OTel terms a user would actually say — 'semantic convention', 'attributes', 'span naming rules', 'semantic convention compliance' — rather than jargon-only phrasing.	3 / 3
Distinctiveness Conflict Risk	Targets a clear niche (OpenTelemetry semantic conventions) with distinct, domain-specific triggers unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: ollygarden/opentelemetry-agent-skills
Path: skills/otel-semantic-conventions/SKILL.md
Commit: c5d2edc

Reviewed: about 2 hours ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.