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, API documentation, 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 its purpose and trigger conditions. It uses proper third-person voice, includes an explicit 'Use when' clause, and provides comprehensive coverage of specific capabilities. The extensive list of technical terms serves as effective trigger keywords while also defining clear boundaries for the skill's scope.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists numerous specific concrete actions: 'design, review, or improve REST APIs' with detailed capabilities including HTTP methods, resource URIs, status codes, DTOs, versioning, pagination, validation, error handling, security, and documentation. | 3 / 3 |
Completeness | Explicitly answers both what ('design, review, or improve REST APIs with Spring Boot') and when ('Use when you need to...') with clear trigger guidance at the start of the description. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'REST APIs', 'Spring Boot', 'HTTP methods', 'pagination', 'validation', 'error handling', 'API documentation', 'ETag', 'caching' - these are all terms developers naturally use when working on API design. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear niche: specifically targets Spring Boot REST API design with detailed technical scope. The combination of 'REST APIs' + 'Spring Boot' + specific concerns like 'vendor media types', 'Bean Validation', 'problem details' creates a unique fingerprint unlikely to conflict with generic coding 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.
This skill serves primarily as a table of contents pointing to a reference file, but provides almost no actionable content in the body itself. While the progressive disclosure is well-executed and constraints are reasonable, the lack of any concrete code examples or specific guidance means Claude must always consult the reference file to do anything useful. The extensive topic list adds tokens without adding value since these are standard REST concepts.
Suggestions
Add 2-3 concrete code examples showing the most common patterns (e.g., a controller method with @Valid, proper status codes, and error handling) directly in the skill body
Remove or significantly condense the 'What is covered' bullet list - these are standard REST concepts that don't need enumeration
Add a feedback loop to the constraints section explaining what to do when compilation fails (e.g., 'If compilation fails, diagnose the error, fix it, and re-run compile before proceeding')
Include at least one good/bad pattern comparison inline to make the skill immediately actionable without requiring reference file consultation
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill lists many topics Claude already understands (HTTP methods, status codes, basic REST concepts) without adding novel guidance. The bullet list is comprehensive but could be trimmed since it mostly enumerates standard REST concepts. | 2 / 3 |
Actionability | No concrete code examples, commands, or executable guidance provided. The skill describes what topics are covered and points to a reference file, but provides no copy-paste ready patterns or specific implementation details in the body itself. | 1 / 3 |
Workflow Clarity | The constraints section provides a clear sequence (compile -> apply -> verify) with a safety checkpoint, but lacks feedback loops for error recovery. The 'stop immediately' instruction doesn't explain what to do next if compilation fails. | 2 / 3 |
Progressive Disclosure | Appropriately structured as an overview with a single, clearly signaled reference to detailed guidance. The reference link is one level deep and well-organized with clear navigation to the detailed rules and examples. | 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
7772a1b
- 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.