180-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, secure logging without sensitive data exposure, environment-specific configuration, log aggregation and monitoring, or validating logging through tests. Part of the skills-for-java project
77
71%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/180-java-observability-logging/SKILL.mdQuality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description that clearly defines its scope (Java logging and observability), lists specific concrete capabilities, and opens with an explicit 'Use when' trigger clause. The inclusion of specific framework names, log level enumerations, and distinct practices like parameterized logging and secure logging makes it both highly searchable and clearly distinguishable from other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: selecting SLF4J with Logback/Log4j2, applying proper log levels (with specific levels enumerated), parameterized logging, secure logging without sensitive data exposure, environment-specific configuration, log aggregation and monitoring, and validating logging through tests. | 3 / 3 |
Completeness | Clearly answers both 'what' (implement/improve Java logging and observability with specific techniques listed) and 'when' (opens with 'Use when you need to implement or improve Java logging and observability' followed by explicit trigger scenarios). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'logging', 'observability', 'SLF4J', 'Logback', 'Log4j2', 'log levels', 'ERROR', 'WARN', 'INFO', 'DEBUG', 'TRACE', 'sensitive data', 'log aggregation', 'monitoring'. These cover both general and specific terms a Java developer would use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — narrowly scoped to Java logging and observability specifically, with named frameworks (SLF4J, Logback, Log4j2) and specific practices. Unlikely to conflict with general Java skills or other language logging skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill has good structure and appropriate progressive disclosure with a clear reference link, and the compilation/verification constraints are a useful safety measure. However, the body lacks any concrete code examples or actionable logging patterns — it reads as a table of contents rather than a skill that teaches Claude how to do something. The actionable content is entirely deferred to the reference file, making the skill body itself minimally useful.
Suggestions
Add at least 2-3 concrete, executable code examples directly in the skill body showing key patterns (e.g., parameterized logging with SLF4J, proper exception logging, sensitive data masking) so Claude has immediately actionable guidance without needing to read the reference.
Include a brief workflow for applying logging improvements: e.g., 1) identify current logging framework, 2) check for anti-patterns (string concatenation, sensitive data), 3) apply fixes, 4) validate — with specific validation criteria.
Remove or significantly condense the 'What is covered' bullet list, which mostly restates the reference's table of contents without adding actionable value.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The bullet-point summary of what's covered is somewhat redundant with the description and the reference file. The 'What is covered' section reads like a table of contents for the reference rather than actionable content. However, it's not excessively verbose. | 2 / 3 |
Actionability | There are no concrete code examples, no executable commands beyond compile/verify, and no specific logging patterns shown. Everything actionable is deferred to the reference file. The skill body describes rather than instructs. | 1 / 3 |
Workflow Clarity | The constraints section provides a clear sequence (compile → apply → verify) with a blocking condition on compilation failure, which is good. However, the actual workflow for applying logging improvements is absent — it just says 'read the reference,' with no validation checkpoints for the logging changes themselves. | 2 / 3 |
Progressive Disclosure | The skill provides a clear overview and appropriately delegates detailed content to a single, well-signaled reference file. The navigation is one level deep and clearly indicated. | 3 / 3 |
Total | 8 / 12 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- jabrena/cursor-rules-java
- Commit
9ec21dd
- 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.