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

78%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 that delegates detail to a single real reference file and includes concrete build/verify commands with a pre-change compile checkpoint. The main gaps are minor redundancy in the Constraints section and an implicit rather than explicit post-change retry loop.

Suggestions

Tighten the Constraints section by collapsing the five overlapping compile/verify bullets into one prerequisite ('compile must pass before changes') and one verification step ('run mvn clean verify after'), removing the repetition.

Add an explicit post-change feedback loop to the workflow: if 'mvn clean verify' fails, fix the issue and re-run verification before reporting, rather than just summarizing results.

Consider including one small inline good/bad code snippet (e.g. constructor injection with @Inject) so the skill's core pattern is actionable without opening the reference.

Dimension	Reasoning	Score
Conciseness	The body is largely lean and assumes Claude's competence (no explaining of what Micronaut is), but the Constraints section restates the compile-before/verify-after message across five overlapping bullets, a minor redundancy that could be tightened.	4 / 5
Actionability	It provides concrete executable commands ('./mvnw compile', 'mvn compile', './mvnw clean verify') and a specific reference file to read, but the actual code patterns live in the deferred reference rather than inline, leaving minor gaps.	4 / 5
Workflow Clarity	The four-step workflow has a clear pre-change validation checkpoint (compile must pass; stop immediately on failure) and a post-change verify step, but the post-change verification lacks an explicit fix-and-retry feedback loop, which is a minor validation gap.	4 / 5
Progressive Disclosure	The body is a genuine overview that points to a single, well-signaled, one-level-deep reference (references/501-frameworks-micronaut-core.md, which exists) with a clean markdown link, keeping detail appropriately split.	5 / 5
	Total	17 / 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, highly specific description that clearly states both capabilities and concrete trigger phrases for a well-scoped Micronaut niche. Its only minor weakness is slightly repetitive trigger phrasing lacking synonym/extension breadth.

Dimension	Reasoning	Score
Specificity	The description enumerates many concrete capabilities — 'Micronaut.run bootstrap', '@Singleton/@Prototype', '@Factory beans', '@ConfigurationProperties', '@Requires', '@Controller vs services', '@Scheduled', 'graceful shutdown', '@ExecuteOn for blocking work' — giving comprehensive coverage of the domain's specific actions.	5 / 5
Completeness	It explicitly answers both 'what' (the enumerated capability list) and 'when' via a leading 'Use when building or reviewing Micronaut applications' clause plus five concrete trigger requests, satisfying the highest anchor.	5 / 5
Trigger Term Quality	It includes natural request phrasings a user would say ('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'), but the example triggers are somewhat repetitive and lack synonym/extension variations, stopping short of comprehensive coverage.	4 / 5
Distinctiveness Conflict Risk	The description targets a clear niche (Micronaut framework with framework-specific annotations and terms) with distinct triggers, giving minimal conflict risk against unrelated 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/501-frameworks-micronaut-core/SKILL.md
Commit: 05bf9d1

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