302-frameworks-spring-boot-rest

Use when you need to design, review, or improve REST APIs with Spring Boot — including HTTP methods, resource URIs, status codes, DTOs, versioning, deprecation and sunset headers, content negotiation (JSON and vendor media types), ISO-8601 instants in DTOs, pagination/sorting/filtering, Bean Validation at the boundary, idempotency, ETag concurrency, HTTP caching, error handling, security, contract-first OpenAPI (OpenAPI Generator), controller advice, and problem details for errors. This should trigger for requests such as Review Java code for Spring Boot REST API; Apply best practices for Spring Boot REST API in Java code; Design Spring Boot REST controllers and DTOs; Add Problem Details error responses in Spring Boot REST; Improve pagination validation or idempotency in Spring APIs. Part of Plinth Toolkit

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

78%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-structured overview skill with strong progressive disclosure and explicit compile/verify validation checkpoints. The main gaps are duplicated list content from the description, abstract middle-workflow steps, and the absence of an explicit fix-and-re-verify recovery loop.

Suggestions

Remove the "When to use this skill" list (or the "What is covered" list) since both duplicate the frontmatter description, reclaiming tokens for a brief inline pattern snippet.

Tighten workflow step 3 with a concrete anchor, e.g. "Apply changes matching a specific reference example (e.g., Example 6 for error responses, Example 10 for idempotency)" so the step is self-actionable without opening the reference.

Add an explicit recovery loop after verification: "If `mvn clean verify` fails, fix the failing change and re-run verify before reporting."

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence (no explanations of REST, Spring Boot, or ETags), but the "What is covered in this Skill?" list and the "When to use this skill" list largely duplicate the frontmatter description verbatim, which is minor redundancy that could be trimmed.	4 / 5
Actionability	Concrete executable commands are present ("./mvnw compile or mvn compile", "./mvnw clean verify or mvn clean verify") and the reference pointer is explicit, but the core API-design guidance is deferred to the reference and workflow step 3 ("Implement or refactor configuration/code following the reference patterns") stays abstract, leaving minor gaps.	4 / 5
Workflow Clarity	A clear four-step sequence with explicit validation checkpoints ("MANDATORY: Run ./mvnw compile before applying", "SAFETY: If compilation fails, stop immediately", "VERIFY: Run ./mvnw clean verify after") and edge-case handling, but it lacks an explicit fix-and-re-verify recovery loop after the post-change verification, so it does not reach the anchor-5 feedback-loop bar.	4 / 5
Progressive Disclosure	The body is a concise overview pointing to a single one-level-deep, well-signaled reference ("see references/302-frameworks-spring-boot-rest.md", plus "BEFORE APPLYING: Read the reference" and workflow step 1), and the reference file is real and well-structured with 16 named examples, matching the clear-overview anchor.	5 / 5
	Total	17 / 20 Passed

Description

91%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, comprehensive description with explicit what/when structure and highly natural trigger phrases. The only weaknesses are second-person voice in the trigger clause and inferred sibling-skill overlap from the toolkit naming.

Dimension	Reasoning	Score
Specificity	Comprehensive topic coverage ("HTTP methods, resource URIs, status codes, DTOs, versioning, deprecation and sunset headers, ... ETag concurrency, HTTP caching, ... problem details") but the concrete action verbs are limited to "design, review, or improve" with the remainder enumerated as topic nouns; the "Use when you need to" trigger uses second person, applying the rubric's -1 voice penalty from an otherwise comprehensive 5.	4 / 5
Completeness	Explicitly answers both what ("design, review, or improve REST APIs with Spring Boot" plus a full capability list) and when ("Use when you need to..." and "This should trigger for requests such as..." with five concrete trigger phrases), matching the anchor for explicit what-and-when with concrete triggers.	5 / 5
Trigger Term Quality	"This should trigger for requests such as Review Java code for Spring Boot REST API; Apply best practices for Spring Boot REST API in Java code; Design Spring Boot REST controllers and DTOs; Add Problem Details error responses in Spring Boot REST; Improve pagination validation or idempotency in Spring APIs" gives comprehensive, natural phrasings users would actually say, with synonyms (review/apply/design/add/improve).	5 / 5
Distinctiveness Conflict Risk	The Spring Boot REST niche is clear and triggers are unambiguous, but "Part of Plinth Toolkit" and the "302-frameworks-spring-boot-rest" naming imply sibling framework skills, creating minor overlap risk with closely related toolkit skills rather than minimal conflict risk.	4 / 5
	Total	18 / 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: jabrena/plinth
Path: skills/302-frameworks-spring-boot-rest/SKILL.md
Commit: 05bf9d1

Reviewed: 5 minutes 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.