300-frameworks-spring-boot-create-project

Use when you need to create a new Maven-based Spring Boot 4.0.x project using SDKMAN-managed Java and Spring Boot CLI tooling. This should trigger for requests such as Create a Spring Boot Maven project; Bootstrap Spring Boot project with SDKMAN; Generate a new Spring Boot service; Create Spring Boot 4 Maven project; Scaffold Spring Boot service with Java 25. Part of Plinth Toolkit

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/300-frameworks-spring-boot-create-project/SKILL.md

Quality

Content

71%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured overview body that cleanly defers detail to a single one-level-deep reference and includes explicit verification and safety checkpoints. Its main weaknesses are an abstract core creation step in the body (the executable command is only in the reference) and some redundancy between the 'When to use'/'What is covered' sections and the description/workflow.

Suggestions

Inline the concrete 'spring init --build=maven ...' command (or a compact template) into Workflow step 3 so the body is executable on its own, keeping the reference for the extended explanation.

Drop or condense the 'When to use this skill' section since it duplicates the description's trigger phrases, and fold the 'What is covered' bullets into the Workflow to remove redundancy.

Add an explicit feedback loop to the verify step (e.g., 'if ./mvnw clean verify fails, read the failing goal, fix pom.xml/dependencies, and re-run') to reach the top workflow-clarity anchor.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence without explaining Spring Boot/Maven concepts, but the 'When to use this skill' section duplicates the five trigger phrases already in the description and the 'What is covered' bullets overlap the Workflow, which are minor instances that could be trimmed — efficient with minor over-explanation rather than fully lean.	4 / 5
Actionability	It gives concrete commands for prerequisites and verification ('sdk version', './mvnw clean verify' / 'mvn clean verify'), but the central creation step in the body ('Use Spring Boot CLI project creation backed by Spring Initializr') is abstract — the actual executable 'spring init ...' command lives only in the reference, leaving the key detail incomplete in the body.	3 / 5
Workflow Clarity	There is a clear four-step sequence (gather inputs, verify SDKMAN tooling, create project, verify and report) with an explicit VERIFY checkpoint and a SAFETY guard against overwriting directories, but the body lacks an explicit fix-and-retry feedback loop for verification failures, capping it just below the top anchor.	4 / 5
Progressive Disclosure	The body is a concise overview that points to a single real, one-level-deep reference (references/300-frameworks-spring-boot-create-project.md), signaled in both Workflow step 1 and the Reference section, with content appropriately split between overview and detail and easy navigation.	5 / 5
	Total	16 / 20 Passed

Description

86%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description that clearly states what the skill does and when it should trigger, with five natural, synonym-rich trigger phrases. It is slightly limited on specificity (single core action) and carries minor overlap risk from being part of a broader toolkit.

Suggestions

Broaden specificity beyond the single 'create' action by mentioning the verification/safety behaviors the skill performs (e.g., 'create and verify a Maven-based Spring Boot 4.0.x project').

Clarify what 'Part of Plinth Toolkit' means or remove it if it does not aid trigger distinctiveness, to reduce overlap ambiguity with sibling toolkit skills.

Dimension	Reasoning	Score
Specificity	It names the domain and a concrete action ('create a new Maven-based Spring Boot 4.0.x project using SDKMAN-managed Java and Spring Boot CLI tooling') with specific toolchain detail, but the core capability is a single action (project creation) rather than the multiple distinct actions the top anchors expect, so it sits at 'names domain and 1-2 concrete actions' rather than 4.	3 / 5
Completeness	It explicitly answers both 'what' (create a Maven-based Spring Boot 4.0.x project via SDKMAN/CLI tooling) and 'when' ('Use when you need to create... This should trigger for requests such as...') with concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	It supplies five natural trigger phrases with verb synonyms ('Create a Spring Boot Maven project; Bootstrap Spring Boot project with SDKMAN; Generate a new Spring Boot service; Create Spring Boot 4 Maven project; Scaffold Spring Boot service with Java 25') plus concrete version/build qualifiers, giving comprehensive coverage of terms a user would actually say.	5 / 5
Distinctiveness Conflict Risk	The niche is well-scoped (Maven + SDKMAN + Spring Boot 4.0.x + Java 25) with distinct triggers, but the 'Part of Plinth Toolkit' suffix implies sibling framework-scaffolding skills, leaving minor overlap risk with closely related skills rather than the minimal-conflict top anchor.	4 / 5
	Total	17 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: jabrena/plinth
Path: skills/300-frameworks-spring-boot-create-project/SKILL.md
Commit: 77b8825

Reviewed: about 23 hours ago

Table of Contents

Discovery Implementation Validation

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.