CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

69

Quality

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Failed to scan

The risk profile of this skill

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, lean reference skill body with a clear lookup workflow and explicit anti-hallucination guardrails. Adding a brief sample data-file row would push actionability to fully concrete.

Suggestions

Include a short example data-file excerpt (frontmatter plus one table row) so the 'What a data file contains' section is concrete rather than only descriptive.

Show a one-line example of how to phrase the 'exact version is unverified' fallback message so Claude applies the guardrail consistently.

DimensionReasoningScore

Conciseness

Lean and efficient (~45 lines); assumes Claude's competence and explains no background concepts; every section earns its place.

5 / 5

Actionability

Concrete lookup steps, an exact path example, and explicit fallback rules make the guidance actionable; the only minor gap is the absence of a sample data-file row to illustrate the described structure.

4 / 5

Workflow Clarity

A clear four-step lookup sequence with explicit guardrails ('say the exact version is unverified', 'do not infer from semconv') that function as validation checkpoints for a non-destructive task.

4 / 5

Progressive Disclosure

Under 50 lines with well-organized sections and no need for external reference files, satisfying the simple-skill exception for progressive disclosure.

5 / 5

Total

18

/

20

Passed

Description

82%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 clear, well-targeted description that explicitly states both the capability and concrete usage triggers, with good natural keyword coverage for its niche. The only gap is that it frames one core action (inventory/lookup) rather than listing several distinct capabilities.

DimensionReasoningScore

Specificity

Names the domain and concrete telemetry types (spans, metrics, logs, attributes), but the capability is essentially a single inventory/lookup action plus version comparison rather than several distinct actions.

3 / 5

Completeness

Explicitly answers both what (version-pinned inventory of emitted telemetry) and when (Use when working with a covered component, comparing versions, or upgrading), with concrete trigger phrases.

5 / 5

Trigger Term Quality

Strong coverage of natural niche terms (telemetry, spans, metrics, logs, OpenTelemetry collector, SDK instrumentation, upgrading a version), with only a few synonyms missing.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (OTel telemetry emissions, version-pinned) with distinct triggers and minimal overlap risk with other skills.

5 / 5

Total

17

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
ollygarden/opentelemetry-agent-skills
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.