mapper-creator

Creates a mapper between an entity and a DTO (MapStruct or custom converter). Use this skill when a mapper/converter between entity and DTO needs to be created, either standalone or as part of a larger task (e.g. after DTO creation, during CRUD setup).

1.26x

Quality

75%

Does it follow best practices?

Impact

71%

1.26x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/mapper-creator/SKILL.md

Quality

Content

67%Weight 40%Scale 1-5

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

A thorough, well-sequenced interactive workflow with strong actionability and a real reference bundle used appropriately. Its main weaknesses are repetition of the don't-re-ask philosophy and references to examples/ paths that do not exist in the provided bundle.

Suggestions

Consolidate the repeated 'never re-ask what the user already said' guidance (Defaults, Step 0, smart-answer-recognition, Decision-making principle) into a single canonical statement to reduce token overhead.

Reconcile Step 4's generation source: either add the examples/_skeletons and examples/_fragments files to the bundle or rewrite Step 4 to source all generation from the existing references/*.md files so Claude does not read non-existent paths.

Add a short post-write verification step (e.g. re-read the produced mapper/build file and confirm imports/annotations against the Anti-hallucination checklist) to give the workflow an explicit feedback loop.

Dimension	Reasoning	Score
Conciseness	The body is mostly procedural and concrete, but the "never re-ask what the user already said" guidance is restated in the Defaults section, Step 0, the smart-answer-recognition block, and the Decision-making principle, which is padded repetition that could be consolidated.	3 / 5
Actionability	It gives concrete MCP tool calls with named variables, exact build-file edit strategies per file type, and explicit variable-substitution/FQN rules, but Step 4 directs Claude to read examples/_skeletons and examples/_fragments paths that are not present in the bundle, a small execution gap.	4 / 5
Workflow Clarity	Steps 0-5 are clearly sequenced with a pre-write Anti-hallucination checklist as an explicit validation checkpoint, but there is no post-write validate/feedback loop for the file-writing and build-editing operations, leaving a minor checkpoint gap.	4 / 5
Progressive Disclosure	The overview correctly signals one-level-deep references to the real references/*.md files (mapstruct-java.md, mapping-annotations.md, method-naming.md, etc.), but references to a non-existent examples/ directory (skeletons/fragments) create a minor navigation gap.	4 / 5
	Total	15 / 20 Passed

Description

82%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A tight, third-person description that cleanly answers both what and when with concrete trigger contexts and a distinct niche. Its only weakness is specificity: it names one action (create a mapper) with two variants rather than enumerating several concrete operations.

Dimension	Reasoning	Score
Specificity	"Creates a mapper between an entity and a DTO (MapStruct or custom converter)" names the domain and one concrete action with two implementation variants, but does not list several distinct actions, matching the 1-2 concrete actions anchor rather than the comprehensive 4-5 anchors.	3 / 5
Completeness	It explicitly states what ("Creates a mapper between an entity and a DTO (MapStruct or custom converter)") and when with concrete trigger phrases ("Use this skill when a mapper/converter between entity and DTO needs to be created... after DTO creation, during CRUD setup"), matching the anchor 5 example.	5 / 5
Trigger Term Quality	Natural terms users would say are well covered — "mapper", "converter", "entity", "DTO", "MapStruct", "CRUD", "after DTO creation" — with the synonym pair mapper/converter, falling just short of anchor 5 which expects comprehensive synonyms/extensions.	4 / 5
Distinctiveness Conflict Risk	The entity↔DTO mapping niche with MapStruct/custom-converter triggers is clearly distinct from sibling skills (e.g. dto-creator) and unlikely to fire for unrelated tasks, matching the clear-niche/minimal-conflict anchor.	5 / 5
	Total	17 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: Amplicode/spring-skills
Path: skills/mapper-creator/SKILL.md
Commit: bf19b3c

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.