CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

otel-go

OpenTelemetry in Go — SDK setup, API surface, breaking changes, contrib instrumentation libraries (otelhttp, otelgrpc, otelmongo), compile-time zero-code instrumentation (otelc), and performance tuning. Use when adding, reviewing, or configuring OpenTelemetry in a Go service. Triggers on "setup otel in go", "go telemetry", "go tracing", "otelconf go", "otelhttp", "otelgrpc", "TracerProvider go", "MeterProvider go", "otelc", "compile-time instrumentation go", "zero-code go instrumentation", "go build instrumentation", or any Go-related OTel question.

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

86%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 hub skill: appropriately concise, highly actionable with executable commands, and cleanly splitting detail into six one-level-deep references. The main gaps are minor — time-sensitive version details inline rather than isolated, and no explicit error-recovery loop for the verification path.

Suggestions

Move or isolate time-sensitive facts (the "verified 2026-10-25" semconv parenthetical, specific version examples like v1.47.0/v0.72.0) into a dedicated versioning/record section or reference file so the main body stays evergreen.

Add a brief error-recovery step to the upgrade verification path (e.g., what to check and retry when `go mod tidy -diff` or `go build ./...` fails) to close the workflow-clarity gap.

DimensionReasoningScore

Conciseness

Nearly every section carries non-obvious, decision-critical information (the module-version-group trap, exact fetch commands), with no explanations of concepts Claude already knows. Minor trims possible: the dated "verified 2026-10-25 (record: ...)" parenthetical and inline version numbers (v1.47.0, v0.72.0) are time-sensitive details not placed in a deprecated/old-patterns section. Not 5 due to those instances; not 3 because padding is genuinely rare.

4 / 5

Actionability

Fully executable, copy-paste-ready guidance: the `go get ... @latest` block with `go mod tidy && go build ./...`, `gh api repos/.../releases/latest -q '.tag_name'` commands, WebFetch CHANGELOG URLs, and a tag-sorting one-liner covering the common cases. Matches the anchor-5 example of executable commands plus specific lookups; nothing is pseudocode.

5 / 5

Workflow Clarity

Clear routing workflow (task → reference table) with explicit validation checkpoints for upgrade reviews ("always finish with a safe local verification path (`go mod tidy -diff`, `go build ./...`, and `go test ./...`)") and a safety constraint ("never a deployment endpoint"). Not 5 because no error-recovery/feedback loop is described (e.g., what to do when the verification fails); not 3 since validation checkpoints are explicit rather than implicit.

4 / 5

Progressive Disclosure

A clean overview with a well-signaled references table (one row per file with a "Use when" column); all six referenced files (api.md, breaking-changes.md, compile-time-instrumentation.md, declarative-setup.md, instrumentation-libraries.md, performance.md) exist one level deep in the bundle, and inline content is limited to decision-critical material. Matches the anchor-5 structure of a concise hub with clear one-level-deep navigation.

5 / 5

Total

18

/

20

Passed

Description

91%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 that explicitly states what the skill covers, when to use it, and a comprehensive set of natural trigger phrases. The only weaknesses are minor: a few capability entries are topic nouns rather than actions, and the otelconf-related trigger slightly overlaps a sibling skill.

DimensionReasoningScore

Specificity

Lists several concrete capabilities — "SDK setup", "performance tuning", "contrib instrumentation libraries (otelhttp, otelgrpc, otelmongo)", "compile-time zero-code instrumentation (otelc)" — but mixes in topic nouns like "API surface" and "breaking changes" that aren't actions. Not 5 because the anchor-5 example is uniformly verb-based concrete actions; not 3 because coverage here is broad and mostly specific.

4 / 5

Completeness

Explicitly answers both: what ("SDK setup, API surface, breaking changes, contrib instrumentation libraries..., and performance tuning") and when ("Use when adding, reviewing, or configuring OpenTelemetry in a Go service. Triggers on...") with concrete trigger phrases. Clearly the anchor-5 example pattern; 4 would require the 'when' to be less explicit, which it is not.

5 / 5

Trigger Term Quality

Comprehensive natural trigger phrases including synonyms and variations: "setup otel in go", "go telemetry", "go tracing", "zero-code go instrumentation", "go build instrumentation", plus specific identifiers ("otelhttp", "otelgrpc", "otelc", "TracerProvider go") and a broad catch-all. Matches the anchor-5 pattern of full coverage with synonyms; nothing common is missing.

5 / 5

Distinctiveness Conflict Risk

A clear Go+OTel niche with distinct triggers, but the "otelconf go" trigger and declarative-config coverage overlap the sibling otel-declarative-config skill mentioned in the body, creating minor conflict risk within a closely-related skill family. Not 5 due to that overlap; not 3 since the niche boundary (Go-specific OTel) is otherwise unambiguous.

4 / 5

Total

18

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

15

/

16

Passed

Repository

ollygarden/opentelemetry-agent-skills

Path

skills/otel-go/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.