CtrlK
BlogDocsLog inGet started
Tessl Logo

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. Part of cursor-rules-java project

67

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

70%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured instruction skill with strong workflow validation and clean progressive disclosure to one reference file. Its main weaknesses are mild redundancy between coverage/trigger lists and vague core implementation guidance that relies entirely on the deferred reference.

Suggestions

Remove the duplicated trigger-phrase list in 'When to use this skill' (already in the description) or the overlapping 'What is covered' bullets to tighten conciseness.

Add one or two concrete inline examples in step 3 (e.g., a parameterized-logging snippet or a logback.xml level snippet) so the body is actionable without forcing a reference read for common cases.

Clarify step 3's 'Implement selected framework/configuration/practice changes' with specific sub-steps or a decision pointer into the reference rather than abstract direction.

DimensionReasoningScore

Conciseness

The body is mostly lean and avoids explaining concepts Claude already knows, but the 'What is covered' bullet list overlaps with the intro sentence and the 'When to use this skill' section repeats trigger phrases already present in the description, so it could be tightened.

2 / 3

Actionability

It provides concrete executable commands ('./mvnw compile', 'mvn clean verify') and a clear reference pointer, but the core logging guidance in step 3 ('Implement selected framework/configuration/practice changes') is vague and defers all specifics to the reference rather than giving concrete instruction.

2 / 3

Workflow Clarity

A clear 4-step sequence with explicit validation checkpoints (compile-before, verify-after) and a 'stop immediately if compilation fails' feedback loop, matching the score-3 anchor for sequenced validation with error recovery.

3 / 3

Progressive Disclosure

The body is a concise overview pointing to a single real, verified reference file (references/181-java-observability-logging.md), one level deep and clearly signaled, with well-organized sections.

3 / 3

Total

10

/

12

Passed

Description

90%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, specific description with explicit trigger guidance and a clear Java-logging niche. The only weakness is second-person voice, which costs it one specificity point per the rubric.

DimensionReasoningScore

Specificity

The description lists many concrete actions ('selecting SLF4J with Logback/Log4j2', 'parameterized logging', 'log aggregation, monitoring, and alerting'), which would merit a 3, but it uses second-person voice ('Use when you need to implement...'), which the rubric penalizes by reducing specificity by one.

2 / 3

Completeness

It explicitly answers both 'what' (detailed capability list) and 'when' via an explicit 'Use when...' clause plus 'This should trigger for requests such as...', matching the score-3 anchor.

3 / 3

Trigger Term Quality

It includes natural user phrases such as 'Improve logging; Apply logging; Refactor logging; Add logging support' alongside concrete technical terms, giving good coverage of terms users would actually say.

3 / 3

Distinctiveness Conflict Risk

It occupies a clear niche (Java logging and observability) with distinct triggers, making it unlikely to fire for unrelated skills.

3 / 3

Total

11

/

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.

Validation16 / 16 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.