crud-rest-controller

Creates a Spring REST controller with CRUD endpoints backed by a Spring Data repository. Use this skill when a CRUD controller needs to be created, either standalone or as part of a larger task.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

77%

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

A well-structured, highly actionable orchestration skill with a clear step sequence and strong validation checkpoints. Its main weaknesses are repeated restatement of the same context-first/AskUserQuestion guidance and a monolithic inline body whose referenced example files are not present in the bundle.

Suggestions

Consolidate the 'derive from context -> confirm -> ask' guidance and the 'don't re-ask what the user already said' rule into a single canonical section; remove the duplicated restatements in Defaults, Step 0, and How-to-ask to recover tokens.

Move the large Defaults tables and the Decision-making philosophy into a separate reference file (e.g. references/defaults.md) so SKILL.md stays a lean overview pointing one level deep.

Ensure the referenced examples/ tree (skeletons, beans, methods, dependencies) is actually bundled alongside the skill so the signaled navigation paths resolve.

Dimension	Reasoning	Score
Conciseness	The body is operationally focused (no basic-concept padding), but the 'derive from context / don't re-ask / prefer AskUserQuestion' guidance is restated roughly four times across the Defaults, Decision-making principle, How-to-ask, and Step 0 sections, so it could be tightened to earn the score-3 'every token earns its place' anchor.	2 / 3
Actionability	Guidance is concrete and executable: exact MCP tool calls, precise example file paths (e.g. 'examples/_methods/{method-name}/{language}.md'), explicit variable substitutions, and FQN-shortening rules — matching the score-3 anchor for specific, copy-ready instruction (the absence of inline code is fine for an orchestration skill per the rubric's code-vs-instruction note).	3 / 3
Workflow Clarity	A clearly sequenced Preflight -> Step 0 -> Step 1..6 flow with explicit validation checkpoints ('STOP and ask user' when no example matches, anti-hallucination checklist, refresh_build_system_model) and error-recovery guidance, satisfying the score-3 anchor.	3 / 3
Progressive Disclosure	References to examples/ files are one level deep and clearly signaled with exact paths, but the SKILL.md body itself is a large inline wall of defaults/philosophy text that could be split out, and no bundle files are present under references/scripts/assets/examples to verify the referenced paths resolve.	2 / 3
	Total	10 / 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 concise, third-person description that cleanly answers both 'what' and 'when' with an explicit trigger clause and a well-scoped niche. It is held back from a perfect score by a single composite action statement and somewhat limited trigger-term variation.

Suggestions

Broaden trigger terms to cover natural phrasings users actually say, e.g. 'REST API', 'expose an entity over REST', or 'add endpoints for an entity'.

Consider naming a couple of concrete sub-actions (e.g. 'with pagination, filtering, and DTO mapping') to lift specificity from a single composite action to a list of concrete capabilities.

Dimension	Reasoning	Score
Specificity	Names the concrete domain and deliverable ('Spring REST controller with CRUD endpoints backed by a Spring Data repository') but describes a single composite action rather than a comprehensive list of distinct actions, matching the score-2 anchor over the multi-action score-3 example.	2 / 3
Completeness	Explicitly states both what it does ('Creates a Spring REST controller with CRUD endpoints...') and when to use it ('Use this skill when a CRUD controller needs to be created, either standalone or as part of a larger task'), satisfying the score-3 anchor with an explicit trigger clause.	3 / 3
Trigger Term Quality	Includes natural terms a user would say ('CRUD controller', 'CRUD endpoints', 'REST controller') but misses common variations like 'REST API', 'expose entity as REST', or 'endpoints for an entity', so coverage is partial rather than complete.	2 / 3
Distinctiveness Conflict Risk	The narrow 'Spring REST controller with CRUD endpoints backed by a Spring Data repository' niche with its 'CRUD controller' trigger is clearly distinguishable and unlikely to fire for unrelated skills, matching the score-3 anchor.	3 / 3
	Total	10 / 12 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
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.