CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

otel-span-events-to-logs-migration

Migrate OpenTelemetry Span Events (AddEvent, RecordException, and language equivalents) to the Logs API following the accepted OTEP 4430 migration plan. Use when migrating instrumentation from span events to log-based events, reviewing code that still uses AddEvent or RecordException, or planning a codebase migration while preserving trace correlation.

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

81%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 migration skill with an excellent validation loop and checklist, concrete language-specific API guidance, and properly one-level-deep references. The main gaps are the unreferenced scan script in the bundle and a dated status paragraph that belongs in the deprecation-plan reference.

Suggestions

Reference scripts/scan-span-events.sh in workflow step 1 (e.g., 'run ./scripts/scan-span-events.sh <directory> or grep for ...') so the bundle's existing scan tool is discoverable and step 1 is copy-paste executable.

Move the dated 'Status as of 2026-10-25 (specification v1.62.0)' snapshot and the .NET Activity.RecordException aside into references/deprecation-plan.md, keeping only the actionable conclusion ('treat existing span-event calls as migration candidates, not automatically invalid code') inline.

Consider mentioning the backward-compat bridge capability in the description or a short 'Capabilities' line so the skill's full scope (scan, classify, migrate, bridge, verify) is visible up front.

DimensionReasoningScore

Conciseness

The body is lean with no concept padding and delegates detail to references, but the 'Status as of 2026-10-25 (specification v1.62.0)' paragraph embeds a dated status snapshot with a long .NET parenthetical inline rather than in references/deprecation-plan.md. Not 5 because that time-sensitive material (specific dates/version numbers outside a deprecated/old-patterns section) could be trimmed or moved; not 3 since the rest is efficient and version specifics in step 3 are operationally necessary.

4 / 5

Actionability

Gives concrete, executable guidance: exact scan symbols (AddEvent, record_error, AddException, ...), exact Go APIs ('otel.Logger', 'Record.SetEventName', 'attribute.String(...)'), exact Java artifact/class ('io.opentelemetry.sdk.extension.incubator.logs.EventToSpanEventBridge' from 'opentelemetry-sdk-extension-incubator'), and required semconv attributes with the 'at least one is required' rule. Not 5 because no runnable code or commands appear inline and the bundle's ready-made scan tool (scripts/scan-span-events.sh) is never surfaced, leaving step 1 as manual grep instructions.

4 / 5

Workflow Clarity

Clear 0-5 sequence with a 'Required Completion Loop' that mandates re-reading changed files, confirming each checklist item with codebase evidence, and repeating until every item is completed or explicitly not applicable. This is exactly the anchor-5 pattern: explicit validation steps, feedback loops for error recovery, and a checklist for a batch operation.

5 / 5

Progressive Disclosure

Four references (deprecation-plan.md, decision-tree.md, migration-patterns.md, backward-compat.md) all exist, are one level deep, and each is clearly signaled at the appropriate workflow step. Not 5 because scripts/scan-span-events.sh exists in the bundle but is never referenced from SKILL.md, leaving a key asset undiscoverable.

4 / 5

Total

17

/

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 description: specific, in third person, with an explicit 'Use when' clause covering three concrete trigger scenarios and exact API names. Only minor capability coverage is missing relative to the body's full feature set.

DimensionReasoningScore

Specificity

Names concrete actions ('Migrate OpenTelemetry Span Events ... to the Logs API following the accepted OTEP 4430 migration plan', 'preserving trace correlation') and the exact source APIs (AddEvent, RecordException, and language equivalents). Not 5 because coverage of the skill's capabilities is incomplete (e.g., the backward-compat bridge and decision-tree classification are not mentioned); clearly above 3 since more than 1-2 actions are named specifically.

4 / 5

Completeness

Explicitly answers both questions: what ('Migrate ... to the Logs API following the accepted OTEP 4430 migration plan') and when ('Use when migrating instrumentation ..., reviewing code that still uses AddEvent or RecordException, or planning a codebase migration'). Concrete trigger phrases match the 5 anchor exactly.

5 / 5

Trigger Term Quality

Covers natural phrasings users would actually say: 'migrating instrumentation from span events to log-based events', 'reviewing code that still uses AddEvent or RecordException', 'planning a codebase migration', plus synonyms (span events, Logs API, log-based events, trace correlation). Above 4 because synonym and API-name coverage is thorough for this domain.

5 / 5

Distinctiveness Conflict Risk

A clear niche ('OpenTelemetry Span Events', 'OTEP 4430', 'AddEvent or RecordException') with distinct triggers; virtually no overlap risk with other skills. Matches the 'clear niche with distinct triggers' anchor.

5 / 5

Total

19

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

ollygarden/opentelemetry-agent-skills

Path

skills/otel-span-events-to-logs-migration/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.