otel-telemetry-emissions

Version-pinned inventory of the telemetry (spans, metrics, logs, attributes) emitted by OpenTelemetry collector components and SDK instrumentation packages. Use when working with a covered component — what it emits at a given version, or how emission changed across versions — and when upgrading a component or SDK version, to see the telemetry after the change.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Failed to scan

The risk profile of this skill

Quality

Content

82%Scale 1-5

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 reference-lookup skill that is concise, clearly structured, and provides specific guidance for navigating version-pinned telemetry data. Its main strength is the lean, no-nonsense writing that respects Claude's intelligence while providing precise lookup rules with edge-case handling. The only notable weakness is the absence of a concrete worked example showing a full lookup scenario from question to answer.

Suggestions

Add a brief worked example showing a complete lookup scenario (e.g., 'User asks about kafkareceiver v0.157.0 → no exact match → use v0.156.0 file → state version is unverified').

Dimension	Reasoning	Score
Conciseness	Every section earns its place. The content is lean, assumes Claude's competence with OpenTelemetry concepts, and avoids explaining what collectors, spans, or metrics are. The caveat about LLM-generated data is necessary context, not padding.	5 / 5
Actionability	The lookup procedure (steps 1-4) is concrete and specific, with clear fallback behavior for missing versions. However, there's no executable code or commands — it's purely navigational guidance. For a reference-lookup skill this is appropriate, but the guidance could be slightly more concrete (e.g., showing an example lookup scenario with expected output).	4 / 5
Workflow Clarity	The 4-step lookup process is clearly sequenced with explicit handling for edge cases (no exact match, component not covered). The instruction to not infer telemetry is a good safety boundary. Minor gap: no validation step for confirming the looked-up data is correct beyond the general caveat note.	4 / 5
Progressive Disclosure	The skill clearly describes the layout convention and references index.md as the entry point. It explains what data files contain without inlining the actual data. Without bundle files to verify, the structure described is well-organized with one-level-deep references. Minor gap: no explicit links to example files or index.md.	4 / 5
	Total	17 / 20 Passed

Description

87%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.

This is a strong description that clearly defines a narrow, well-scoped domain (OpenTelemetry telemetry inventory) with explicit 'what' and 'when' clauses. The trigger terms are domain-appropriate and the use cases are concrete. Minor improvements could include adding common abbreviations (OTel) and more natural user phrasings.

Dimension	Reasoning	Score
Specificity	The description names the domain (OpenTelemetry collector components and SDK instrumentation packages) and lists several concrete concepts: spans, metrics, logs, attributes, version-pinned inventory, emission changes across versions, and upgrade scenarios. It could be more specific about exact actions (e.g., 'query', 'compare', 'diff') but covers the capability space well.	4 / 5
Completeness	Clearly answers both 'what' (version-pinned inventory of telemetry emitted by OTel components and SDK packages) and 'when' (when working with a covered component to understand emissions at a version, how emissions changed across versions, or when upgrading). The 'Use when' clause is explicit and provides concrete trigger scenarios.	5 / 5
Trigger Term Quality	Includes strong domain-specific trigger terms like 'OpenTelemetry', 'collector components', 'SDK instrumentation', 'spans', 'metrics', 'logs', 'attributes', 'upgrading', and 'version'. Missing some natural user phrases like 'otel', 'OTel', 'tracing', 'observability', or 'what metrics does X emit'.	4 / 5
Distinctiveness Conflict Risk	Highly distinctive — the combination of OpenTelemetry, version-pinned telemetry inventory, and component/SDK emission tracking creates a very clear niche. Unlikely to conflict with other skills given the specificity of the domain and use cases.	5 / 5
	Total	18 / 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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: ollygarden/opentelemetry-agent-skills
Path: skills/otel-telemetry-emissions/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.