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

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

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.

The content is a tight, actionable lookup workflow with sound progressive disclosure and executable commands. It loses points for a version number embedded in the main flow and the absence of an explicit error-recovery loop.

Suggestions

Move the 'v1.42.0' GenAI-repository guidance into a clearly labeled 'Deprecated / old patterns' section so the main workflow stays free of time-sensitive version details.

Add a brief validate-fix-retry note for query failures (e.g., what to do when a group or attribute id returns nothing) to strengthen the workflow's error-recovery feedback loop.

Give one concrete example of a 'stable custom namespace' format so the no-released-key fallback is as actionable as the query commands.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence, but the time-sensitive version number 'v1.42.0' appears in the main workflow rather than in a deprecated/old-patterns section, which the rubric penalizes.	4 / 5
Actionability	Provides copy-paste-ready shell commands covering the common cases — listing groups, inspecting a group, a kind, and an exact attribute — plus a concrete local-checkout invocation.	5 / 5
Workflow Clarity	A clear five-step sequence is present with one validation checkpoint (run the test script after parser changes), but there is no explicit validate-fix-retry feedback loop for error recovery.	4 / 5
Progressive Disclosure	The body is a concise overview with well-signaled, one-level-deep references to real files (references/semconv-selection.md and references/otel-semantic-conventions.md) and bundled scripts, with detail appropriately split out.	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.

The description is well-crafted: third-person voice, explicit what-and-when, concrete actions, and a distinct trigger surface. Its only weakness is slightly narrow keyword coverage that misses a few natural synonyms.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — lookup, naming guidance, selecting released groups/attributes/span naming rules, and compliance checking — giving comprehensive coverage of the skill's purpose.	5 / 5
Completeness	Explicitly states what the skill does ('lookup and naming guidance') and when to use it ('Use when selecting released semantic convention groups, attributes, or span naming rules, or when checking semantic convention compliance') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural terms like 'semantic conventions', 'attributes', 'span naming rules', 'compliance', and 'OpenTelemetry', but omits common synonyms a user might say such as 'traces', 'metrics', or 'instrumentation'.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear OpenTelemetry semantic-conventions niche with distinct triggers, making overlap with unrelated skills minimal.	5 / 5
	Total	19 / 20 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: 8e6ed41

Reviewed: 16 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.