305-frameworks-spring-boot-modulith

Use when you need to design, review, or improve modular monoliths with Spring Modulith in Spring Boot applications - including application module package structure, ApplicationModules verification, named interfaces, allowed dependencies, domain events, @ApplicationModuleTest, Scenario-based module tests, generated documentation, actuator exposure, observability, and event publication registry choices. This should trigger for requests such as Add Spring Modulith to a Spring Boot application; Review Spring Modulith module boundaries; Improve modular monolith architecture in Spring Boot; Add @ApplicationModuleTest tests; Generate Spring Modulith documentation. Part of Plinth Toolkit

Quality

88%

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

Quality

Content

85%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, lean overview with strong progressive disclosure and an explicit compile/verify validation loop. The main improvement opportunity is reducing redundancy between the capability list, description, and 'When to use' section, and surfacing a few key inline code patterns.

Suggestions

Consolidate the overlapping capability lists in 'What is covered' and 'When to use this skill' to remove redundancy with the description and tighten the body.

Inline one or two key executable patterns (e.g., the ApplicationModules.verify() test and the BOM dependency snippet) so the body is self-sufficient for the most common action without requiring the reference.

Move the version-specific compatibility note ('Spring Boot 4.0.x') into a clearly labeled baseline/deprecation-style section so time-sensitive details do not penalize long-term conciseness.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence, but the 'What is covered' bullet list, the description's capability list, and the 'When to use this skill' section overlap noticeably and could be consolidated.	4 / 5
Actionability	Concrete executable commands are present ('./mvnw compile', 'mvn compile', './mvnw clean verify') and the workflow gives specific steps, but the bulk of executable code patterns (XML deps, Java tests) are deferred to the reference rather than inline.	4 / 5
Workflow Clarity	A clear four-step sequence is paired with an explicit validation feedback loop: MANDATORY compile before changes, SAFETY stop-on-failure, and VERIFY clean verify afterward, matching the anchor for explicit validation with error recovery.	5 / 5
Progressive Disclosure	The SKILL.md is a concise overview pointing to a single one-level-deep reference (references/305-frameworks-spring-boot-modulith.md), clearly signaled both in the workflow and via a final link, with detailed examples appropriately split into the reference file.	5 / 5
	Total	18 / 20 Passed

Description

92%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, specific description that explicitly covers both what the skill does and when to trigger it, with natural request phrasing and a clear niche. The only minor gap is the lack of synonyms and file extensions in the trigger terms.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capabilities ('module package structure, ApplicationModules verification, named interfaces, allowed dependencies, domain events, @ApplicationModuleTest, Scenario-based module tests, generated documentation, actuator exposure, observability, and event publication registry choices'), giving comprehensive coverage of the skill's scope.	5 / 5
Completeness	Explicitly answers both what ('design, review, or improve modular monoliths with Spring Modulith') and when via a leading 'Use when' clause plus concrete 'This should trigger for requests such as' trigger phrases.	5 / 5
Trigger Term Quality	Natural request phrases ('Add Spring Modulith to a Spring Boot application; Review Spring Modulith module boundaries; Improve modular monolith architecture in Spring Boot') match what users would say, but synonyms and file extensions are absent, keeping it just below comprehensive.	4 / 5
Distinctiveness Conflict Risk	The narrow niche ('modular monoliths with Spring Modulith in Spring Boot applications') plus specific trigger phrases make it clearly distinguishable with minimal overlap risk against other skills.	5 / 5
	Total	19 / 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/305-frameworks-spring-boot-modulith/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.