CtrlK
BlogDocsLog inGet started
Tessl Logo

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

71

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

86%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 well-architected skill body: concise overview with explicit routing to one-level reference files, concrete tool calls and decision tables, and a strong anti-hallucination checklist. The main minor weakness is some redundancy across the question-batching guidance and the advisory rather than loop-enforced validation.

Suggestions

Consolidate the AskUserQuestion rules, which currently appear in three places (Defaults, Decision-making principle, Step 4) into one canonical section to remove redundancy.

Promote the anti-hallucination checklist into an explicit validate→fix→retry loop with a re-validation step after edits, rather than a single pre-write checklist.

Trim the Defaults table rows whose values are 'NO / auto-detected' into a single auto-detected note, since they add tokens without changing behavior.

DimensionReasoningScore

Conciseness

The body is dense and directive with minimal conceptual padding, but sections like the repeated AskUserQuestion rules and Defaults table carry some redundancy that could be tightened.

4 / 5

Actionability

Provides fully executable, specific guidance — exact MCP tool calls, decision tables mapping context to actions, concrete FQN-shortening import rules, and cited example file paths — leaving little ambiguity about what to do.

5 / 5

Workflow Clarity

Steps 0–7 are clearly sequenced with explicit checkpoints (validation gates, anti-hallucination checklist before writing code), but the checklist is advisory rather than an enforced validate→fix→retry loop, leaving a minor feedback-loop gap.

4 / 5

Progressive Disclosure

Body is a lean overview that splits detailed variant logic into clearly signaled one-level-deep references (java-lombok.md, java-record.md, java-plain.md, kotlin.md, sub-dto.md, validation.md), all confirmed present in references/.

5 / 5

Total

18

/

20

Passed

Description

88%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 strong, concrete description that names the artifact, the supported variants, and explicit use-when triggers with example contexts. It is concise yet complete and clearly scoped to DTO creation rather than general codegen.

DimensionReasoningScore

Specificity

Names multiple concrete actions — "creates a DTO ... class", "Java class, Java record, Java+Lombok, or Kotlin data class" with constructors, getters/setters, equals/hashCode, toString, and optional features — giving comprehensive coverage of capabilities.

5 / 5

Completeness

Clearly answers "what" (creates a DTO class for an entity with listed members) and "when" ("Use this skill when a DTO class needs to be created, either standalone or as part of a larger task") with concrete trigger contexts.

5 / 5

Trigger Term Quality

Includes natural terms users say ("DTO", "entity", "REST controller", "service layer") but lacks synonyms like "data transfer object" spelled out or file-extension keywords; good coverage with a few natural variants missing.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche (DTO generation with specific variant routing); minor overlap risk with the sibling mapper-creator skill, but the delegation boundary is explicit so conflict is low.

4 / 5

Total

18

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

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