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

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

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.

A well-structured entry-point skill that delegates detail to two genuine reference files and gives concrete live-source fetch commands. Main weakness is duplication of the Sources-of-Truth table between the body and a reference, a minor token inefficiency.

Suggestions

Deduplicate the 'Sources of Truth' fetch table: keep a concise pointer in SKILL.md and host the full table only in references/declarative-setup.md to save tokens.

Make reference selection more decisive by mapping each common task ('setup', 'redact query params', 'capture headers') to a named reference file rather than the generic 'Load a reference below based on the task'.

Add one or two inline minimal setup snippets (e.g. the javaagent -javaagent flag or the Spring Boot starter dependency) so the entry point is self-sufficient for the most common case without forcing a reference load.

Dimension	Reasoning	Score
Conciseness	The body is a lean entry point with no concept padding and assumes Claude's competence, but the sizable 'Sources of Truth' fetch-command table is duplicated verbatim inside references/declarative-setup.md, so some tokens could be trimmed by deferring it to the reference.	4 / 5
Actionability	Provides copy-paste-ready commands ('gh api repos/.../releases/latest -q .tag_name', exact WebFetch URLs) and a numbered Explorer navigation sequence, but the actual instrumentation setup code lives in the references rather than the body, leaving minor gaps in the entry-point itself.	4 / 5
Workflow Clarity	The reference-selection table and the numbered Explorer lookup give a clear sequence with no destructive/batch operations needing validation, though 'Load a reference below based on the task' leaves the reference choice slightly implicit rather than decisively routed.	4 / 5
Progressive Disclosure	A clear overview points to two real, well-signaled one-level-deep references via a 'Use when' table (verified files exist), with content appropriately split out and sibling skills cross-referenced — easy to navigate.	5 / 5
	Total	17 / 20 Passed

Description

96%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, specific description that crisply states capabilities and gives explicit, natural trigger phrases for both conversational and code-context invocation. The only soft spot is a slightly broad catch-all tail that risks minor overlap with sibling otel skills.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capabilities with sub-detail — 'Javaagent zero-code instrumentation', 'Spring Boot Starter', 'manual autoconfigure SDK', 'declarative YAML configuration', 'BOM dependency management', and 'sensitive-data capture and redaction (url.query, headers, request parameters, SQL sanitization)' — comprehensive coverage rather than a couple of actions.	5 / 5
Completeness	Explicitly answers both 'what' (the enumerated capability list) and 'when' ('Use when adding, reviewing, or configuring OpenTelemetry in a Java service' plus a concrete 'Triggers on ...' phrase list), matching the anchor for clearly answering both with concrete triggers.	5 / 5
Trigger Term Quality	Natural user phrases ('setup otel in java', 'java telemetry', 'javaagent', 'Spring Boot otel', 'url.query redaction', 'capture request headers') are present alongside synonyms (otel/telemetry) and code-context API class names, giving comprehensive keyword coverage.	5 / 5
Distinctiveness Conflict Risk	Scoped clearly to OpenTelemetry-in-Java with Java-specific triggers (javaagent, Spring Boot otel, Java API classes), but the broad catch-all 'or any Java-related OTel question' and the cross-referenced sibling otel-* skills create minor overlap risk with closely related skills.	4 / 5
	Total	19 / 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: ollygarden/opentelemetry-agent-skills
Path: skills/otel-java/SKILL.md
Commit: 8e6ed41

Reviewed: 13 hours 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.