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.

Quality

94%

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

100%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 body is an exemplary lean lookup workflow: it delegates all volatile data to a single well-organized reference file, provides concrete decision rules and verbatim output phrasing, and covers offline, incompatibility, and coverage-gap edge cases. No meaningful weaknesses were found.

DimensionReasoningScore

Conciseness

The ~30-line body is lean and assumes Claude's competence: no OTel concept explanations, no filler, and time-sensitive data (versions, dates) is kept in the reference file rather than inlined ("its 'Versions last changed' date is the last day any row changed"). Every line is either a decision policy or a concrete instruction, matching anchor 5.

5 / 5

Actionability

Fully actionable for an instruction-only skill: an exact file to open ("Open `references/generated/otel-version-index.md`"), named table columns to use per case, and a copy-paste-ready offline phrasing template ("`<version>` as of `<date>`; a newer release may exist"). The common cases (online lookup, offline lookup, companion packages, gaps) are each covered with specific guidance.

5 / 5

Workflow Clarity

Five clearly sequenced steps with explicit validation checkpoints ("confirm each package individually", "use the Release Source or Release column to confirm") and error-recovery branches for offline mode, incompatible latest releases, and index gaps. This is a read-only lookup skill, so the destructive/batch cap does not apply, and the edge-case handling matches anchor 5's standard.

5 / 5

Progressive Disclosure

The body is under 50 lines and points to a single, clearly signaled, one-level-deep reference (references/generated/otel-version-index.md) that exists in the bundle and itself contains only flat data tables with no nested skill references. Structure and navigation match anchor 5.

5 / 5

Total

20

/

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 that clearly states what the skill does and when to use it, with concrete trigger phrases and an explicit negative scope that reduces conflict risk. The main gaps are minor: missing the "otel" abbreviation and language-specific trigger terms, and actions that are all variations on lookup rather than broader distinct capabilities.

Suggestions

Add the "otel" abbreviation and commonly named languages (e.g., Python, Java, Go) as trigger terms so users' natural phrasing like "latest otel python sdk version" matches the description.

Consider mentioning an additional distinct capability, such as resolving companion exporter/instrumentation package versions, to broaden the concrete actions listed beyond lookup-centric variants.

DimensionReasoningScore

Specificity

Lists several concrete actions ("release version lookup", "choosing the latest compatible released... version", "locating setup docs or examples") with comprehensive scope enumeration across SDKs, Collector components, config schema, semconv, and Weaver. Falls short of 5 because the actions are all lookup-centric variants rather than multiple distinct concrete operations.

4 / 5

Completeness

Explicitly answers both "what" ("OpenTelemetry release version lookup for SDKs across languages and for the Collector...") and "when" with concrete trigger phrases ("Use when choosing the latest compatible released... version, when asked what the latest release of one of these is, and when locating setup docs or examples"), plus a negative-scope clause. Clearly matches anchor 5; anchor 4's "when could be more explicit" does not apply.

5 / 5

Trigger Term Quality

Includes natural phrases users would say — "latest release", "latest compatible", "SDK, package, or component version", "setup docs", "examples" — but omits the common "otel" abbreviation and specific language names (Python, Java, Go) that users typically mention. Good coverage with a few natural terms missing, matching anchor 4 rather than the comprehensive synonym coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (OTel release version lookup) with distinct triggers, and the explicit exclusion "Not for Collector build manifests or upgrade-risk assessment" cleanly separates it from the sibling otel-collector-builder skill. Minimal conflict risk, matching anchor 5.

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.