otel-upgrade

Assess OpenTelemetry package and Collector upgrades across ecosystems. Use when choosing or validating API, SDK, instrumentation, exporter, Collector distribution, component, image, chart, Operator, OCB build, or configuration versions, including compatibility, required changes, telemetry and runtime behavior, and rollout risk.

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

85%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 instruction skill that routes cleanly to one-level-deep references and includes explicit validation checkpoints with a fail-then-diagnose feedback loop. Minor tightening of a few dense shared-instruction items and surfacing a couple of concrete lookup commands in the body would push it higher.

Dimension	Reasoning	Score
Conciseness	Lean and free of concept explanations Claude already knows (no 'what is OpenTelemetry' padding), with every directive earning its place; a few shared-instruction items (e.g. step 3 and step 6) are dense and could be tightened slightly.	4 / 5
Actionability	Provides concrete, executable routing via the decision table and specific directives (query authoritative registries, validate in a temporary copy/worktree, start with the latest stable candidate) plus a structured report template, but exact commands live in the referenced files rather than the body itself.	4 / 5
Workflow Clarity	The numbered 'Shared instructions' form a clear sequence with explicit validation checkpoints (do not call a candidate validated when checks could not run) and a feedback loop (start with latest stable; if it fails, diagnose and test selected lower versions), satisfying the validation requirement for upgrade/batch operations.	5 / 5
Progressive Disclosure	A concise overview routes to two real, one-level-deep references via a decision table ([Dependency upgrade](references/dependency-upgrade.md), [Collector upgrade](references/collector-upgrade.md)), both verified present, with clear navigation and no nested reference chains.	5 / 5
	Total	18 / 20 Passed

Description

95%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, well-scoped description that clearly states what the skill does and when to invoke it, with comprehensive domain-specific trigger terms. The only minor weakness is reliance on a single dominant action verb ('Assess') despite the broad target coverage.

Dimension	Reasoning	Score
Specificity	Names the domain and many specific concrete targets (API, SDK, instrumentation, exporter, Collector distribution, component, image, chart, Operator, OCB build, configuration) plus assessment aspects (compatibility, required changes, telemetry/runtime behavior, rollout risk), but the action vocabulary is dominated by a single 'Assess'/'choosing or validating' framing rather than multiple distinct verbs.	4 / 5
Completeness	Explicitly answers both 'what' ('Assess OpenTelemetry package and Collector upgrades across ecosystems') and 'when' ('Use when choosing or validating ... versions') with concrete trigger phrasing.	5 / 5
Trigger Term Quality	Comprehensive natural-term coverage for the domain — 'OpenTelemetry', 'Collector', 'package', 'API', 'SDK', 'instrumentation', 'exporter', 'image', 'chart', 'Operator', 'OCB build', 'versions', 'compatibility' — the phrases a user managing OTel upgrades would actually say.	5 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (OpenTelemetry package and Collector version upgrades) with distinct, domain-specific triggers and minimal overlap risk with unrelated skills.	5 / 5
	Total	19 / 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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: ollygarden/opentelemetry-agent-skills
Path: skills/otel-upgrade/SKILL.md
Commit: 8e6ed41

Reviewed: 16 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.