123-java-exception-handling
Use when you need to apply Java exception handling best practices — including using specific exception types, managing resources with try-with-resources, securing exception messages, preserving error context via exception chaining, validating inputs early with fail-fast principles, handling thread interruption correctly, documenting exceptions with @throws, enforcing logging policy, translating exceptions at API boundaries, managing retries and idempotency, enforcing timeouts, attaching suppressed exceptions, and propagating failures in async/reactive code. Part of the skills-for-java project
88
85%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
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 comprehensively lists specific Java exception handling practices, includes a clear 'Use when' trigger clause, and uses natural developer terminology. The description is highly specific to its domain, making it easily distinguishable from other skills. The only minor weakness is that the sheer length and density of the list could be slightly overwhelming, but it serves the purpose of skill selection well.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description lists numerous specific concrete actions: using specific exception types, managing resources with try-with-resources, securing exception messages, preserving error context via exception chaining, validating inputs early, handling thread interruption, documenting exceptions with @throws, enforcing logging policy, translating exceptions at API boundaries, managing retries and idempotency, enforcing timeouts, attaching suppressed exceptions, and propagating failures in async/reactive code. | 3 / 3 |
Completeness | The description explicitly answers both 'what' (apply Java exception handling best practices with a comprehensive list of specific practices) and 'when' (opens with 'Use when you need to apply Java exception handling best practices'), providing clear trigger guidance. | 3 / 3 |
Trigger Term Quality | The description includes many natural keywords a Java developer would use: 'exception handling', 'try-with-resources', 'exception chaining', 'fail-fast', 'thread interruption', '@throws', 'logging policy', 'API boundaries', 'retries', 'idempotency', 'timeouts', 'suppressed exceptions', 'async/reactive'. These are terms developers naturally use when seeking help with Java exception handling. | 3 / 3 |
Distinctiveness Conflict Risk | The description is highly specific to Java exception handling best practices, a clear niche that is unlikely to conflict with other skills. The combination of Java-specific terminology and exception handling focus makes it distinctly identifiable. | 3 / 3 |
Total | 12 / 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.
This skill is well-organized with clear progressive disclosure and a solid workflow with validation checkpoints. Its main weakness is the lack of any concrete code examples in the skill body itself — all patterns are deferred to the reference file, which reduces immediate actionability. The bullet-point summary of topics covered is moderately useful but adds length without adding executable guidance.
Suggestions
Include at least 1-2 concrete before/after code examples of the most common patterns (e.g., try-with-resources, exception chaining) directly in the skill body so Claude has immediately actionable guidance without needing to read the reference.
Trim the 'What is covered' bullet list to the top 5-6 most important items, or remove it entirely since the reference file presumably covers the full scope.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The 'What is covered' bullet list is essentially a table of contents that adds moderate value but is somewhat verbose. The skill could be tighter by removing the introductory summary and going straight to constraints and reference. However, it doesn't over-explain concepts Claude already knows. | 2 / 3 |
Actionability | The skill provides concrete commands (`./mvnw compile`, `mvn clean verify`) for verification, but contains zero code examples of actual exception handling patterns. All concrete guidance is deferred to the reference file, making the skill itself more of a pointer than an actionable guide. | 2 / 3 |
Workflow Clarity | The constraints section provides a clear sequence: compile first, stop if it fails, apply changes, then verify. The explicit 'stop immediately' checkpoint for compilation failure is a good feedback loop for a potentially destructive refactoring operation. | 3 / 3 |
Progressive Disclosure | The skill is well-structured as a concise overview with a single, clearly signaled one-level-deep reference to the detailed guide. Content is appropriately split between the overview and the reference file. | 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
9ec21dd
- 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.