181 Java Observability Logging

Community

jabrena

181-java-observability-logging

Use when you need to implement or improve Java logging and observability — including selecting SLF4J with Logback/Log4j2, applying proper log levels (ERROR, WARN, INFO, DEBUG, TRACE), parameterized logging, correlation context, secure logging without sensitive data exposure, environment-specific configuration, log aggregation, monitoring, and alerting. This should trigger for requests such as Improve logging; Apply logging; Refactor logging; Add logging support; Review SLF4J structured logging in Java code. Part of Plinth Toolkit

Overview

Publisher	jabrena
Repository	`plinth`
Skill name	`181-java-observability-logging`
Stars	455
Forks	95
Bundled files	1
License	Apache-2.0
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
1 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by jabrena on GitHub. Read the source before you install it.

Installation

Install the 181 Java Observability Logging AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/jabrena/plinth/tree/main/skills/181-java-observability-logging
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/jabrena/plinth.git /tmp/plinth
mkdir -p .claude/skills
cp -r /tmp/plinth/skills/181-java-observability-logging .claude/skills/181-java-observability-logging

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable 181 Java Observability Logging in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads 181 Java Observability Logging on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so 181 Java Observability Logging is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Java Logging Best Practices

Implement effective Java logging following standardized frameworks, meaningful log levels, core practices (parameterized logging, exception handling, no sensitive data), explicit correlation context, flexible configuration, security-conscious logging, monitoring, and alerting.

What is covered in this Skill?

Standardized framework selection: SLF4J facade with Logback or Log4j2
Meaningful and consistent log levels: ERROR, WARN, INFO, DEBUG, TRACE
Core practices: parameterized logging, proper exception handling, avoiding sensitive data
Configuration: environment-specific (logback.xml, log4j2.xml), output formats, log rotation
Security: mask sensitive data, control log access, secure transmission, GDPR/HIPAA compliance
Log monitoring and alerting: centralized aggregation (ELK, Splunk, Loki), automated alerts

Scope: The reference is organized by examples (good/bad code patterns) for each core area. Apply recommendations based on applicable examples.

Constraints

Before applying any logging recommendations, ensure the project compiles. Compilation failure is a blocking condition. After applying improvements, run full verification.

MANDATORY: Run ./mvnw compile or mvn compile before applying any change
SAFETY: If compilation fails, stop immediately — do not proceed until resolved
VERIFY: Run ./mvnw clean verify or mvn clean verify after applying improvements
BEFORE APPLYING: Read the reference for detailed good/bad examples, constraints, and safeguards for each logging pattern

When to use this skill

Improve logging
Apply logging
Refactor logging
Add logging support
Review SLF4J structured logging in Java code

Workflow

Compile project before logging changes

Run ./mvnw compile or mvn compile and stop immediately if compilation fails.

Read logging reference and assess current observability

Read references/181-java-observability-logging.md and evaluate framework usage, log levels, sensitive-data handling, and config gaps.

Apply logging and observability improvements

Implement selected framework/configuration/practice changes, including secure logging and monitoring integration where applicable.

Verify with full build

Run ./mvnw clean verify or mvn clean verify after applying improvements.

Reference

For detailed guidance, examples, and constraints, see references/181-java-observability-logging.md.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

references/181-java-observability-logging.md16 KB

Frequently asked questions

What does the 181 Java Observability Logging AI skill do?

Why use 181 Java Observability Logging on TypingMind?

Because you install it once and use it with any model. 181 Java Observability Logging is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install 181 Java Observability Logging in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/jabrena/plinth/tree/main/skills/181-java-observability-logging. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use 181 Java Observability Logging?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with 181 Java Observability Logging?

As many as you like. As long as a model supports skills, you can use 181 Java Observability Logging with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the 181 Java Observability Logging AI skill free?

Yes. It is published on GitHub by jabrena under the Apache-2.0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Deslop

openclaw

OrganizationPopular

Diff-scoped AI-slop cleanup pass: strip comment slop, defensive-check slop, type-laundering, and style drift from the current branch diff before autoreview.

Discord Clawd

Use to talk to the Discord-backed OpenClaw agent/session; not for archive search.

Discrawl

Discord archive: search, sync freshness, DMs, summaries, TUI, repo/release work.

Gitcrawl

GitHub archive: issue/PR search, sync freshness, duplicate clusters, current GitHub handoff, and Gitcrawl repo work.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Java Logging Best Practices

Constraints

When to use this skill

Workflow

Reference

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now