CtrlK
BlogDocsLog inGet started
Tessl Logo

beeline-migration

Step-by-step guide for migrating from Honeycomb Beelines (End of Life) to OpenTelemetry instrumentation. Trigger phrases: "migrate from Beelines", "upgrade from Beeline to OpenTelemetry", "migrate to OTel", "replace Beelines", "Beeline end of life", "Beeline EOL", "switch from Beeline to OTel", "migrate Go Beeline", "migrate Python Beeline", "migrate Node Beeline", "migrate Java Beeline", "migrate Ruby Beeline", "W3C trace headers", "W3C propagation", "incremental migration to OpenTelemetry", or any request about migrating from Honeycomb Beelines to OpenTelemetry SDKs.

80

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is well-structured, actionable, and concise, with a clear phased workflow and proper progressive disclosure to verified reference files. It is a strong skill body with no significant weaknesses.

DimensionReasoningScore

Conciseness

The body is lean, assumes Claude's competence (no priming on what OTel or Beeline are), and every section earns its place; the minor restatement in the Status section does not rise to the 'mostly efficient but could be tightened' level 2 threshold.

3 / 3

Actionability

Provides executable code blocks for Go/Python/Node, a concrete minimum-version table, specific env vars (OTEL_SERVICE_NAME), and explicit API mappings (startSpan() -> tracer.start_span(), addField() -> span.set_attribute()), matching the 'fully executable, copy-paste ready' anchor rather than the pseudocode level 2.

3 / 3

Workflow Clarity

A clearly sequenced two-phase workflow with numbered steps, explicit 'Verify' checkpoints, a bold gating rule, and checklists for error-prone migration, matching the 'clear sequence with explicit validation steps' anchor; it is not level 2 because checkpoints are explicit rather than implicit.

3 / 3

Progressive Disclosure

The SKILL.md is a clear overview that defers full per-language migration code and complete W3C config to real, one-level-deep reference files (verified present in ./references/), clearly signaled via a Reference Files section, matching the 'clear overview with well-signaled one-level-deep references' anchor rather than the inline/under-organized level 2.

3 / 3

Total

12

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific, well-triggered, and complete, using third person and answering both what the skill does and when to use it. It is a strong example with no notable weaknesses.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — migrating per-language Beelines to OpenTelemetry SDKs and enabling W3C trace propagation — matching the 'lists multiple specific concrete actions' anchor rather than the partial domain-only level 2.

3 / 3

Completeness

Explicitly states what it does (step-by-step Beeline-to-OTel migration) and when to use it via an explicit 'Trigger phrases:' clause and a catch-all 'or any request about migrating' sentence, satisfying the 'clearly answers both what AND when' anchor rather than capping at 2.

3 / 3

Trigger Term Quality

Broad natural-language coverage ('migrate from Beelines', 'Beeline EOL', 'switch from Beeline to OTel', plus per-language variants) that a user would actually say, matching the 'good coverage of natural terms' anchor; it is not the partial level 2 because common variations are present.

3 / 3

Distinctiveness Conflict Risk

Targets a narrow, well-defined niche (Honeycomb Beeline EOL migration) with distinct triggers unlikely to fire for unrelated skills, matching the 'clear niche with distinct triggers' anchor rather than the overlapping level 2.

3 / 3

Total

12

/

12

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
honeycombio/agent-skill
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.