Agent skill

183 Java Observability Tracing Opentelemetry

by jabrena in jabrena/plinth

A skill your agent uses when you need to implement or improve distributed tracing with OpenTelemetry in Java — including trace/span modeling, context propagation, semantic conventions, span…

Apache-2.0Auto-check passedDevOps & Cloud

Install 183 Java Observability Tracing Opentelemetry

skills CLI
$ npx skills add jabrena/plinth --skill 183-java-observability-tracing-opentelemetry -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install jabrena/plinth 183-java-observability-tracing-opentelemetry --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/jabrena/plinth.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/183-java-observability-tracing-opentelemetry .claude/skills/183-java-observability-tracing-opentelemetry && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
183-java-observability-tracing-opentelemetry
GitHub stars
446
Token cost
~842 tokens
SKILL.md length
305 words
Files
2 (incl. references)
Skills in repo
124
Repo updated
First seen
Licence
Apache-2.0

At a glance

A skill your agent uses when you need to implement or improve distributed tracing with OpenTelemetry in Java — including trace/span modeling, context propagation, semantic conventions, span…

  • You need to implement
  • SKILL.md covers Constraints, When to use this skill, Workflow and Reference
  • Calls mvn
  • Improve distributed tracing with OpenTelemetry in Java — including trace/span modeling

What it does

183 Java Observability Tracing Opentelemetry is an agent skill from jabrena/plinth. 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

Its SKILL.md is about 840 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/183-java-observability-tracing-opentelemetry.md`).

It sits in DevOps & Cloud, covering Observability. It works with OpenTelemetry and Java. The repository describes itself as: Plinth is an AI-native engineering toolkit for modern Java enterprise SDLC, built around reusable Commands, Agents, Skills, and MCP Servers. The licence is Apache-2.0.

When your agent uses it

  • You need to implement
  • Improve distributed tracing with OpenTelemetry in Java — including trace/span modeling
  • Context propagation
  • Semantic conventions

Example prompts

  • “/183-java-observability-tracing-opentelemetry”

What it can do on your machine

Read from SKILL.md and the folder at commit dca88dc. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • mvn

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

183 Java Observability Tracing Opentelemetry loads about 842 tokens when it runs, and up to ~4.4k if it reads all its reference files. Until then it costs about 140 tokens; SKILL.md has 305 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~140
When it runs · the whole SKILL.md, loaded when a task matches
~842
With references · SKILL.md plus every file in references/, read only if the agent opens them
~4.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from jabrena/plinth at commit dca88dc, republished under its Apache-2.0 licence (© jabrena). 305 words, ~842 tokens.

Download SKILL.mdSave it as .claude/skills/183-java-observability-tracing-opentelemetry/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
183-java-observability-tracing-opentelemetry
description
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
license
Apache-2.0
metadata.author
Juan Antonio Breña Moral
metadata.version
0.19.0

Java Distributed Tracing with OpenTelemetry

Implement robust distributed tracing in Java with OpenTelemetry by modeling meaningful spans, preserving context propagation, and instrumenting critical business and infrastructure paths with low-overhead, privacy-safe telemetry.

What is covered in this Skill?

  • OpenTelemetry tracing fundamentals for Java services
  • Span design: boundaries, parent/child relationships, and operation naming
  • Context propagation across HTTP, messaging, async tasks, and thread boundaries
  • Semantic conventions and stable attribute naming
  • Error/status/event recording best practices
  • Sampling strategy and performance/cost trade-offs
  • Privacy and security controls for trace attributes
  • Testing and verification of trace propagation and span correctness

Scope: Distributed tracing quality in application and integration layers, focused on diagnosability, consistency, and operational safety.

Constraints

Tracing instrumentation must preserve context correctly and avoid leaking sensitive data. Over-instrumentation and high-cardinality attributes can harm cost and signal quality.

  • PROPAGATION FIRST: Ensure context propagation across all sync/async boundaries before adding extra span detail
  • NO SENSITIVE DATA: Never store secrets, credentials, tokens, raw payloads, or PII in span attributes/events
  • LOW CARDINALITY ATTRIBUTES: Avoid unbounded values in attributes that are used for aggregation/search
  • VERIFY: Run ./mvnw clean verify or mvn clean verify after applying tracing changes

When to use this skill

  • Improve tracing
  • Apply OpenTelemetry tracing
  • Add distributed tracing
  • Refactor tracing instrumentation
  • Instrument Java services with OpenTelemetry spans

Workflow

  1. Define trace model and critical flows

Identify high-value request and async flows, define operation boundaries, and choose span names/attributes aligned with semantic conventions.

  1. Instrument and propagate context

Add OpenTelemetry spans to key boundaries and ensure trace context is propagated across HTTP clients/servers, messaging, and executor-based async work.

  1. Harden span data and sampling

Record status/errors/events consistently, remove sensitive data, control attribute cardinality, and configure sampling/exporters according to environment needs.

  1. Validate traces end-to-end

Verify parent-child relationships, propagation continuity, and backend visibility through tests and runtime checks.

Reference

For detailed guidance, examples, and constraints, see references/183-java-observability-tracing-opentelemetry.md.

© jabrena, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in skills/183-java-observability-tracing-opentelemetry of jabrena/plinth.

  • SKILL.md
  • references/183-java-observability-tracing-opentelemetry.md

Open the folder on GitHubat commit dca88dc

Compare with similar skills

183 Java Observability Tracing Opentelemetry next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

183 Java Observability Tracing Opentelemetry compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
183 Java Observability Tracing Opentelemetry this skilljabrena/plinth446—~842Automated safety check: PassApache-2.0
Azure Monitor Opentelemetry Exporter Javamicrosoft/skills3.1k6 repos~2.2kAutomated safety check: PassMIT
Opentelemetrygrafana/skills279—~1.7kAutomated safety check: PassApache-2.0
Otel Javaollygarden/opentelemetry-agent-skills106—~1.4kAutomated safety check: PassApache-2.0
Motel Debugkitlangton/motel298—~2.2kAutomated safety check: PassMIT
Tempsgotempsh/temps826—~1.9kAutomated safety check: PassApache-2.0

Similar skills

  • Azure Monitor OpenTelemetry Exporter for Java. An agent skill from microsoft/skills.

    3.1k GitHub starsUsed in 6 repos~2.2k tokens
    DevOps & CloudAuto-check passed
  • Opentelemetry

    grafana/skills

    Official

    Instrument any app with OpenTelemetry and ship metrics / logs / traces to Grafana Cloud or self-hosted Mimir / Loki / Tempo / Pyroscope.

    279 GitHub stars~1.7k tokensUpdated yesterday
    DevOps & CloudAuto-check passed
  • Otel Java

    ollygarden/opentelemetry-agent-skills

    OpenTelemetry in Java — Javaagent zero-code instrumentation, Spring Boot Starter, manual autoconfigure SDK, declarative YAML configuration, BOM dependency management, sensitive-data capture and…

    106 GitHub stars~1.4k tokensUpdated yesterday
    DevOps & CloudAuto-check passed
  • Motel Debug

    kitlangton/motel

    Debug applications with motel, a local OpenTelemetry ingest and query server.

    298 GitHub stars~2.2k tokensUpdated 1 mo ago
    DevOps & CloudAuto-check passed
  • Temps

    gotempsh/temps

    Manage, deploy, operate, and instrument applications with Temps.

    826 GitHub stars~1.9k tokensUpdated today
    DevOps & CloudAuto-check passed
  • UModel Root Cause Analysis

    alibaba/UnifiedModel

    Investigates a service incident to its root cause by querying a UModel object graph alongside metrics, logs, topology and recent deployments.

    412 GitHub stars~1.9k tokensUpdated 14 days ago
    DevOps & CloudAuto-check passed

More from jabrena/plinth

All 124 skills in this repo
  • A skill your agent uses when you need to add or review fuzz testing for Java APIs with CATS — including contract-driven negative testing, malformed payload validation, boundary input exploration, CI…

    446 GitHub stars~874 tokensUpdated yesterday
    Auto-check passed
  • A skill your agent uses when you need to generate Java project diagrams — including UML sequence diagrams, UML class diagrams, C4 model diagrams, UML state machine diagrams, UML Deployment Diagrams…

    446 GitHub stars~3.1k tokensUpdated yesterday
    Auto-check passed
  • A skill your agent uses when you need to add or configure Maven plugins in your pom.xml — including quality tools (enforcer, surefire, failsafe, jacoco, pitest, spotbugs, pmd), security scanning…

    446 GitHub stars~3.2k tokensUpdated yesterday
    Auto-check passed
  • A skill your agent uses when you need to set up JMeter performance testing for a Java project — including creating the run-jmeter.sh script from the exact template, configuring load tests with…

    446 GitHub stars~842 tokensUpdated yesterday
    Auto-check passed
  • A skill your agent uses when you need to set up Java application profiling to detect and measure performance issues — including trusted preinstalled async-profiler v4.x setup, problem-driven…

    446 GitHub stars~903 tokensUpdated yesterday
    Auto-check passed
  • A skill your agent uses when you need to generate a checklist document with embedded commands inventory, following the embedded template exactly and producing INVENTORY-COMMANDS-JAVA.md in the…

    446 GitHub stars~697 tokensUpdated yesterday
    Auto-check passed

Categories

Questions about 183 Java Observability Tracing Opentelemetry

What does 183 Java Observability Tracing Opentelemetry do?

A skill your agent uses when you need to implement or improve distributed tracing with OpenTelemetry in Java — including trace/span modeling, context propagation, semantic conventions, span…. 183 Java Observability Tracing Opentelemetry is an agent skill from jabrena/plinth. 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.

When should I use 183 Java Observability Tracing Opentelemetry?

183 Java Observability Tracing Opentelemetry fits situations like: you need to implement; improve distributed tracing with OpenTelemetry in Java — including trace/span modeling; context propagation; semantic conventions.

How do I install 183 Java Observability Tracing Opentelemetry in Claude Code?

Run `npx skills add jabrena/plinth --skill 183-java-observability-tracing-opentelemetry -a claude-code`. Or copy the skill folder (skills/183-java-observability-tracing-opentelemetry in jabrena/plinth) into .claude/skills/183-java-observability-tracing-opentelemetry in your project. Claude Code loads it when a task matches its description.

How do I install 183 Java Observability Tracing Opentelemetry in Codex?

Run `npx skills add jabrena/plinth --skill 183-java-observability-tracing-opentelemetry -a codex`. Or copy the skill folder (skills/183-java-observability-tracing-opentelemetry in jabrena/plinth) into .agents/skills/183-java-observability-tracing-opentelemetry in your project. Codex loads it when a task matches its description.

Can I use 183 Java Observability Tracing Opentelemetry in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jabrena/plinth --skill 183-java-observability-tracing-opentelemetry -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/183-java-observability-tracing-opentelemetry, .gemini/skills/183-java-observability-tracing-opentelemetry, .github/skills/183-java-observability-tracing-opentelemetry and .opencode/skills/183-java-observability-tracing-opentelemetry in your project.

What does 183 Java Observability Tracing Opentelemetry need to run?

Going by SKILL.md and its folder, 183 Java Observability Tracing Opentelemetry needs the command-line tools its instructions call (mvn).

Does 183 Java Observability Tracing Opentelemetry access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is 183 Java Observability Tracing Opentelemetry safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does 183 Java Observability Tracing Opentelemetry use?

183 Java Observability Tracing Opentelemetry is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does 183 Java Observability Tracing Opentelemetry use?

About 842 tokens (SKILL.md is roughly 3.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 3.6k tokens, read only when the agent opens those files.

What are the alternatives to 183 Java Observability Tracing Opentelemetry?

Skills that share tags, products or a category with 183 Java Observability Tracing Opentelemetry: Azure Monitor Opentelemetry Exporter Java (microsoft/skills, 3.1k stars), Opentelemetry (grafana/skills, 279 stars), Otel Java (ollygarden/opentelemetry-agent-skills, 106 stars) and Motel Debug (kitlangton/motel, 298 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains 183 Java Observability Tracing Opentelemetry?

jabrena (a GitHub user) maintains it in jabrena/plinth, which has 446 GitHub stars. The repository holds 124 skills in this directory. The repository was last updated on October 7, 2026.

Source: jabrena/plinth on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.