spring-boot-engineer
Use when building Spring Boot 3.x applications, microservices, or reactive Java applications. Invoke for Spring Data JPA, Spring Security 6, WebFlux, Spring Cloud integration.
Install with Tessl CLI
npx tessl i github:jeffallan/claude-skills --skill spring-boot-engineerOverall
score
61%
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
72%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description excels at trigger term coverage and distinctiveness with specific Spring ecosystem technologies and version numbers. However, it lacks concrete action verbs describing what the skill actually does - it tells when to use it but not what capabilities it provides beyond vague 'building' and 'integration'.
Suggestions
Add specific concrete actions like 'Generate REST controllers, configure security policies, set up database repositories, create reactive endpoints'
Expand the 'what' portion to describe capabilities: 'Creates Spring Boot applications with auto-configuration, implements security authentication/authorization, builds reactive streams with WebFlux'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Spring Boot 3.x) and lists specific technologies (Spring Data JPA, Spring Security 6, WebFlux, Spring Cloud), but doesn't describe concrete actions - only mentions 'building' and 'integration' without specifying what operations can be performed. | 2 / 3 |
Completeness | Has a 'Use when' clause that covers when to invoke the skill, but the 'what does this do' portion is weak - it only says 'building' applications without describing specific capabilities like generating configurations, creating REST endpoints, setting up security, etc. | 2 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'Spring Boot', 'microservices', 'reactive', 'Spring Data JPA', 'Spring Security', 'WebFlux', 'Spring Cloud' - these are all terms developers naturally use when seeking help with Spring applications. | 3 / 3 |
Distinctiveness Conflict Risk | Very distinct niche with Spring Boot 3.x and specific Spring ecosystem components (Security 6, WebFlux, Spring Cloud). The version specificity (3.x, Security 6) and technology stack focus make it unlikely to conflict with generic Java or other framework skills. | 3 / 3 |
Total | 10 / 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 has good structural organization with clear progressive disclosure through the reference table, but critically lacks actionable code examples. The content reads more like a role description than executable guidance, with abstract instructions that don't demonstrate Spring Boot 3.x patterns concretely. The MUST DO/MUST NOT DO constraints are useful but would benefit from code snippets showing correct vs incorrect approaches.
Suggestions
Add executable code examples for key patterns: show a complete @RestController with validation, a @Service with constructor injection, and a @Repository interface
Replace abstract workflow steps with concrete commands or code snippets (e.g., show actual Spring Security 6 configuration instead of 'Add Spring Security')
Include a minimal working example that demonstrates the layered architecture (Entity → Repository → Service → Controller) with actual Java code
Add validation checkpoints to the workflow, such as 'Run ./mvnw test after implementing each layer' or specific Actuator health check verification
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content includes some unnecessary verbosity like the role definition paragraph and 'When to Use This Skill' section that largely restates obvious information. The reference table and constraints are efficient, but the overall structure could be tighter. | 2 / 3 |
Actionability | The skill provides no executable code examples, only abstract guidance like 'Apply dependency injection via constructor injection' without showing how. The 'Output Templates' section describes what to provide but gives no concrete examples or copy-paste ready code. | 1 / 3 |
Workflow Clarity | The 6-step 'Core Workflow' provides a sequence but lacks validation checkpoints, feedback loops, or specific commands. Steps like 'Implement' and 'Secure' are too abstract to guide actual execution without the referenced files. | 2 / 3 |
Progressive Disclosure | The reference table clearly signals one-level-deep references to specific topics (web.md, data.md, security.md, etc.) with clear 'Load When' guidance. The structure appropriately separates overview from detailed content. | 3 / 3 |
Total | 8 / 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 |
|---|---|---|
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 |
body_examples | No examples detected (no code fences and no 'Example' wording) | 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.