spring-boot-rest-api-standards
Implement REST API design standards and best practices for Spring Boot projects. Use when creating or reviewing REST endpoints, DTOs, error handling, pagination, security headers, HATEOAS and architecture patterns.
Install with Tessl CLI
npx tessl i github:giuseppe-trisciuoglio/developer-kit --skill spring-boot-rest-api-standardsOverall
score
84%
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 a well-crafted skill description that follows best practices. It uses third person voice, lists specific capabilities, includes a clear 'Use when...' clause with relevant trigger terms, and targets a distinct technical domain (Spring Boot REST APIs) that minimizes conflict with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'REST endpoints, DTOs, error handling, pagination, security headers, HATEOAS and architecture patterns' - these are concrete, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what ('Implement REST API design standards and best practices for Spring Boot projects') and when ('Use when creating or reviewing REST endpoints, DTOs, error handling...') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'REST API', 'Spring Boot', 'endpoints', 'DTOs', 'error handling', 'pagination', 'security headers', 'HATEOAS' - good coverage of terms developers naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche targeting Spring Boot REST APIs specifically, with distinct triggers like 'HATEOAS', 'DTOs', 'Spring Boot' that differentiate it from generic API or Java skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
73%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, actionable skill with excellent code examples that are production-ready. The main weaknesses are verbosity in the introductory sections (Overview, When to Use) that explain concepts Claude already knows, and missing validation/verification steps in the workflow for what are potentially destructive database operations.
Suggestions
Remove or drastically shorten the 'Overview' and 'When to Use This Skill' sections - Claude knows what REST APIs are and when to apply REST patterns
Add explicit validation checkpoints to the Instructions workflow, such as 'Test endpoint with curl/httpie before proceeding' or 'Verify error responses return expected format'
Consolidate the numbered Instructions list with the Best Practices section to reduce redundancy (e.g., validation is mentioned in both)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill contains some unnecessary explanation (e.g., 'When to Use This Skill' section lists obvious use cases, Overview restates what REST APIs are). The examples are good but the instructional prose could be tightened significantly. | 2 / 3 |
Actionability | Provides fully executable, copy-paste ready code examples for controllers, DTOs, exception handlers, and service patterns. All code is complete with proper imports implied and annotations shown. | 3 / 3 |
Workflow Clarity | The 8-step process in Instructions is clear but lacks validation checkpoints. For API development involving database operations and security, there's no explicit 'test your endpoint' or 'verify response format' feedback loops between steps. | 2 / 3 |
Progressive Disclosure | Well-structured with clear sections (Overview, Instructions, Examples, Best Practices, Constraints, References). References to external files are one level deep and clearly signaled at the end. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
75%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 12 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 12 / 16 Passed | |
- 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.