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; Review SLF4J structured logging in Java code. Part of Plinth Toolkit

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

85%

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

A well-structured, lean overview with strong workflow clarity and clean one-level-deep progressive disclosure. The body's own actionability is limited because the concrete logging-pattern guidance lives entirely in the reference.

Suggestions

Add a couple of inline copy-paste-ready logging examples (e.g. parameterized logging and a logback.xml snippet) so the body is actionable without opening the reference.

Tighten the overlap between the one-line intro and the 'What is covered' bullet list to reduce redundancy.

Optionally fold the 'When to use this skill' list back into the description to avoid duplicating the trigger terms already in the frontmatter.

Dimension	Reasoning	Score
Conciseness	The body is lean, delegates detail to the reference, and does not re-explain concepts Claude already knows; the only minor slack is overlap between the intro line and the 'What is covered' bullets, which is not enough to drop below the lean/efficient anchor.	3 / 3
Actionability	Concrete build commands are present ('./mvnw compile', 'mvn clean verify') and the reference is clearly pointed to, but the core implementation guidance is abstract ('Implement selected framework/configuration/practice changes, including secure logging and monitoring integration where applicable') and deferred to the reference, leaving key details out of the body itself.	2 / 3
Workflow Clarity	A clear 4-step sequence (compile, read reference, apply, verify) with explicit validation checkpoints and a feedback loop ('stop immediately if compilation fails', 'Run ./mvnw clean verify after applying improvements'), matching the anchor for clear sequence with explicit validation and error-recovery.	3 / 3
Progressive Disclosure	SKILL.md is a concise overview pointing to a single, real, well-organized one-level-deep reference (references/181-java-observability-logging.md, verified to exist with examples, constraints, and safeguards), clearly signaled via the Reference section and workflow step 2.	3 / 3
	Total	11 / 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, comprehensive description with explicit capabilities and natural trigger phrases. The only issue is the second-person 'Use when you need to' opening, which the rubric penalizes on specificity.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ('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'), which would anchor at 3, but the opening 'Use when you need to...' uses second person, which the rubric penalizes by reducing specificity by 1.	2 / 3
Completeness	Clearly answers both what (the enumerated logging/observability capabilities) and when ('Use when you need to implement or improve Java logging and observability' plus an explicit trigger list), matching the anchor for explicit what-and-when.	3 / 3
Trigger Term Quality	Natural user phrases are well covered ('Improve logging; Apply logging; Refactor logging; Add logging support; Review SLF4J structured logging in Java code'), matching the anchor for good coverage of terms users would actually say.	3 / 3
Distinctiveness Conflict Risk	The Java/SLF4J-specific scope and Java-tied triggers create a clear niche unlikely to conflict with non-Java skills, matching the anchor for a distinct niche with distinct triggers.	3 / 3
	Total	11 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: jabrena/plinth
Commit: aaee915

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.