501-frameworks-micronaut-core

Use when building or reviewing Micronaut applications — Micronaut.run bootstrap, @Singleton/@Prototype, @Factory beans, @ConfigurationProperties, environments, @Requires, @Controller vs services, @Scheduled, graceful shutdown, @ExecuteOn for blocking work, and Jakarta-consistent APIs. This should trigger for requests such as Review Java code for Micronaut application structure and beans; Apply best practices for Micronaut configuration, @Requires, and factories; Improve scheduling, shutdown, or threading in Micronaut services. ; Review Micronaut dependency injection scopes and factories; Configure Micronaut @Requires conditions for environments. Part of Plinth Toolkit

Quality

85%

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-structured overview body with good progressive disclosure to a real, well-organized reference file and a clear gated workflow. Its main weakness is redundancy: the compile constraint is repeated four times and the 'When to use' section duplicates the description verbatim.

Suggestions

Collapse the Constraints section's four restatements of the compile rule into two bullets: one for the pre-change compile gate and one for post-change verification.

Remove the 'When to use this skill' section, which duplicates the frontmatter description verbatim and adds no new information to the body.

Add an explicit error-recovery step to the workflow (e.g., 'If verification fails, fix the failing changes and re-run mvn clean verify') to close the feedback loop.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean, but the compile-before/stop-if-fails rule is stated four times in five lines ('Before applying Micronaut changes, ensure the project compiles. If compilation fails, stop immediately.' then MANDATORY/PREREQUISITE/SAFETY bullets repeating it), and 'When to use this skill' duplicates the frontmatter description verbatim.	3 / 5
Actionability	Concrete, executable commands are given ('Run `./mvnw compile` or `mvn compile` before applying any change', 'Run `./mvnw clean verify`', 'Read `references/501-frameworks-micronaut-core.md`'), with only workflow steps 2-3 remaining high-level ('following the reference patterns and project conventions').	4 / 5
Workflow Clarity	The 4-step workflow has a clear pre-change compile gate ('compilation failure is a blocking condition') and a post-change verify step, but lacks an explicit error-recovery loop if verification fails after changes are applied.	4 / 5
Progressive Disclosure	The SKILL.md is a clean overview; the single reference file exists, is one level deep with no nested references (verified), and is clearly signaled both in the workflow and a dedicated Reference section with a markdown link.	5 / 5
	Total	16 / 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 description: comprehensive, specific, and explicitly stating both what it does and when to use it with concrete trigger phrases. Only minor polish is needed (an awkward 'services. ;' punctuation break and the 'Part of Plinth Toolkit' trailer).

Dimension	Reasoning	Score
Specificity	The description enumerates the full set of concrete capabilities ('Micronaut.run bootstrap, @Singleton/@Prototype, @Factory beans, @ConfigurationProperties, environments, @Requires, @Controller vs services, @Scheduled, graceful shutdown, @ExecuteOn for blocking work, and Jakarta-consistent APIs'), comprehensively mirroring the skill's actual coverage.	5 / 5
Completeness	It explicitly answers both 'what' ('building or reviewing Micronaut applications' with named capabilities) and 'when' ('Use when building or reviewing... This should trigger for requests such as...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural trigger phrasings like 'Review Java code for Micronaut application structure and beans' and 'Improve scheduling, shutdown, or threading in Micronaut services' match what users would say, but common synonyms or variations (e.g., 'Micronaut app', Groovy/Kotlin Micronaut) are absent.	4 / 5
Distinctiveness Conflict Risk	'Micronaut' and its framework-specific annotations form a clear, distinct niche; the description is unlikely to trigger for other skills, even within the 'Plinth Toolkit' family.	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/501-frameworks-micronaut-core/SKILL.md
Commit: dca88dc

Reviewed: 3 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.