CtrlK
BlogDocsLog inGet started
Tessl Logo

183-java-observability-tracing-opentelemetry

Use when you need to implement or improve distributed tracing with OpenTelemetry in Java — including trace/span modeling, context propagation, semantic conventions, span attributes/events/status, sampling strategy, baggage usage, privacy safeguards, and backend integration with OTLP collectors. This should trigger for requests such as Improve tracing; Apply OpenTelemetry tracing; Add distributed tracing; Refactor tracing instrumentation; Instrument Java services with OpenTelemetry spans. Part of Plinth Toolkit

70

Quality

85%

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

71%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-organized overview that practices clean progressive disclosure — a lean body pointing to one real reference file with a clear workflow and verification checkpoint. Its main weakness is actionability in the body itself, since executable instrumentation code is delegated to the reference rather than shown inline.

Suggestions

Add one small inline Java span-creation snippet (e.g. spanBuilder/startSpan/endSpan with status) in the Workflow so the body is executable on its own, not just the reference.

Tighten the opening paragraph or merge it with the 'What is covered' list to remove the redundancy between the prose overview and the bullets.

Make the VERIFY step an explicit feedback loop ('if verification fails, fix instrumentation and re-run') to reach anchor-5 workflow clarity.

DimensionReasoningScore

Conciseness

The body is efficient and assumes Claude's competence (no OpenTelemetry basics explained), but the opening paragraph restates topics already covered by the 'What is covered' bullet list, a minor redundancy that could be trimmed. It is above the anchor-3 midpoint but not perfectly lean.

4 / 5

Actionability

Concrete guidance is limited to one command ('Run `./mvnw clean verify` or `mvn clean verify`') and high-level workflow directives like 'Add OpenTelemetry spans to key boundaries'; the executable Java/OTel code lives in the reference file rather than the body, so guidance is present but incomplete.

3 / 5

Workflow Clarity

Four steps are clearly sequenced and step 4 ('Validate traces end-to-end') plus the VERIFY constraint provide a validation checkpoint, but there is no explicit fix-and-retry feedback loop, leaving a minor gap versus anchor 5.

4 / 5

Progressive Disclosure

The body is a concise overview that signals a single one-level-deep reference ('see references/183-java-observability-tracing-opentelemetry.md'), which exists as a real 434-line structured file; content is appropriately split and navigation is easy.

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 strong, well-structured description that clearly states what the skill does and when to invoke it, with concrete capability coverage and natural trigger phrases. It follows the exemplar pattern closely with no fluff.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities — 'trace/span modeling, context propagation, semantic conventions, span attributes/events/status, sampling strategy, baggage usage, privacy safeguards, and backend integration with OTLP collectors' — giving comprehensive coverage anchored by the lead action 'implement or improve distributed tracing'.

5 / 5

Completeness

Explicitly answers both 'what' (implement/improve distributed tracing with OpenTelemetry in Java plus a capability list) and 'when' ('Use when you need to...' plus named trigger requests), matching the anchor-5 pattern.

5 / 5

Trigger Term Quality

Provides five natural trigger phrases users would actually say — 'Improve tracing; Apply OpenTelemetry tracing; Add distributed tracing; Refactor tracing instrumentation; Instrument Java services with OpenTelemetry spans' — covering synonyms (tracing, instrumentation, distributed tracing).

5 / 5

Distinctiveness Conflict Risk

The narrow niche 'distributed tracing with OpenTelemetry in Java' with OTLP collectors gives a clear, distinct trigger surface with minimal overlap risk against other 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
jabrena/plinth
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.