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. This should trigger for requests such as Improve logging; Apply logging; Refactor logging; Add logging support. Part of cursor-rules-java project
88
85%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Quality
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 provides explicit trigger guidance with example phrases. The only minor note is the use of second person 'you need to' at the start, though this is borderline since it's describing when Claude should use the skill rather than addressing the user directly. Overall it follows best practices closely.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: selecting SLF4J with Logback/Log4j2, applying proper log levels, 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 with specific techniques) and 'when' with explicit trigger guidance ('Use when you need to implement or improve Java logging...', 'This should trigger for requests such as Improve logging; Apply logging; Refactor logging; Add logging support'). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'logging', 'observability', 'SLF4J', 'Logback', 'Log4j2', 'log levels', 'ERROR/WARN/INFO/DEBUG/TRACE', plus explicit trigger phrases like 'Improve logging', 'Add logging support', 'Refactor logging'. These cover common variations well. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — narrowly scoped to Java logging and observability with specific frameworks (SLF4J, Logback, Log4j2) and practices. Unlikely to conflict with other skills unless there's another Java logging skill. The 'Part of cursor-rules-java project' further narrows context. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
70%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill has a solid workflow with explicit validation checkpoints and good progressive disclosure to a reference file. However, it lacks any inline code examples for the actual logging patterns it describes, making it more of an orchestration document than a self-contained skill. The body also contains some redundancy between the introduction, the 'What is covered' section, and the 'When to use this skill' section.
Suggestions
Add at least one concrete, executable Java code example showing a recommended logging pattern (e.g., parameterized SLF4J logging with proper exception handling) so the skill is actionable without requiring the reference file.
Remove the 'When to use this skill' section since these trigger phrases belong in frontmatter metadata, not the body content, saving tokens.
Consolidate the opening paragraph and the 'What is covered' bullet list into a single concise section to reduce redundancy.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The 'What is covered' section largely restates the opening sentence and the description. The bullet list of topics is somewhat useful for navigation but adds redundancy. The 'When to use this skill' section repeats trigger phrases that belong in frontmatter, not the body. | 2 / 3 |
Actionability | The skill provides concrete commands (./mvnw compile, ./mvnw clean verify) and a clear workflow, but contains no executable code examples for actual logging implementation. All concrete guidance is deferred to the reference file, making the SKILL.md itself more of a pointer than an actionable guide. | 2 / 3 |
Workflow Clarity | The workflow is clearly sequenced with explicit validation checkpoints: compile before changes (with a stop condition on failure), read reference, apply changes, then verify with full build. The feedback loop for compilation failure is explicitly stated as a blocking condition. | 3 / 3 |
Progressive Disclosure | The skill provides a clear overview and defers detailed examples and patterns to a single, well-signaled reference file (references/180-java-observability-logging.md). Navigation is one level deep and clearly indicated. For a skill that delegates detail to a reference, this is well-structured. | 3 / 3 |
Total | 10 / 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
762cb86
- 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.