dto-creator

Creates a DTO (Data Transfer Object) class for an entity. Use this skill when a DTO class needs to be created, either standalone or as part of a larger task (e.g. REST controller, service layer, replacing entity usage with a DTO).

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

62%

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

A richly specified, well-sequenced DTO-generation workflow with strong validation checkpoints, undermined by verbosity from repeated policy guidance and a real gap: the examples/ code templates it depends on are not bundled. Tightening the duplicated asking-rules and providing the missing example files would lift the weaker dimensions.

Suggestions

De-duplicate the AskUserQuestion / 'context first, then ask' guidance — state it once in the Decision-making principle and reference it from Steps 0–5 instead of restating the batching rules four times.

Bundle the examples/_skeletons/ and examples/_fragments/ files the skill reads from (or relocate that content into references/), since 'Code ONLY from examples/ files' is unfulfillable without them and caps actionability.

Consider moving the large per-field options and indentation sections into a reference file so the SKILL.md body stays a lean overview with one-level-deep pointers.

Dimension	Reasoning	Score
Conciseness	The body is ~510 lines with significant policy repetition — the AskUserQuestion/batching rules and 'context first, then ask' guidance are restated in the Defaults section, the Decision-making principle, Step 0, and again in 'How to ask' — so it is mostly efficient but could be tightened considerably. It does correctly avoid explaining concepts Claude already knows (no 'what is a DTO' filler).	2 / 3
Actionability	Guidance is concrete (exact MCP tool names, derived-variable tables, decision matrices, FQN/import substitution rules), but the skill mandates 'Code ONLY from examples/ files' and repeatedly reads from examples/_skeletons/ and examples/_fragments/ — yet no examples/ tree exists in the bundle (only references/), so the executable templates the workflow depends on are missing key details.	2 / 3
Workflow Clarity	Steps 0–7 are clearly sequenced with explicit validation checkpoints and feedback loops — the anti-hallucination checklist, 'If no matching example -- STOP and ask user', and per-step generation order give a clear, recoverable process for a fragile code-generation task.	3 / 3
Progressive Disclosure	Variant details are well split into one-level-deep reference files (java-plain/java-record/java-lombok/kotlin/sub-dto/validation, all present and signaled), but the body also references an examples/_skeletons/ and examples/_fragments/ tree that is absent from the bundle — references are present but a referenced path tree is missing rather than clearly organized.	2 / 3
	Total	9 / 12 Passed

Description

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.

A solid third-person description that covers both the 'what' and explicit 'when' with reasonable trigger terms. It is somewhat under-specified on the concrete generation capabilities and could surface more natural keyword variations.

Suggestions

Expand the description to enumerate the concrete actions the skill performs (e.g. generates constructors, getters/setters, equals/hashCode, supports Java class/record/Lombok and Kotlin variants) rather than only 'Creates a DTO class'.

Add common natural keyword variations users might say — 'data transfer object', 'record', 'Lombok DTO', 'Kotlin data class', 'projection' — so the trigger matches more phrasings.

Dimension	Reasoning	Score
Specificity	The description names the core action ("Creates a DTO (Data Transfer Object) class for an entity") plus contextual use cases, but does not list multiple concrete generation actions (constructors, getters/setters, variants) that the body actually performs — closest to 'Names domain and some actions, but not comprehensive'.	2 / 3
Completeness	It explicitly answers what ("Creates a DTO ... class for an entity") and when ("Use this skill when a DTO class needs to be created, either standalone or as part of a larger task") with explicit triggers and example contexts — clearly both what AND when.	3 / 3
Trigger Term Quality	Natural terms like "DTO", "DTO class", "REST controller", and "service layer" are present, but common variations a user might say ("data transfer object", "projection", "record", "Lombok") are missing — 'Some relevant keywords but missing common variations'.	2 / 3
Distinctiveness Conflict Risk	DTO creation is a clear niche with distinct triggers (DTO, REST controller, service layer, replacing entity usage) unlikely to fire for unrelated skills; third-person voice ("Creates", "Use this skill") is correctly used.	3 / 3
	Total	10 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (517 lines); consider splitting into references/ and linking	Warning

	Total	15 / 16 Passed

Repository: Amplicode/spring-skills
Commit: 79e0e9c

Reviewed: 4 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.