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. Part of cursor-rules-java project
82
77%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/143-java-functional-exception-handling/SKILL.mdQuality
Discovery
85%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 description that clearly articulates specific capabilities and provides explicit trigger guidance. Its main weakness is that the trigger terms are somewhat narrow and formulaic, potentially missing users who describe the need in different ways (e.g., 'avoid exceptions', 'use Result types', 'functional error handling'). The description is well-structured and distinctive enough to avoid conflicts with other skills.
Suggestions
Broaden trigger term coverage by adding natural user phrases like 'avoid try-catch', 'error handling without exceptions', 'Result type pattern', or 'functional error handling in Java' to capture more query variations.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific 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, establishing functional control flow patterns, and reserving exceptions for system-level failures. | 3 / 3 |
Completeness | Clearly answers both 'what' (applying functional exception handling best practices including Optional, VAVR Either, sealed classes, monadic composition, etc.) and 'when' (explicit 'Use when' clause at the start plus explicit trigger phrases like 'Apply Functional Exception Handling'). | 3 / 3 |
Trigger Term Quality | Includes some natural trigger terms like 'Functional Exception Handling', 'Optional', 'VAVR Either', 'sealed classes', but the trigger phrases listed are somewhat formulaic ('Apply Functional Exception Handling', 'Refactor the code with Functional Exception Handling') and miss common variations users might say like 'error handling in Java', 'avoid try-catch', 'monadic error handling', or 'result type pattern'. | 2 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche focusing specifically on functional exception handling in Java with specific technologies (VAVR Either, Optional, sealed classes). Unlikely to conflict with general Java skills or generic error handling skills due to the functional programming focus and specific tooling mentioned. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
70%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill has strong workflow structure with proper validation checkpoints and good progressive disclosure to a reference file. Its main weakness is the lack of any inline code examples — the body describes patterns conceptually but defers all executable guidance to the reference, reducing immediate actionability. There is also moderate redundancy across sections (dependency checks mentioned multiple times, trigger phrases restating metadata).
Suggestions
Add at least one or two concise, executable Java code examples inline (e.g., a before/after showing exception-based code refactored to Either or Optional) to improve actionability without requiring the reader to open the reference file.
Remove the 'When to use this skill' section since it duplicates YAML frontmatter trigger information, and consolidate the repeated VAVR dependency mention to appear only once (in the workflow step where it's actionable).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The 'What is covered' bullet list and the constraints section have some redundancy (e.g., VAVR dependency check is mentioned three times across sections). The introductory sentence and trigger phrases section restate what the YAML frontmatter already conveys. However, it's not egregiously verbose — mostly efficient with some tightening possible. | 2 / 3 |
Actionability | The skill provides concrete commands (mvnw validate, mvn clean verify) and references a detailed guide, but the SKILL.md itself contains zero code examples — no executable Java snippets showing Optional, Either, or any pattern. All actionable code is deferred to the reference file, making the skill body itself more descriptive than instructive. | 2 / 3 |
Workflow Clarity | The workflow is clearly sequenced with 5 numbered steps, includes explicit validation checkpoints (validate before, verify after), has a stop condition if validation fails, and includes a dependency check step before implementation. This covers feedback loops for a potentially destructive refactoring operation. | 3 / 3 |
Progressive Disclosure | The skill provides a clear overview with well-organized sections and a single, clearly signaled reference to the detailed guide (references/143-java-functional-exception-handling.md). Navigation is one level deep and the split between overview and detailed content is appropriate. | 3 / 3 |
Total | 10 / 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- jabrena/cursor-rules-java
- Commit
762cb86
- 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.