CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

otel-java

OpenTelemetry in Java — Javaagent zero-code instrumentation, Spring Boot Starter, manual autoconfigure SDK, declarative YAML configuration, BOM dependency management, sensitive-data capture and redaction (url.query, headers, request parameters, SQL sanitization). Use when adding, reviewing, or configuring OpenTelemetry in a Java service. Triggers on "setup otel in java", "java telemetry", "javaagent", "Spring Boot otel", "GlobalOpenTelemetry", "AutoConfiguredOpenTelemetrySdk", "TracerProvider java", "url.query redaction", "capture request headers", or any Java-related OTel question.

Quality

93%

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

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

An excellent entry-point skill: lean, dense with exact commands and URLs, and structured as a pure router with two verified, clearly signaled reference files. The only minor gap is the absence of error-recovery guidance in the fetch workflows, which keeps workflow clarity just below perfect.

DimensionReasoningScore

Conciseness

Every section carries non-obvious, high-value information — exact fetch commands, an explicit 'Do **not** answer from model memory', and the note that the Explorer 'applies upstream metadata corrections that the raw registry does not'. There is no padding or explanation of concepts Claude already knows, matching the 'every token earns its place' anchor.

5 / 5

Actionability

The guidance is copy-paste ready: 'gh api repos/open-telemetry/opentelemetry-java/releases/latest -q '.tag_name'', exact WebFetch URLs per fact type, and a numbered 2-step Explorer navigation ('WebFetch https://explorer.opentelemetry.io/agent/javaagent/index.md' then 'WebFetch that JSON URL'). Specific commands cover the common cases.

5 / 5

Workflow Clarity

The reference routing is unambiguous via the 'Use when' table, and the Explorer lookup is a clear numbered sequence with a built-in diff signal ('a differing hash for the same id across two versions means that instrumentation changed'). It is not anchor 5 because there are no explicit error-recovery checkpoints (e.g., what to do when a fetch 404s or a tag lacks a fixture), though for read-only lookup workflows this is only a minor gap.

4 / 5

Progressive Disclosure

The body is a clear overview pointing to exactly two one-level-deep references (references/declarative-setup.md, references/sensitive-data-capture.md — both verified to exist and be self-contained), each row carrying 'Use when' guidance, plus a fact-to-source table so nothing bulky is inlined. This matches the 'clear overview with well-signaled one-level-deep references' anchor.

5 / 5

Total

19

/

20

Passed

Description

88%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 both what the skill covers and when to use it, backed by a rich, domain-specific trigger list. The only weaknesses are the broad 'any Java-related OTel question' wildcard, which slightly raises conflict risk with sibling otel skills, and a few missing natural trigger synonyms like 'java tracing'.

Suggestions

Add missing natural trigger synonyms such as 'java tracing', 'instrument java service', or 'opentelemetry maven/gradle' to the trigger list so it matches how users most commonly phrase the request.

Narrow the 'any Java-related OTel question' wildcard (e.g., 'any Java-specific OTel setup, config, or telemetry question') to reduce overlap with the language-agnostic otel sibling skills it cross-references.

DimensionReasoningScore

Specificity

The description lists multiple concrete capabilities — 'Javaagent zero-code instrumentation, Spring Boot Starter, manual autoconfigure SDK, declarative YAML configuration, BOM dependency management, sensitive-data capture and redaction (url.query, headers, request parameters, SQL sanitization)' — with comprehensive, fine-grained coverage. It is not below anchor 4 because coverage goes well beyond 'several specific actions with minor gaps'; every named capability is concrete.

5 / 5

Completeness

Both questions are answered explicitly: the 'what' is the enumerated capability list, and the 'when' appears twice — 'Use when adding, reviewing, or configuring OpenTelemetry in a Java service' and an explicit 'Triggers on ...' list of concrete phrases. This matches the anchor-5 example's structure exactly.

5 / 5

Trigger Term Quality

The trigger list includes natural user phrases ('setup otel in java', 'java telemetry', 'javaagent', 'Spring Boot otel', 'capture request headers') plus API-level identifiers, which is good coverage. It falls short of anchor 5 because a few natural variations a user would say are missing (e.g., 'java tracing', 'instrument my java service', 'opentelemetry maven/gradle').

4 / 5

Distinctiveness Conflict Risk

The niche is clear (OpenTelemetry specifically in Java) with distinct Java-only triggers like 'GlobalOpenTelemetry' and 'AutoConfiguredOpenTelemetrySdk'. It is not anchor 5 because the catch-all 'or any Java-related OTel question' widens overlap risk with closely related sibling skills in the same otel family (e.g., language-agnostic schema or semantic-convention skills referenced in the body).

4 / 5

Total

18

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

ollygarden/opentelemetry-agent-skills

Path

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