CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

74

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

82%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 dense, highly actionable index skill: every command and URL is concrete and executable, and reference routing is well signaled. The main weaknesses are the near-verbatim duplication of the Sources-of-Truth table between SKILL.md and references/declarative-setup.md and the absence of routing priority or fetch-failure guidance.

Suggestions

Deduplicate the Sources of Truth table: keep it in references/declarative-setup.md (or the sensitive-data reference as appropriate) and have SKILL.md link to it, instead of repeating ~9 rows in both files.

State a routing priority or decision rule for when both references apply (e.g., setup questions always load declarative-setup.md first, capture/redaction questions load sensitive-data-capture.md).

Add one line of fallback guidance for the Explorer/WebFetch workflow (e.g., what to do if the index or JSON fetch fails), which is the only multi-step sequence in the body.

DimensionReasoningScore

Conciseness

The body is lean — no concept explanations, just routing tables and concrete fetch commands — but the "Sources of Truth" table rows (BOM, Javaagent, smoke fixtures, starter docs) are duplicated nearly verbatim in references/declarative-setup.md, so those tokens are paid twice whenever the reference is loaded. That is trimmable duplication rather than severe padding, sitting between the efficient and lean anchors.

4 / 5

Actionability

Everything is copy-paste executable: `gh api repos/open-telemetry/opentelemetry-java/releases/latest -q '.tag_name'`, exact WebFetch URLs with parameterized tags, and the two-step Explorer navigation with concrete index/JSON/schema URLs. No pseudocode or vague direction anywhere.

5 / 5

Workflow Clarity

The Explorer lookup is clearly sequenced (numbered index→record steps plus explicit version-diff logic: "a differing hash for the same id across two versions means that instrumentation changed") and "Do not answer from model memory" acts as a verification directive. However routing between the two references relies only on the Use-when column with no stated priority when both apply, and no error-recovery guidance if a fetch fails — minor gaps against the anchor-5 sequence.

4 / 5

Progressive Disclosure

Structure is good: a References table with both files verified real and one-level-deep, well-signaled links with per-file use-when descriptions, and clearly labeled cross-references to sibling skills. The gap is that the substantial Sources-of-Truth table is inlined in SKILL.md while being duplicated in declarative-setup.md rather than living in one place — content that should be split (or deduplicated) sits in both, matching the minor-organization-gaps anchor.

4 / 5

Total

17

/

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 model description: third-person voice, comprehensive and specific capability enumeration with concrete attribute names, an explicit 'Use when' clause, and a rich trigger list covering natural phrases, synonyms, and code identifiers. No fluff or over-claims.

DimensionReasoningScore

Specificity

Lists multiple specific concrete capabilities — "Javaagent zero-code instrumentation", "manual autoconfigure SDK", "BOM dependency management", "sensitive-data capture and redaction (url.query, headers, request parameters, SQL sanitization)" — with concrete attribute names, plus explicit actions ("adding, reviewing, or configuring"). Coverage of the OpenTelemetry-in-Java domain is comprehensive with no noticeable gaps, matching the anchor-5 example's breadth.

5 / 5

Completeness

Explicitly answers what (the enumerated capability list) and when ("Use when adding, reviewing, or configuring OpenTelemetry in a Java service" plus a concrete trigger-phrase list), matching the anchor-5 example structure. The 'when' clause is concrete, not weakly implied.

5 / 5

Trigger Term Quality

Triggers include natural user phrases ("setup otel in java", "java telemetry", "javaagent", "Spring Boot otel"), synonym variants (otel/telemetry), code identifiers users would paste ("GlobalOpenTelemetry", "AutoConfiguredOpenTelemetrySdk"), and task-shaped phrases ("url.query redaction", "capture request headers"), closed by a catch-all "any Java-related OTel question". No natural term for this niche is missing.

5 / 5

Distinctiveness Conflict Risk

Clear niche (OpenTelemetry in Java) with distinct triggers — "javaagent", "Spring Boot otel", "TracerProvider java" — unlikely to fire for the wrong skill; even the declarative-YAML mention stays Java-scoped, and no other skill's domain overlaps.

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
ollygarden/opentelemetry-agent-skills
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.