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

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

85%Weight 40%Scale 1-5

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

The content is well-structured with a clear validated workflow and good progressive disclosure via a single reference file. Slight redundancy with the description and lack of inline code examples keep conciseness and actionability at 4.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with well-organized bullets and a compact workflow, but the 'When to use' list repeats trigger phrases already present in the description and the Constraints/Workflow sections restate the validate/verify commands.	4 / 5
Actionability	Provides concrete commands ('./mvnw validate', 'mvn clean verify') and specific dependency identifiers (io.vavr:vavr, SLF4J), but delegates all code examples to the reference file rather than including executable snippets inline.	4 / 5
Workflow Clarity	A clear five-step sequence with explicit validation checkpoints and a feedback loop ('stop immediately — do not proceed until the project is in a valid state'), plus a post-change verify step.	5 / 5
Progressive Disclosure	SKILL.md is a concise overview with a single one-level-deep reference (references/143-java-functional-exception-handling.md) that is clearly signaled and linked, matching the actual bundle structure.	5 / 5
	Total	18 / 20 Passed

Description

92%Weight 40%Scale 1-5

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

The description is specific, complete, and distinct, clearly stating what the skill does and when to use it with concrete trigger phrases. The only minor gap is trigger-term synonym breadth, which keeps trigger_term_quality at 4 rather than 5.

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' — giving comprehensive coverage of capabilities.	5 / 5
Completeness	Explicitly answers both 'what' (the enumerated functional error-handling capabilities) and 'when' via a clear 'Use when...' clause with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes several natural trigger phrases users would say ('Apply Functional Exception Handling', 'Refactor the code with Functional Exception Handling', 'Replace exception-heavy flows with functional error handling'), though it lacks broader synonym variants.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (Java functional exception handling with VAVR/Either/Optional) with distinct triggers and minimal overlap risk against other skills.	5 / 5
	Total	19 / 20 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
Path: skills/143-java-functional-exception-handling/SKILL.md
Commit: 77b8825

Reviewed: about 23 hours 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.