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

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

72%

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

A well-structured, concise skill body that uses progressive disclosure effectively with a real single-level reference. Its main gaps are that the executable creation command and the verify-failure feedback loop are delegated to the reference rather than surfaced in the body.

Suggestions

Surface the concrete `mn create-app` invocation (with --build=maven, --jdk, --features, --lang, --output flags) in the body's Workflow Step 3 so the core action is actionable without opening the reference.

Add an explicit verify-failure feedback loop in the body (e.g., 'If `./mvnw clean verify` fails, read the failing goal, fix the cause, and re-run verify') to satisfy the error-recovery expectation for a filesystem-mutating operation.

Drop or trim the 'When to use this skill' section, which duplicates the trigger phrases already in the frontmatter description, to reduce redundancy.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence, with no padding explaining what Micronaut/Maven/SDKMAN are; every section (Constraints, Workflow, Reference) earns its place, fitting the lean-and-efficient anchor at 3.	3 / 3
Actionability	Concrete commands appear for verification ("sdk version", "./mvnw clean verify", "mvn clean verify"), but the core creation command (`mn create-app`) lives only in the reference, so the body's guidance is incomplete rather than copy-paste ready, matching anchor 2 not 3.	2 / 3
Workflow Clarity	A clear 4-step sequence with an explicit verify checkpoint is present, but the in-body error-recovery feedback loop (fix -> re-verify) is absent and only implied via the reference, keeping it below the feedback-loops-required anchor at 3.	2 / 3
Progressive Disclosure	Clear overview body with a single well-signaled, verified one-level-deep reference ("Read the reference...", "BEFORE APPLYING: Read the reference", plus a Reference link), matching the clear-overview-with-one-level-references anchor at 3.	3 / 3
	Total	10 / 12 Passed

Description

100%

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 highly specific, third-person description that clearly states both the capability and explicit trigger conditions with natural user phrasings. It is concise, well-scoped to the Micronaut/Maven/SDKMAN niche, and carries low conflict risk.

Dimension	Reasoning	Score
Specificity	Names a concrete action ("create a new Maven-based Micronaut 4.x project") with specific tooling (SDKMAN-managed Java, Micronaut CLI), matching the multiple-concrete-actions anchor rather than the vague single-domain anchor at 2.	3 / 3
Completeness	Answers both what (create Maven-based Micronaut 4.x project via SDKMAN/CLI) and when (explicit "Use when you need to..." plus enumerated trigger phrases), matching the both-what-and-when anchor at 3.	3 / 3
Trigger Term Quality	Explicit trigger phrasings ("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") give strong coverage of natural terms users would say, exceeding the partial-coverage anchor at 2.	3 / 3
Distinctiveness Conflict Risk	The narrow niche (Micronaut 4.x + Maven + SDKMAN + Java 25) with distinct triggers is unlikely to collide with other skills, fitting the clear-niche anchor at 3 rather than the overlap-prone anchor at 2.	3 / 3
	Total	12 / 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.