500-frameworks-micronaut-create-project

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

Quality

80%

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

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-organized, lean instruction skill with good progressive disclosure and a sequenced workflow including validation; its main weakness is that the actual project-creation command lives only in the reference, leaving the body's core action short of fully executable guidance.

Suggestions

Add the concrete Micronaut CLI creation command (e.g. the actual `mn create-app` invocation with Maven and feature flags) to step 3 so the body is actionable without forcing a reference read for the core action.

Remove the 'When to use this skill' section or fold it into the description, since it duplicates the description's trigger phrases verbatim.

Add an explicit error-recovery feedback loop after the verify step (e.g. 'if verification fails, fix the reported issues and re-run ./mvnw clean verify') to lift workflow clarity to the top anchor.

Dimension	Reasoning	Score
Conciseness	The body is lean and does not over-explain concepts Claude already knows (no definitions of Micronaut/SDKMAN/Maven), but the 'When to use this skill' section duplicates triggers already in the description and 'What is covered' partly duplicates the Workflow, leaving minor trimmable redundancy just above the midpoint.	4 / 5
Actionability	Concrete commands appear for verification ('sdk version', './mvnw clean verify', 'mvn clean verify'), but the core creation action ('Use the Micronaut CLI to create a Maven project') is high-level with no actual command in the body — the executable detail is deferred to the reference, leaving key details incomplete.	3 / 5
Workflow Clarity	The 4-step workflow is clearly sequenced with a prerequisite check (SDKMAN) and a verification checkpoint (Maven verify), but there is no explicit error-recovery feedback loop, placing it just below the top anchor.	4 / 5
Progressive Disclosure	The body is a concise overview pointing to a single real reference file (references/500-frameworks-micronaut-create-project.md, confirmed present) signaled clearly in two places and one level deep, matching the clear-overview anchor.	5 / 5
	Total	16 / 20 Passed

Description

90%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 well-crafted description with explicit trigger guidance, comprehensive natural keywords, and a clearly distinct niche; its only real flaw is second-person voice ('you need'), which costs it specificity per the rubric.

Dimension	Reasoning	Score
Specificity	The description names the domain and a richly-specified action ('create a new Maven-based Micronaut 4.x project using SDKMAN-managed Java and Micronaut CLI tooling'), which is solidly at anchor 4, but it uses second person voice ('Use when you need to create...') so specificity is reduced by 1 per the rubric guidelines.	3 / 5
Completeness	It explicitly answers both 'what' (create a Maven-based Micronaut 4.x project via SDKMAN-managed tooling) and 'when' (explicit 'Use when...' clause with concrete trigger phrases), matching the top anchor exactly.	5 / 5
Trigger Term Quality	It lists five natural trigger phrases a user would actually say ('Create a Micronaut Maven project; Bootstrap Micronaut project with SDKMAN; Generate a new Micronaut service; Create Micronaut 4 Maven project; Scaffold Micronaut service with Java 25'), covering synonyms (create/bootstrap/generate/scaffold) and version specifics, matching the comprehensive anchor.	5 / 5
Distinctiveness Conflict Risk	The combination of Micronaut 4.x, Maven, SDKMAN, and Java 25 defines a clear niche with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	18 / 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/500-frameworks-micronaut-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.