CtrlK
BlogDocsLog inGet started
Tessl Logo

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).

82

1.26x
Quality

Does it follow best practices?

Impact

71%

1.26x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

62%

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

The skill has a clear, well-sequenced workflow with a strong pre-write validation checklist and good use of real reference files. Its main weaknesses are repeated context-first guidance that inflates tokens and a missing `examples/` directory that the code-generation step depends on.

Suggestions

Consolidate the "context first, then ask" rule into one place (the Decision-making principle section) and have Step 0 and Steps 2–3 reference it, instead of restating the rule three times.

Add the missing `examples/_skeletons/` and `examples/_fragments/` files referenced in Step 4, or redirect generation at the existing `references/` files, so the code-generation step is fully actionable.

Add a post-generation verification step (confirm emitted imports are valid and the build-file edit parses) to create a feedback loop after the destructive build-file edit and hand-managed import emission.

DimensionReasoningScore

Conciseness

The body is procedurally dense and avoids explaining concepts Claude already knows, but the "context first, then ask" rule is restated across Step 0, the Decision-making principle section, and again inside Steps 2–3, so it could be tightened.

2 / 3

Actionability

Guidance is largely concrete (exact MCP tools, variable substitution rules, per-build-file edit strategies), but Step 4 instructs reading skeletons/fragments from `examples/_skeletons/` and `examples/_fragments/` — a directory that does not exist in the bundle — leaving the core code-generation step incomplete.

2 / 3

Workflow Clarity

Steps 0–5 are clearly sequenced and the Anti-hallucination checklist provides an explicit pre-write validation checkpoint for a complex multi-step process.

3 / 3

Progressive Disclosure

The six `references/*.md` files are real, one level deep, and well signaled, but the `examples/` skeleton/fragment paths referenced in Step 4 are missing entirely, so navigation to a referenced path breaks.

2 / 3

Total

9

/

12

Passed

Description

100%

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

The description is concise, concrete, and complete: it states exactly what the skill does, names the two supported approaches, and gives an explicit "Use when" trigger with realistic invocation contexts. It is distinct from sibling skills and free of fluff.

DimensionReasoningScore

Specificity

"Creates a mapper between an entity and a DTO (MapStruct or custom converter)" names a concrete action with two specific named approaches rather than vague language.

3 / 3

Completeness

It states what ("Creates a mapper between an entity and a DTO") and explicitly when ("Use this skill when a mapper/converter... needs to be created, either standalone or as part of a larger task"), satisfying both requirements with an explicit trigger.

3 / 3

Trigger Term Quality

Natural developer terms are well covered — "mapper", "converter", "entity and DTO", "DTO creation", "CRUD setup" — matching phrases a user would actually say.

3 / 3

Distinctiveness Conflict Risk

The entity-to-DTO mapping niche with MapStruct/custom variants is specific and unlikely to trigger for unrelated skills.

3 / 3

Total

12

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
Amplicode/spring-skills
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.