otel-semantic-conventions

OpenTelemetry Semantic Conventions expert. Use when selecting, applying, or reviewing telemetry attributes. Triggers on tasks involving attribute selection, semantic convention compliance, attribute migration, or custom attribute decisions. Covers the attribute registry, naming patterns, attribute placement, and versioning. For span names, span kinds, and span status codes, see the otel-instrumentation skill.

1.22x

Quality

100%

Does it follow best practices?

Impact

98%

1.22x

Average score across 3 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Quality

Content

100%

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

This is a well-crafted skill that efficiently covers attribute selection, placement, and validation with concrete code examples and a clear decision workflow. The progressive disclosure via the rules table is exemplary, and the content respects Claude's intelligence by avoiding unnecessary explanations of basic concepts. The correct/incorrect example pairs are particularly effective for teaching the nuances of attribute usage.

Dimension	Reasoning	Score
Conciseness	The content is lean and efficient. It doesn't explain what OpenTelemetry is or what semantic conventions are conceptually — it jumps straight to actionable rules and selection guidance. Every section earns its place, and the table format for rules is compact.	3 / 3
Actionability	Provides concrete, executable code examples for correct vs incorrect attribute selection, resource vs span placement, and cardinality violations. The 5-step selection process is specific and prescriptive with clear do/don't patterns.	3 / 3
Workflow Clarity	The 'How to select the right attribute' section provides a clear 5-step sequential workflow for attribute selection decisions. Each step has a clear action and rationale. For this type of skill (decision-making guidance rather than destructive operations), validation checkpoints are appropriately represented by steps like 'Check stability' and 'Verify cardinality'.	3 / 3
Progressive Disclosure	Excellent structure: concise overview with a clear rules table pointing to one-level-deep rule files (attributes.md, versioning.md, dash0.md), plus well-organized external documentation links. The SKILL.md serves as a navigable hub without inlining excessive detail.	3 / 3
	Total	12 / 12 Passed

Description

100%

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

This is an excellent skill description that clearly defines its scope around OpenTelemetry semantic conventions, provides explicit trigger conditions, and thoughtfully delineates boundaries with a related skill. It uses third person voice consistently, includes domain-specific trigger terms that practitioners would naturally use, and covers both 'what' and 'when' comprehensively.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: selecting, applying, reviewing telemetry attributes, attribute migration, custom attribute decisions, attribute registry, naming patterns, attribute placement, and versioning.	3 / 3
Completeness	Clearly answers both what (selecting, applying, reviewing telemetry attributes, attribute registry, naming patterns, placement, versioning) and when ('Use when selecting, applying, or reviewing telemetry attributes. Triggers on tasks involving attribute selection, semantic convention compliance, attribute migration, or custom attribute decisions').	3 / 3
Trigger Term Quality	Includes natural keywords users would say: 'telemetry attributes', 'semantic conventions', 'attribute selection', 'attribute migration', 'naming patterns', 'attribute registry', 'versioning'. These are terms practitioners naturally use when working with OpenTelemetry semantic conventions.	3 / 3
Distinctiveness Conflict Risk	Clearly carves out a distinct niche focused on OpenTelemetry semantic conventions and attributes, and explicitly delineates boundaries by directing span names, span kinds, and span status codes to the otel-instrumentation skill, reducing conflict risk.	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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: dash0hq/agent-skills
Commit: cb7cf0d

Reviewed: about 1 month 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.