CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

otel-sdk-versions

OpenTelemetry release version lookup for SDKs across languages and for the Collector (core, contrib, distributions, builder/OCB), the declarative configuration schema, semantic conventions, and Weaver. Use when choosing the latest compatible released OpenTelemetry SDK, package, or component version, when asked what the latest release of one of these is, and when locating setup docs or examples. Not for Collector build manifests or upgrade-risk assessment.

70

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

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 tight, well-structured instruction-only skill: lean procedural body, one clearly signaled reference file that carries all time-sensitive data, and explicit handling of edge cases like offline mode and index gaps. The only improvements are making the online fallback and recency check more concrete.

Suggestions

In step 5, name the concrete online sources to fall back to (e.g., the release-source URLs in the index's Release Source column, or registry-specific queries) instead of the generic 'official release source'.

Add an explicit recency-check step: when online, re-verify the bundled version against the release source before answering, mirroring the offline staleness phrasing.

DimensionReasoningScore

Conciseness

Every line is procedural guidance with zero padding — no explanation of what OpenTelemetry is, and time-sensitive version data is correctly deferred to the bundled index with an explicit staleness phrasing template for offline use. Assumes Claude's competence throughout.

5 / 5

Actionability

Gives concrete instructions: the exact file to open, a copy-paste offline phrasing ('`<version>` as of `<date>`; a newer release may exist'), and per-package confirmation rules. 'Fall back to the official release source' and the column-based lookups lack concrete online-lookup commands or URLs, leaving minor gaps.

4 / 5

Workflow Clarity

A clear five-step sequence with edge-case branches for offline use, incompatibility, companion packages, and index gaps. Checkpoints cover the failure modes this lookup skill actually has; a minor gap is the absence of an explicit step to verify online whether a newer release exists.

4 / 5

Progressive Disclosure

The body is a lean overview pointing to a single, well-signaled reference one level deep (references/generated/otel-version-index.md, verified to exist as an organized 36-line table file with no nested references). Structure is exactly what progressive disclosure calls for.

5 / 5

Total

18

/

20

Passed

Description

87%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: it concisely states a concrete capability, enumerates its coverage, gives explicit multi-condition 'Use when' triggers, and closes with clear boundary exclusions. Only minor trigger-synonym gaps keep it from full marks.

DimensionReasoningScore

Specificity

States several concrete actions ('release version lookup', 'choosing the latest compatible released ... version', 'locating setup docs or examples') with comprehensive domain enumeration (Collector core, contrib, distributions, builder/OCB, config schema, semconv, Weaver). Falls just short of a 5 because the actions are variations of lookup rather than multiple distinct capabilities.

4 / 5

Completeness

Explicitly answers 'what' (release version lookup for SDKs, Collector components, config schema, semconv, Weaver) and 'when' via a concrete 'Use when ...' clause with three trigger conditions, plus an explicit 'Not for ...' boundary.

5 / 5

Trigger Term Quality

Includes natural user phrasings like 'what the latest release of one of these is', 'latest compatible', 'setup docs or examples'. A few natural terms are missing (the 'otel' shorthand, package-registry names like npm/PyPI/crates.io), which keeps it below comprehensive synonym-level coverage.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (released OpenTelemetry version lookup) with distinct triggers and an explicit exclusion ('Not for Collector build manifests or upgrade-risk assessment'), minimizing conflict with adjacent OTel skills.

5 / 5

Total

18

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 1 deeper-than-1-level

Warning

Total

15

/

16

Passed

Repository

ollygarden/opentelemetry-agent-skills

Path

skills/otel-sdk-versions/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.