otel-migration
Retrofitting OpenTelemetry into an existing, uninstrumented application. Trigger phrases: "migrate existing app to OTel", "add OpenTelemetry to existing project", "retrofit OTel into my codebase", "thread context through my code", "context propagation", "bridge Prometheus metrics to OTel", "logging bridge", "migrate logging to OTel", "slog bridge", "logback bridge", "verify my instrumentation", "traces are disconnected", "orphaned spans", "migrate to OpenTelemetry", "OTel migration plan", "how do I sequence an OTel migration", "add tracing to existing code", "refactor for context propagation", "Fiber context gotcha", "keep existing logging working with OTel", "add OTel without breaking Prometheus", "bridge existing metrics", "coexist with existing monitoring". For greenfield instrumentation use otel-instrumentation; for Beelines use beeline-migration.
77
89%
Does it follow best practices?
Impact
100%
1.00x1 of 3 eval scenarios. Add 2 more for a full score.
Passed
No findings from the security scan
| Run | Type | Date | Status |
|---|---|---|---|
baseline vs usage-spec With / without contextCompleted | With / without context | Completed |
Eval run
01a13b86-aaa4-74c0-8e75-8b0763490348
Run
Stats are not available yet
The run is available. Its result stats will appear here when they are ready.
- Repository
honeycombio/agent-skill
- Revision
6bb0927
- Evaluated
- Agent
- Claude Code
- Model
- Claude Sonnet 4.6
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.