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. Part of the skills-for-java project
77
71%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/302-frameworks-spring-boot-rest/SKILL.mdQuality
Discovery
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.
This is an excellent skill description that clearly communicates what the skill does (design, review, and improve REST APIs with Spring Boot) and when to use it, with an explicit 'Use when' clause. The extensive list of specific topics provides strong trigger term coverage and makes the skill highly distinguishable. The only minor concern is that the description is quite long, but the detail serves the purpose of disambiguation well.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description lists numerous specific concrete actions and concepts: HTTP methods, resource URIs, status codes, DTOs, versioning, deprecation/sunset headers, content negotiation, pagination/sorting/filtering, Bean Validation, idempotency, ETag concurrency, HTTP caching, error handling, security, contract-first OpenAPI, controller advice, and problem details. This is highly specific and comprehensive. | 3 / 3 |
Completeness | The description explicitly answers both 'what' (design, review, or improve REST APIs with Spring Boot covering a comprehensive list of topics) and 'when' ('Use when you need to design, review, or improve REST APIs with Spring Boot'). The 'Use when...' clause is present and explicit. | 3 / 3 |
Trigger Term Quality | Includes many natural keywords a developer would use: 'REST APIs', 'Spring Boot', 'HTTP methods', 'status codes', 'pagination', 'sorting', 'filtering', 'OpenAPI', 'error handling', 'security', 'DTOs', 'versioning', 'ETag', 'caching'. These are terms developers naturally use when working on REST API design with Spring Boot. | 3 / 3 |
Distinctiveness Conflict Risk | The description carves out a very clear niche: REST API design specifically with Spring Boot, covering a detailed and distinctive set of concerns. The combination of Spring Boot + REST API design + the specific subtopics (ETag concurrency, vendor media types, OpenAPI Generator, problem details) makes it highly unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill is well-structured as a navigation hub with good progressive disclosure to a reference file, and it includes basic compilation safety checks. However, it critically lacks any concrete code examples, specific patterns, or actionable guidance in the body itself — everything substantive is deferred to the reference. The long bullet-point list of topics adds token cost without providing executable value.
Suggestions
Add at least 2-3 concrete code examples showing key patterns (e.g., a properly annotated controller method with @Valid, a ProblemDetail error response, an ETag-based conditional endpoint) so the skill body itself is actionable without requiring the reference file.
Trim the 'What is covered' bullet list to a shorter summary or remove it entirely — the reference file can serve as the detailed index. Replace the saved space with executable examples.
Add a feedback loop to the workflow: specify what to do when `mvn clean verify` fails (e.g., check test output, fix validation errors, re-run) rather than only having a stop condition for the initial compile.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The bullet-point list of covered topics is somewhat verbose and reads like a table of contents rather than actionable content. The 'What is covered' section largely restates what Claude could infer from the skill title and description, though it does provide useful specificity about expected patterns (e.g., 'OffsetDateTime, Instant', '409 Conflict for collisions'). | 2 / 3 |
Actionability | The skill body contains no concrete code examples, no executable commands beyond generic mvnw invocations, and no specific patterns or anti-patterns. All substantive guidance is deferred entirely to the reference file, making the skill itself vague and non-actionable. | 1 / 3 |
Workflow Clarity | The constraints section provides a clear sequence (compile → apply → verify) with a stop condition on failure, which is good. However, the validation steps are generic (just Maven compile/verify) with no specific checkpoints for REST API correctness, and there's no feedback loop for fixing issues found during verification. | 2 / 3 |
Progressive Disclosure | The skill provides a clear overview of what's covered and cleanly delegates detailed rules and examples to a single reference file with a well-signaled one-level-deep link. The structure is appropriate for a skill that serves as an entry point to detailed guidance. | 3 / 3 |
Total | 8 / 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- jabrena/cursor-rules-java
- Commit
9ec21dd
- 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.