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

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

57%

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 with good progressive disclosure and a clear sequenced workflow, but it defers the key executable command to the reference and lacks an explicit error-recovery loop, leaving actionability and workflow_clarity mid-range.

Suggestions

Add the concrete `spring init --build=maven ...` command (or a copy-paste-ready template with the key flags) to the "Create the Maven project" step so the body is actionable without opening the reference.

Make the verify feedback loop explicit, e.g. "If `./mvnw clean verify` fails, read the failing goal, fix the pom/configuration, and re-run before reporting completion."

Drop or shrink the "When to use this skill" section (it duplicates the description triggers) and merge the "What is covered" bullets into the Workflow to remove redundancy.

Dimension	Reasoning	Score
Conciseness	Per-section prose is lean and avoids teaching basics, but the "When to use this skill" list duplicates the description's triggers and the "What is covered" bullets overlap the Workflow steps, so it could be tightened.	2 / 3
Actionability	Concrete commands exist for verification ("./mvnw clean verify", "mvn clean verify", "sdk version"), but the central creation step is vague ("Use Spring Boot CLI project creation backed by Spring Initializr...") with no executable `spring init` command in the body.	2 / 3
Workflow Clarity	The four-step sequence is clear and includes an explicit Maven verify checkpoint, but for a filesystem-mutating operation the error-recovery feedback loop (verify fails -> fix -> re-run) is only implied, not stated in the body.	2 / 3
Progressive Disclosure	The body is a concise overview that points to a single one-level-deep, clearly signaled reference (references/300-frameworks-spring-boot-create-project.md, verified to exist) for the full command workflow.	3 / 3
	Total	9 / 12 Passed

Description

90%

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, well-targeted description with explicit "Use when" triggers and good natural-language coverage. Its only weakness is specificity, since it describes one core action with tooling detail rather than enumerating multiple concrete capabilities.

Dimension	Reasoning	Score
Specificity	"create a new Maven-based Spring Boot 4.0.x project using SDKMAN-managed Java and Spring Boot CLI tooling" names a concrete action and specific tooling, but it is a single primary action rather than the multiple distinct actions (e.g. extract, fill, merge) the top anchor expects.	2 / 3
Completeness	It states what ("create a new Maven-based Spring Boot 4.0.x project...") and when via an explicit "Use when you need to create..." clause plus enumerated triggers, satisfying both halves with explicit trigger guidance.	3 / 3
Trigger Term Quality	"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" gives broad coverage of natural phrases a user would actually say.	3 / 3
Distinctiveness Conflict Risk	The narrow niche (Maven, Spring Boot 4.0.x, SDKMAN-managed Java 25, Spring Boot CLI) with distinct triggers makes it unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 12 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
Commit: aaee915

Reviewed: 1 day 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.