CtrlK
BlogDocsLog inGet started
Tessl Logo

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

88

Quality

85%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

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 an excellent skill description that follows best practices. It uses third person voice, starts with an explicit 'Use when' clause, lists comprehensive specific capabilities, and includes natural trigger terms that Java developers would use. The description is distinctive enough to avoid conflicts with other skills while being comprehensive about its scope.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: selecting SLF4J with Logback/Log4j2, applying proper log levels (with specific examples), parameterized logging, secure logging, environment-specific configuration, log aggregation and monitoring, and validating through tests.

3 / 3

Completeness

Clearly answers both what (implement/improve Java logging with specific techniques) AND when (explicit 'Use when' clause at the start listing multiple trigger scenarios). The 'Use when' is comprehensive and explicit.

3 / 3

Trigger Term Quality

Excellent coverage of natural terms users would say: 'logging', 'observability', 'SLF4J', 'Logback', 'Log4j2', 'log levels', 'ERROR', 'WARN', 'INFO', 'DEBUG', 'TRACE', 'sensitive data', 'log aggregation', 'monitoring'. These are terms Java developers naturally use.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive with clear niche: Java-specific logging and observability. The specific framework names (SLF4J, Logback, Log4j2) and Java-specific terminology make it unlikely to conflict with general logging skills or other language-specific skills.

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.

This skill demonstrates good workflow structure with clear validation checkpoints and appropriate progressive disclosure to a reference file. However, it lacks concrete code examples in the main skill file, relying entirely on the reference for actionable logging patterns. The content could be more concise by trimming the explanatory bullet lists.

Suggestions

Add at least one concrete, executable logging code example (good vs bad pattern) directly in the skill file to improve actionability

Condense the 'What is covered' bullet lists into a more concise summary, as the detailed breakdown is available in the reference file

DimensionReasoningScore

Conciseness

The skill is reasonably efficient but includes some unnecessary explanation in the 'What is covered' section that could be trimmed. The bullet lists are informative but slightly verbose for what could be a more direct pointer to the reference.

2 / 3

Actionability

Provides concrete Maven commands for compilation and verification, but lacks any executable code examples for the actual logging patterns. The skill relies entirely on the reference file for concrete implementation guidance.

2 / 3

Workflow Clarity

Clear workflow with explicit validation checkpoints: compile before changes, stop on failure, verify after changes. The MANDATORY/SAFETY/VERIFY structure provides explicit feedback loops for error recovery.

3 / 3

Progressive Disclosure

Excellent structure with a clear overview and single-level reference to the detailed guidance file. The skill appropriately keeps high-level context in SKILL.md while pointing to comprehensive examples in the reference.

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.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
jabrena/cursor-rules-java
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.