CtrlK
BlogDocsLog inGet started
Tessl Logo

otel-instrumentation

Provides guidance on OpenTelemetry SDK setup, custom instrumentation, and sending data to Honeycomb. Trigger phrases: "instrument my app", "add tracing", "set up OpenTelemetry", "configure OTel", "add custom spans", "add attributes to spans", "send traces to Honeycomb", "set up OTLP", "configure sampling", "add span events", "add span links", "set up tracing for [any language]", "configure the OTel Collector", or any request about OpenTelemetry SDK setup, custom instrumentation, or sending data to Honeycomb.

70

Quality

86%

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

72%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, Honeycomb-specific instrumentation reference with executable code and clear progressive disclosure to real bundle files. Its main weakness is workflow clarity, since it reads as a decision manual rather than a sequenced process with explicit validation checkpoints.

Suggestions

For operations with failure modes (e.g., silent auth failure, local collector verification), add an explicit validate→fix→retry sequence in the body or flag that the local-collector-debug-test reference provides the checkpoint loop.

Tighten the sampling tradeoffs and layered-telemetry prose to reduce token cost while preserving the decision guidance.

Surface at least one Node.js inline example alongside the Go/Python ones so the most common runtime has copy-paste-ready code in the body.

DimensionReasoningScore

Conciseness

Efficient and assumes Claude's competence (no basic-OTel primers), but some explanatory prose on sampling tradeoffs and layered telemetry could be tightened slightly. Clearly above the 'mostly efficient with unnecessary explanation' anchor but not perfectly lean.

4 / 5

Actionability

Provides concrete, executable Go and Python code blocks plus exact env var values and protocol options. Mostly executable with minor gaps (Node/Java/Ruby/.NET/Rust code is deferred to references).

4 / 5

Workflow Clarity

Content is a decision-oriented reference (tables, heuristics) rather than a sequenced operation; steps are present but validation checkpoints are implicit. No destructive/batch workflow triggers the stricter cap, and it does not reach the 'clear sequence with most checkpoints' anchor.

3 / 5

Progressive Disclosure

Clear overview body with well-signaled, one-level-deep references to real bundle files, each listed in 'Additional Resources' with a one-line description, plus cross-references to sibling skills. Content is appropriately split across files.

5 / 5

Total

16

/

20

Passed

Description

100%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 concise, third-person description that pairs a clear capability statement with an exhaustive list of natural trigger phrases. It explicitly answers both 'what' and 'when' and occupies a distinct, low-conflict niche.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('SDK setup', 'custom instrumentation', 'sending data to Honeycomb') covering the skill's scope comprehensively.

5 / 5

Completeness

Explicitly answers both what (guidance on SDK setup, custom instrumentation, sending data to Honeycomb) and when (concrete trigger phrases prefixed by 'Trigger phrases:').

5 / 5

Trigger Term Quality

Comprehensive natural trigger phrases including synonyms and abbreviations ('instrument my app', 'add tracing', 'configure OTel', 'set up OTLP', 'add span events/links').

5 / 5

Distinctiveness Conflict Risk

Clear niche scoped to OpenTelemetry + Honeycomb with distinct, domain-specific triggers; minimal overlap risk with sibling skills.

5 / 5

Total

20

/

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.

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.