CtrlK
BlogDocsLog inGet started
Tessl Logo

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

71

Quality

63%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/123-java-exception-handling/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

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 skill description with excellent specificity and completeness. It clearly defines the scope with an explicit 'Use when' clause and lists numerous concrete actions. The main weakness is that trigger terms lean heavily on technical jargon rather than natural language users might employ when seeking help.

Suggestions

Add natural language trigger terms users might say, such as 'error handling', 'catch exceptions', 'handle errors in Java', or 'try-catch blocks'

DimensionReasoningScore

Specificity

Lists multiple 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', and several more.

3 / 3

Completeness

Clearly answers both what (comprehensive list of exception handling practices) and when ('Use when you need to apply Java exception handling best practices') with an explicit 'Use when' clause at the beginning.

3 / 3

Trigger Term Quality

Contains relevant technical terms like 'exception handling', 'try-with-resources', 'exception chaining', '@throws', but these are more technical jargon than natural user language. Missing common variations users might say like 'error handling', 'catch blocks', 'throw errors', or 'handle errors'.

2 / 3

Distinctiveness Conflict Risk

Highly specific to Java exception handling with distinct triggers like 'try-with-resources', 'exception chaining', '@throws', 'thread interruption'. Unlikely to conflict with other skills due to the narrow, well-defined domain.

3 / 3

Total

11

/

12

Passed

Implementation

42%

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

The skill has good structure and appropriate progressive disclosure with clear reference to detailed documentation. However, it lacks actionability - there are no concrete code examples in the main skill body, making it essentially a table of contents rather than actionable guidance. The workflow for compilation/verification is present but the core exception handling guidance is entirely deferred.

Suggestions

Add at least 2-3 concrete, executable code examples showing good vs bad patterns for the most common scenarios (e.g., try-with-resources, exception chaining)

Include a quick-reference code snippet for the most critical pattern (e.g., proper InterruptedException handling) that Claude can immediately apply

Add error recovery guidance in the Constraints section for what to do when compilation fails (e.g., 'review error messages, check for missing dependencies')

DimensionReasoningScore

Conciseness

The skill lists many topics covered but some bullet points are somewhat verbose (e.g., 'Specific exception types instead of generic Exception/RuntimeException'). The overview section could be tighter, though it avoids explaining basic concepts Claude already knows.

2 / 3

Actionability

The skill provides no concrete code examples, commands, or executable guidance in the body itself. It only lists topics and defers entirely to a reference file for actual implementation details and examples.

1 / 3

Workflow Clarity

The Constraints section provides a clear sequence (compile -> apply changes -> verify) with explicit validation checkpoints, but lacks error recovery guidance beyond 'stop immediately'. The main content has no workflow for applying the exception handling patterns themselves.

2 / 3

Progressive Disclosure

Clear overview structure with a single, well-signaled reference file for detailed examples. The skill appropriately keeps the main file as an overview and delegates detailed patterns to one reference document.

3 / 3

Total

8

/

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.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
jabrena/cursor-rules-java
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.