unit-test-mapper-converter
Unit tests for mappers and converters (MapStruct, custom mappers). Test object transformation logic in isolation. Use when ensuring correct data transformation between DTOs and domain objects.
Install with Tessl CLI
npx tessl i github:giuseppe-trisciuoglio/developer-kit --skill unit-test-mapper-converter76
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
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 well-crafted skill description that clearly defines its scope around mapper and converter testing with specific technologies mentioned. It includes an explicit 'Use when' clause and targets a distinct niche. The main weakness is that trigger terms could be expanded to include more natural variations users might use when requesting this type of testing.
Suggestions
Add more natural trigger term variations like 'mapping tests', 'conversion tests', 'entity mapping', 'model transformation', or 'bean mapping'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists specific concrete actions: 'Unit tests for mappers and converters', names specific technologies (MapStruct, custom mappers), and describes the purpose 'Test object transformation logic in isolation'. | 3 / 3 |
Completeness | Clearly answers both what ('Unit tests for mappers and converters, test object transformation logic') and when ('Use when ensuring correct data transformation between DTOs and domain objects') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes relevant terms like 'MapStruct', 'mappers', 'converters', 'DTOs', 'domain objects', but missing common variations users might say like 'mapping tests', 'conversion tests', 'entity mapping', or 'model transformation'. | 2 / 3 |
Distinctiveness Conflict Risk | Clear niche focusing specifically on mapper/converter unit testing with distinct triggers like 'MapStruct', 'DTOs', 'domain objects' - unlikely to conflict with general unit testing or other testing skills. | 3 / 3 |
Total | 11 / 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 code examples covering MapStruct mapper testing comprehensively. The main weaknesses are verbosity (could trim setup sections and 'When to Use' content) and lack of explicit workflow guidance for systematic mapper testing. The content would benefit from being split into a quick-start overview with references 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 a brief workflow section at the top: 'Test order: 1) Basic field mapping 2) Null handling 3) Nested objects 4) Round-trip verification'
Consider moving advanced patterns (enum mapping, partial mapping, custom converters) to a separate ADVANCED_PATTERNS.md file with clear references
| 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 setup sections with Maven/Gradle dependencies add bulk that may not always be needed. Some explanatory text could be trimmed. | 2 / 3 |
Actionability | Excellent executable code examples throughout - all Java code is complete, copy-paste ready, and demonstrates real MapStruct patterns with proper imports and assertions. Each pattern shows both the mapper interface and corresponding test code. | 3 / 3 |
Workflow Clarity | The skill presents individual test patterns clearly but lacks explicit workflow guidance for how to approach mapper testing systematically. No validation checkpoints or sequence for when to run which tests. The 'Best Practices' section lists items but doesn't sequence them. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear section headers, but it's a monolithic document that could benefit from splitting advanced patterns (enum mapping, partial mapping) into separate files. References at the end are good but inline content is heavy. | 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.