181-java-observability-logging — Claude Code skill for Java logs
181-java-observability-logging is a Claude Code skill for improving Java logging and observability. It activates on requests to add, review, or refactor logging.
Apache-2.0 325 installs ★ 465 updated 2026-10-21
npx skills add jabrena/plinth --skill 181-java-observability-logging -a claude-codeWhat 181-java-observability-logging does
The skill assesses a Java project's logging setup and guides changes to framework choice, log levels, parameterized messages, and correlation context. Its scope also covers masking sensitive values, environment-specific configuration, log aggregation, monitoring, and alerts.
Before changing code, the agent runs ./mvnw compile or mvn compile and stops if compilation fails. It then reads references/181-java-observability-logging.md, which contains good and bad code examples, applies relevant changes, and runs ./mvnw clean verify or mvn clean verify. The project needs Maven or the Maven Wrapper.
What it helps with
- choose between SLF4J with Logback and Log4j2
- assign suitable ERROR, WARN, INFO, DEBUG, and TRACE levels
- add correlation context and parameterized messages
- mask sensitive values in log output
- configure logging across environments and connect monitoring
Example prompts for the agent
- Improve logging in this Java project and verify the build.
- Review the log levels and remove sensitive values from log output.
- Add correlation context and set up log monitoring.
How to install 181-java-observability-logging
1Skills CLI (Vercel)
npx skills add jabrena/plinth --skill 181-java-observability-logging -a claude-code2Manually: put the files in place
~/.claude/skills/181-java-observability-logging/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/181-java-observability-logging/
1Skills CLI (Vercel)
npx skills add jabrena/plinth --skill 181-java-observability-logging -a codex2Manually: put the files in place
.agents/skills/181-java-observability-logging/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add jabrena/plinth --skill 181-java-observability-logging -a cursor2Manually: put the files in place
.cursor/skills/181-java-observability-logging/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install jabrena/plinth skills/181-java-observability-logging2Manually: put the files in place
.github/skills/181-java-observability-logging/SKILL.md1Skills CLI (Vercel)
npx skills add jabrena/plinth --skill 181-java-observability-logging -a gemini-cli2Platform CLI
gemini skills install https://github.com/jabrena/plinth --path skills/181-java-observability-loggingManually: put the files in place
.devin/skills/181-java-observability-logging/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add jabrena/plinth --skill 181-java-observability-logging -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about 181-java-observability-logging
How do I install 181-java-observability-logging in Claude Code?
Run npx skills add jabrena/plinth --skill 181-java-observability-logging -a claude-code. The skill file is at ~/.claude/skills/181-java-observability-logging/SKILL.md.
What does 181-java-observability-logging do?
It guides changes to Java logging frameworks, levels, sensitive-data handling, environment-specific configuration, and monitoring.
What does 181-java-observability-logging need to run?
The project must support Maven through ./mvnw or mvn. The skill compiles before making changes and runs full verification afterward.
Source text
SKILL.md · Apache-2.0
--- name: 181-java-observability-logging description: 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 license: Apache-2.0 metadata: author: Juan Antonio Breña Moral version: 0.19.0 --- # 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 1. **Compile project before logging changes** Run `./mvnw compile` or `mvn compile` and stop immediately if compilation fails. 2. **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. 3. **Apply logging and observability improvements** Implement selected framework/configuration/practice changes, including secure logging and monitoring integration where applicable. 4. **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](references/181-java-observability-logging.md).
© Juan Antonio Breña Moral · Apache-2.0 · jabrena/plinth