143-java-functional-exception-handling

Use when you need to apply functional exception handling best practices in Java — including replacing exception overuse with Optional and VAVR Either types, designing error type hierarchies using sealed classes and enums, implementing monadic error composition pipelines, establishing functional control flow patterns, and reserving exceptions only for truly exceptional system-level failures. This should trigger for requests such as Improve the code with Functional Exception Handling; Apply Functional Exception Handling; Refactor the code with Functional Exception Handling; Model Java errors with Result or Either types; Replace exception-heavy flows with functional error handling. Part of Plinth Toolkit

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

70%

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

Well-structured content with a clear, validated workflow and good progressive disclosure to a single reference file. The main weaknesses are duplicated trigger/constraint text and the absence of any inline code examples for the core refactoring patterns.

Suggestions

Remove the 'When to use this skill' list since it duplicates the description triggers, or replace it with a one-line pointer back to the description.

Add one short inline code example (e.g., an Optional or VAVR Either good/bad snippet) so the SKILL.md is actionable without forcing a reference read for the most common pattern.

Consolidate the validate/dependency/verify guidance so it appears once (Constraints) and the Workflow references it, rather than restating it in both sections.

Dimension	Reasoning	Score
Conciseness	The body is lean and avoids explaining concepts Claude already knows, but the 'When to use this skill' section duplicates the description's trigger phrases and the Constraints and Workflow sections repeat the same validate/dependency/verify points, so it could be tightened.	2 / 3
Actionability	Provides concrete executable commands ('./mvnw validate or mvn validate', './mvnw clean verify') and a specific reference path, but the actual refactoring code patterns (Optional/Either usage) are deferred entirely to the reference rather than shown inline, leaving the core guidance incomplete at the SKILL.md level.	2 / 3
Workflow Clarity	A clear 5-step sequence with explicit validation checkpoints ('stop immediately if validation fails') and a verify step after changes, matching the level-3 anchor of clear sequence with feedback loops for error recovery.	3 / 3
Progressive Disclosure	The SKILL.md is an organized overview pointing to a single one-level-deep reference (references/143-java-functional-exception-handling.md, verified present) via a clearly signaled markdown link, with content appropriately split.	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 description with explicit what/when structure, natural trigger terms, and a distinct niche. The only notable issue is second-person voice ('you need'), which costs a specificity point per the voice guideline.

Suggestions

Rephrase the opening to third person (e.g., 'Use when applying functional exception handling best practices in Java...') to avoid the second-person 'you need' construction.

Consider trimming the long mid-sentence capability list into a tighter clause to improve token efficiency without losing the concrete actions.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ('replacing exception overuse with Optional and VAVR Either types, designing error type hierarchies using sealed classes and enums, implementing monadic error composition pipelines'), but the description opens with second-person voice ('Use when you need to apply...'), which per the judging guidelines reduces specificity by 1.	2 / 3
Completeness	Explicitly answers both what ('apply functional exception handling best practices in Java...') and when via an explicit 'Use when...' clause and 'This should trigger for requests such as...' listing, matching the level-3 anchor.	3 / 3
Trigger Term Quality	Includes five natural phrases a user would say ('Improve the code with Functional Exception Handling', 'Apply Functional Exception Handling', 'Refactor the code with Functional Exception Handling', 'Model Java errors with Result or Either types', 'Replace exception-heavy flows with functional error handling'), giving good coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	Occupies a clear niche (functional exception handling in Java) with distinct triggers and 'Part of Plinth Toolkit' context, making it unlikely to fire for unrelated skills.	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.