springboot-project-starter
Scaffold a production-ready Spring Boot 3.3+ application with Java 21+, Spring Data JPA, Spring Security, Flyway migrations, and comprehensive testing.
77
72%
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 ./backend-java/springboot-project-starter/SKILL.mdQuality
Discovery
67%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 description excels at specificity and distinctiveness by naming exact technologies and versions, making it clearly identifiable for Spring Boot projects. However, it lacks explicit trigger guidance ('Use when...') which limits Claude's ability to know when to select it, and could benefit from more natural user-facing keywords beyond technical jargon.
Suggestions
Add a 'Use when...' clause with trigger terms like 'new Spring Boot project', 'bootstrap Java app', 'create Spring application', 'start new backend'
Include common user phrases and variations such as 'REST API', 'web service', 'microservice', or 'Java backend' that users might naturally say when needing this skill
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and technologies: 'Scaffold a production-ready Spring Boot 3.3+ application with Java 21+, Spring Data JPA, Spring Security, Flyway migrations, and comprehensive testing.' This clearly names the domain and specific components. | 3 / 3 |
Completeness | Clearly answers 'what does this do' (scaffold Spring Boot app with specific technologies), but lacks an explicit 'Use when...' clause or trigger guidance for when Claude should select this skill. | 2 / 3 |
Trigger Term Quality | Contains relevant technical keywords like 'Spring Boot', 'Java 21', 'Spring Data JPA', 'Spring Security', 'Flyway' that users would mention, but missing common variations like 'new project', 'bootstrap', 'starter', 'create app', or file extensions. | 2 / 3 |
Distinctiveness Conflict Risk | Very specific niche targeting Spring Boot 3.3+ with Java 21+ and named dependencies. Unlikely to conflict with generic Java skills or other framework scaffolding skills due to the precise version and technology stack specified. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a highly actionable Spring Boot scaffold skill with excellent executable code examples and clear workflow steps. The main weakness is its length - while comprehensive, some patterns could be referenced rather than fully inline, and certain boilerplate (like complete getter/setter implementations) adds tokens without proportional value for Claude.
Suggestions
Consider moving detailed code examples (full entity, service, controller implementations) to a separate PATTERNS.md file and keeping only minimal examples inline
Remove explicit getter/setter implementations from the entity example - Claude knows how to write these, or note 'add standard getters/setters' to save tokens
Add a brief 'Validation checkpoint' note after the scaffold command to verify the zip extracted correctly before proceeding
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some verbose sections that could be tightened. The full entity with all getters/setters, complete test examples, and extensive configuration files add bulk. However, most content is necessary for a production-ready scaffold. | 2 / 3 |
Actionability | Excellent actionability with fully executable code throughout - complete curl commands, working Java classes, SQL migrations, YAML configs, and Maven commands. Everything is copy-paste ready with no pseudocode. | 3 / 3 |
Workflow Clarity | Clear sequenced workflow in 'First Steps After Scaffold' section with numbered steps including validation (compile check, health endpoint verification). The scaffold command, project structure, and common commands provide clear operational guidance. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but everything is inline in a single large file. The extensive code examples (entity, DTOs, mapper, repository, service, controller, security, exception handler, tests, configs) could benefit from references to separate files for advanced patterns. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (627 lines); consider splitting into references/ and linking | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Repository
- achreftlili/deep-dev-skills
- Commit
181fcbc
- 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.