tessl i github:giuseppe-trisciuoglio/developer-kit --skill unit-test-bean-validationUnit testing Jakarta Bean Validation (@Valid, @NotNull, @Min, @Max, etc.) with custom validators and constraint violations. Test validation logic without Spring context. Use when ensuring data integrity and validation rules are correct.
Validation
75%| 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 | |
Implementation
77%This is a solid, actionable skill with excellent executable code examples covering the full spectrum of Bean Validation testing scenarios. The main weakness is verbosity - it includes explanatory content Claude doesn't need and could be more concise by splitting advanced topics into separate files. The workflow is clear and the examples are immediately usable.
Suggestions
Remove or significantly trim the 'When to Use This Skill', 'Best Practices', and 'Common Pitfalls' sections - Claude knows these patterns
Consider splitting custom validators and validation groups into separate reference files (e.g., CUSTOM_VALIDATORS.md, VALIDATION_GROUPS.md) to reduce main file length
Remove explanatory comments in code that state the obvious (e.g., '// Custom constraint annotation', '// Unit test')
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with good code examples, but includes some unnecessary sections like 'When to Use This Skill' that Claude can infer, and the 'Best Practices' and 'Common Pitfalls' sections contain generic advice Claude already knows. | 2 / 3 |
Actionability | Excellent executable code examples throughout - complete test classes with imports, setup methods, and assertions. All code is copy-paste ready with proper Maven/Gradle dependencies included. | 3 / 3 |
Workflow Clarity | Clear progression from basic validation testing to custom validators to cross-field validation to validation groups. Each section builds logically, and the troubleshooting section addresses common failure points. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but the skill is quite long (300+ lines) and could benefit from splitting advanced topics (custom validators, validation groups) into separate reference files. External references are provided but only at the end. | 2 / 3 |
Total | 10 / 12 Passed |
Activation
85%This is a strong skill description that clearly defines its scope around Jakarta Bean Validation testing with specific annotations and use cases. It includes an explicit 'Use when' clause and uses appropriate third-person voice. The main weakness is that trigger terms could include more natural user language variations beyond the technical annotation names.
Suggestions
Add common user variations to trigger terms such as 'validation tests', 'input validation', 'field validation', 'JSR-380', or 'javax.validation'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Unit testing Jakarta Bean Validation' with specific annotations (@Valid, @NotNull, @Min, @Max), 'custom validators', 'constraint violations', and 'Test validation logic without Spring context'. | 3 / 3 |
Completeness | Clearly answers 'what' (unit testing Jakarta Bean Validation with custom validators and constraint violations) and 'when' with explicit trigger: 'Use when ensuring data integrity and validation rules are correct'. | 3 / 3 |
Trigger Term Quality | Includes good technical terms like '@Valid', '@NotNull', 'Bean Validation', 'constraint violations', but missing common user variations like 'validation tests', 'input validation', 'field validation', or 'JSR-380'. | 2 / 3 |
Distinctiveness Conflict Risk | Highly specific niche targeting Jakarta Bean Validation testing specifically, with distinct triggers like '@Valid', '@NotNull', 'constraint violations' that are unlikely to conflict with general testing or validation skills. | 3 / 3 |
Total | 11 / 12 Passed |
Reviewed
Table of Contents
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.