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.

Quality

84%

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

78%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 well-structured and actionable, with a clear two-phase workflow, validation checkpoints, and clean progressive disclosure into two real reference files. The main improvement areas are making error-recovery loops explicit and tightening the few redundancies.

Suggestions

Add an explicit feedback loop to Phase 1/Phase 2 verify steps (e.g., 'If traces do not link, confirm W3C is enabled on all services and re-deploy before proceeding').

De-duplicate the 'Complete Phase 1 across all services before starting Phase 2' rule, which appears in both the Phase 2 section and the Migration Safety Checklist.

Inline a minimal OTLP exporter configuration example or a one-line pointer so the core migration path is fully executable without opening the reference file.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence, with tight tables and code snippets; minor trim opportunities exist (the opening line repeats the description, and the 'Complete Phase 1 across ALL services' rule is stated in both the strategy section and the safety checklist).	4 / 5
Actionability	Provides executable Go/Python/Node.js W3C snippets and concrete checklists, with full per-language migration code and field-mapping tables in the referenced files; minor gaps remain (Java/Ruby W3C config and OTLP exporter details are deferred to references rather than inline).	4 / 5
Workflow Clarity	The two-phase migration is clearly sequenced with explicit 'Verify' checkpoints and a service migration checklist, but error-recovery feedback loops (verify -> fix -> retry) are implied rather than spelled out, leaving it just below the top anchor.	4 / 5
Progressive Disclosure	SKILL.md is a concise overview that points to two real one-level-deep reference files (migration-steps-by-language.md, w3c-propagation.md) via clearly signaled full paths, with detailed per-language content appropriately split out and a cross-reference to the otel-instrumentation skill.	5 / 5
	Total	17 / 20 Passed

Description

90%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.

The description is strong: it explicitly states both what the skill does and when to use it, with an extensive set of natural trigger phrases and synonyms. The only weakness is specificity, where a single high-level action ('migrating') is named rather than a list of concrete capabilities.

Dimension	Reasoning	Score
Specificity	Names the domain and a single concrete action ('Step-by-step guide for migrating from Honeycomb Beelines ... to OpenTelemetry instrumentation'), but does not enumerate several specific actions; fits the '1-2 concrete actions' anchor rather than the multi-action anchor above.	3 / 5
Completeness	Explicitly answers both 'what' (step-by-step Beeline-to-OTel migration guide) and 'when' via a dedicated 'Trigger phrases:' list plus 'or any request about migrating from Honeycomb Beelines to OpenTelemetry SDKs.'	5 / 5
Trigger Term Quality	Comprehensive natural trigger coverage including synonyms ('Beeline end of life'/'Beeline EOL', 'migrate to OTel'/'OpenTelemetry') and per-language variants ('migrate Go/Python/Node/Java/Ruby Beeline'), matching the comprehensive-coverage anchor.	5 / 5
Distinctiveness Conflict Risk	Occupies a clear, narrow niche (Beeline EOL migration) with distinct, unambiguous triggers and minimal overlap risk with other skills.	5 / 5
	Total	18 / 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: honeycombio/agent-skill
Path: honeycomb/skills/beeline-migration/SKILL.md
Commit: 41214b7

Reviewed: 5 days 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.