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, 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

70

Quality

85%

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.

This skill has strong workflow clarity with explicit validation checkpoints and good progressive disclosure structure pointing to a single detailed reference. Its main weaknesses are moderate verbosity (repeating trigger phrases and listing topics covered without adding actionable value) and limited actionability in the SKILL.md itself, since all concrete logging examples are deferred to the reference file.

Suggestions

Remove the 'What is covered in this Skill?' bullet list and 'When to use this skill' section, as these duplicate the frontmatter description and triggers without adding actionable value.

Add at least one concrete, executable logging code example (e.g., SLF4J parameterized logging pattern) directly in the SKILL.md so Claude has an immediate actionable reference without needing to read the full reference file.

DimensionReasoningScore

Conciseness

The skill includes some unnecessary explanation like the 'What is covered' bullet list that largely restates the description and the reference content. The 'When to use this skill' section repeats frontmatter trigger phrases. However, the workflow and constraints sections are reasonably tight.

2 / 3

Actionability

The skill provides concrete commands (./mvnw compile, ./mvnw clean verify) and a clear workflow, but lacks any executable code examples for the actual logging patterns. All substantive guidance is deferred to the reference file, so the SKILL.md itself doesn't give Claude copy-paste-ready logging code.

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.md serves as a clear overview with a single, well-signaled reference to the detailed guide (references/181-java-observability-logging.md). Navigation is one level deep and clearly indicated. The content is appropriately split between overview and detailed reference.

3 / 3

Total

10

/

12

Passed

Description

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, includes natural trigger terms users would use, and explicitly states when it should be activated. The only minor note is the trailing 'Part of cursor-rules-java project' which adds context but is not critical for skill selection.

DimensionReasoningScore

Specificity

The description 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 with specific techniques) and 'when' ('Use when you need to implement or improve Java logging and observability' plus explicit trigger examples like 'Improve logging', 'Apply logging', etc.).

3 / 3

Trigger Term Quality

Includes strong natural trigger terms 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 — scoped specifically to Java logging and observability with named frameworks (SLF4J, Logback, Log4j2). Unlikely to conflict with general Java skills or non-logging observability skills due to the specific technology stack and domain focus.

3 / 3

Total

12

/

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.