unit-test-exception-handler
Unit tests for @ExceptionHandler and @ControllerAdvice for global exception handling. Use when validating error response formatting and HTTP status codes.
Install with Tessl CLI
npx tessl i github:giuseppe-trisciuoglio/developer-kit --skill unit-test-exception-handler73
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
75%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 reasonably well-crafted description that clearly identifies its niche in Spring exception handling testing and includes explicit trigger guidance. The main weaknesses are moderate specificity in concrete actions and limited coverage of natural trigger term variations that users might employ when seeking this skill.
Suggestions
Add more concrete testing actions like 'mock exceptions, verify response bodies, test exception propagation across controllers'
Expand trigger terms to include variations like 'error handling tests', 'REST error responses', 'Spring MVC exceptions', or 'exception mapper testing'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Spring exception handling with @ExceptionHandler and @ControllerAdvice) and mentions specific actions (validating error response formatting and HTTP status codes), but doesn't list multiple concrete testing actions like 'mock exceptions', 'verify response bodies', or 'test exception propagation'. | 2 / 3 |
Completeness | Clearly answers both what (unit tests for @ExceptionHandler and @ControllerAdvice for global exception handling) and when (Use when validating error response formatting and HTTP status codes) with an explicit 'Use when...' clause. | 3 / 3 |
Trigger Term Quality | Includes relevant technical terms like '@ExceptionHandler', '@ControllerAdvice', 'error response', and 'HTTP status codes' that users familiar with Spring would use, but missing common variations like 'exception handling tests', 'error handling', 'REST error responses', or 'Spring MVC exceptions'. | 2 / 3 |
Distinctiveness Conflict Risk | Very specific niche targeting Spring's exception handling annotations (@ExceptionHandler, @ControllerAdvice) which are distinct from general testing skills or other Spring testing scenarios. Unlikely to conflict with generic unit testing or other controller testing skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, actionable skill with excellent executable code examples covering multiple exception handling scenarios. The main weaknesses are verbosity (could trim setup sections and 'when to use' guidance) and lack of explicit test workflow with validation checkpoints. The content would benefit from being split into a quick-start overview with links to detailed pattern files.
Suggestions
Remove or significantly trim the 'When to Use This Skill' section - Claude can infer appropriate usage from the content itself
Add explicit workflow steps for testing exception handlers: 1) Create test controller that throws exception, 2) Configure MockMvc with handler, 3) Execute request, 4) Verify status AND response body structure
Consider splitting into SKILL.md (basic pattern + setup) and PATTERNS.md (validation errors, custom logic, multiple exception types) to improve progressive disclosure
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary sections like 'When to Use This Skill' that Claude can infer, and the Maven/Gradle setup is standard boilerplate that could be trimmed. The 'Best Practices' and 'Common Pitfalls' sections add value but could be more concise. | 2 / 3 |
Actionability | Excellent executable code examples throughout - complete test classes, exception handlers, and MockMvc setup are all copy-paste ready. Each pattern shows both the production code and corresponding test code with specific assertions. | 3 / 3 |
Workflow Clarity | The skill presents patterns clearly but lacks explicit workflow sequencing. For testing exception handlers, there's no clear 'first do X, then validate Y' structure. The troubleshooting section hints at validation but doesn't integrate it into a workflow with checkpoints. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear section headers, but it's a monolithic document (~300 lines) that could benefit from splitting advanced patterns (validation errors, custom logic) into separate files. References at the end are external links rather than internal skill documentation. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
75%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 12 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 12 / 16 Passed | |
- 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.