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. Part of cursor-rules-java project

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

70%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured overview body with a clear workflow, explicit validation, and proper progressive disclosure to a single reference file. Its weaknesses are mild redundancy with the description and high-level, code-less actionability in the body itself.

Suggestions

Remove or condense the "When to use this skill" section, since those triggers already appear verbatim in the frontmatter description.

Add one small inline code snippet (e.g. a minimal span-creation or context-propagation example) so the body is actionable without forcing a jump to the reference.

Tighten the "What is covered in this Skill?" list so it does not restate the Workflow and Constraints sections.

Dimension	Reasoning	Score
Conciseness	The body is lean and does not explain concepts Claude already knows, but the "When to use this skill" section duplicates the description's trigger phrases and the "What is covered" list overlaps the Workflow and Constraints, so it could be tightened.	2 / 3
Actionability	It provides one concrete command ("./mvnw clean verify" / "mvn clean verify") and specific constraints, but the actual executable tracing instrumentation is delegated to the reference file and the workflow steps remain high-level ("Add OpenTelemetry spans to key boundaries...").	2 / 3
Workflow Clarity	A clear four-step numbered sequence is present, with an explicit VERIFY checkpoint (the mvn command) and a dedicated "Validate traces end-to-end" step covering parent-child relationships, propagation continuity, and backend visibility.	3 / 3
Progressive Disclosure	The body is a well-organized overview that signals a single one-level-deep reference (verified to exist: references/183-java-observability-tracing-opentelemetry.md) via a dedicated Reference section with a markdown link, matching the clear-overview pattern.	3 / 3
	Total	10 / 12 Passed

Description

90%

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 with explicit trigger terms and clear what/when guidance. Its only notable flaw is the second-person phrasing ("Use when you need to..."), which the rubric penalizes on specificity.

Suggestions

Rephrase in third person to avoid the specificity penalty, e.g. "Implements and improves distributed tracing with OpenTelemetry in Java..." instead of "Use when you need to...".

Consider trimming the long capability list slightly to keep the description scannable without losing concrete signal.

Dimension	Reasoning	Score
Specificity	Lists 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") which would merit a 3, but the description uses second-person voice ("Use when you need to implement or improve..."), incurring the mandated one-point specificity penalty.	2 / 3
Completeness	Explicitly answers both what (the listed tracing capabilities) and when ("Use when you need to implement or improve distributed tracing...") with explicit trigger guidance.	3 / 3
Trigger Term Quality	Includes natural trigger phrases users would actually say ("Improve tracing; Apply OpenTelemetry tracing; Add distributed tracing; Refactor tracing instrumentation"), giving good coverage of common phrasings.	3 / 3
Distinctiveness Conflict Risk	The niche is clear and specific (distributed tracing with OpenTelemetry in Java) with distinct triggers, making conflict with other skills unlikely.	3 / 3
	Total	11 / 12 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: jabrena/cursor-rules-java
Commit: 86eb63d

Reviewed: 4 days 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.