CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

86%Weight 40%Scale 1-5

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

A well-structured, highly actionable skill body: executable lookup commands, a clear five-step workflow, and clean one-level-deep reference navigation verified against the actual bundle. Minor gaps are inline time-sensitive version/date details and a validation step scoped to parser maintenance rather than the main workflow.

DimensionReasoningScore

Conciseness

The body is lean and imperative with no concept explanations ('do not load the full semantic convention spec into context', 'use required and recommended attributes before optional ones'). It misses a 5 because time-sensitive details — 'no tagged release as of 2026-10-25' and 'after v1.42.0' — sit inline rather than in a deprecated/old-patterns section, which the guidelines penalize.

4 / 5

Actionability

The guidance is fully executable: four copy-paste-ready script invocations ('./scripts/query-otel-semantic-conventions.sh --groups', '... http', '... http spans', '... http http.request.method'), an env-var setup for local verification, and a concrete test command. Commands cover the common lookup cases.

5 / 5

Workflow Clarity

A clear five-step sequence runs from choosing released guidance to returning results 'with exact source context' (group name, released version, source URL), and step 5's source-context requirement acts as a verification checkpoint. It misses 5 because the only explicit validation step (running the test script) is scoped narrowly to parser changes rather than the lookup workflow itself.

4 / 5

Progressive Disclosure

The body is a concise overview that clearly signals three one-level-deep references ('see references/semconv-selection.md', 'references/sdk-semconv-packages.md', 'references/otel-semantic-conventions.md') — all of which exist in the bundle and point no further than the bundled scripts, so navigation is flat and easy.

5 / 5

Total

18

/

20

Passed

Description

92%Weight 40%Scale 1-5

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 with a clear capability statement, an explicit 'Use when...' trigger clause covering three concrete scenarios, and a distinct niche. The only weakness is modest synonym coverage (e.g., 'OTel', 'traces') in the trigger terms.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — 'selecting released semantic convention groups, attributes, or span naming rules', 'checking semantic convention compliance', and 'checking which semantic-conventions version a language SDK's semconv package exposes' — comprehensively covering the skill's capabilities. It exceeds the score-4 anchor because the action list has no notable coverage gaps.

5 / 5

Completeness

It explicitly answers both questions: the what ('OpenTelemetry semantic convention lookup and naming guidance') and an explicit 'Use when...' clause with three concrete trigger scenarios. This matches the score-5 anchor with concrete trigger phrases.

5 / 5

Trigger Term Quality

Strong natural terms are present ('semantic conventions', 'span naming rules', 'attributes', 'compliance', 'semconv package', 'SDK'), matching the good-coverage anchor. It falls short of 5 because common variations users might say — 'OTel', 'traces', 'telemetry' — are absent.

4 / 5

Distinctiveness Conflict Risk

The description occupies a clear niche — released OTel semantic convention lookup and compliance — with triggers ('semconv package', 'span naming rules') unlikely to fire for unrelated skills. Conflict risk is minimal.

5 / 5

Total

19

/

20

Passed

Validation

100%

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

Reviewed

Table of Contents

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.