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

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

70%

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

The body is a well-organized overview with strong progressive disclosure and a clear, validated workflow that gates changes behind compilation checks. Its weaknesses are mild redundancy (duplicated triggers and a double reference pointer) and the absence of any in-body executable code examples, which are instead deferred to the reference.

Suggestions

Remove or condense the "When to use this skill" section, since its bullets duplicate the description's trigger phrases, and consolidate the two reference pointers (workflow step 1 and the Reference section) into one clearly signaled link.

Add one or two short in-body good/bad code snippets (e.g. a thin main with Micronaut.run vs a fat main, or @ConfigurationProperties vs scattered @Property) so the body carries some executable, copy-paste-ready guidance rather than deferring all examples to the reference.

Tighten workflow step 4's vague "Execute appropriate build/tests" by pointing directly to the concrete "mvn clean verify" command already specified in Constraints.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and does not explain concepts Claude already knows, but the "When to use this skill" section duplicates the description's trigger phrases verbatim and the reference file is pointed to twice (workflow step 1 and the Reference section), so it could be tightened.	2 / 3
Actionability	It names specific APIs/annotations (e.g. "@ExecuteOn(TaskExecutors.BLOCKING)") and gives executable build commands ("./mvnw compile", "mvn clean verify"), but contains no executable code or good/bad examples in the body — the concrete, copy-paste-ready detail is deferred to the reference, leaving the guidance incomplete in-file.	2 / 3
Workflow Clarity	The four-step numbered Workflow is paired with explicit validation checkpoints in Constraints (MANDATORY compile before changes, stop immediately on failure, VERIFY with "mvn clean verify" after), forming a clear sequence with a compile-fail feedback loop, matching the highest anchor.	3 / 3
Progressive Disclosure	A concise, well-sectioned overview (What is covered, Constraints, Workflow, Reference) points to a single real, one-level-deep reference file (references/501-frameworks-micronaut-core.md, verified present) that is clearly signaled, giving easy navigation with no nested-reference chains.	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 strong, comprehensive description that states concrete Micronaut capabilities in third person and supplies explicit natural-language triggers for when to use the skill. Minor surface noise (a stray ";" and the "Part of Plinth Toolkit" tag) does not materially weaken any rubric dimension.

Dimension	Reasoning	Score
Specificity	The description enumerates many concrete capabilities — "Micronaut.run bootstrap, @Singleton/@Prototype, @Factory beans, @ConfigurationProperties, environments, @Requires, @Controller vs services, @Scheduled, graceful shutdown, @ExecuteOn for blocking work" — which matches the anchor for listing multiple specific concrete actions, not merely naming a domain.	3 / 3
Completeness	It answers both "what" (the enumerated Micronaut capabilities) and "when" with explicit triggers ("Use when building or reviewing Micronaut applications" plus the "This should trigger for requests such as..." clause), satisfying the highest anchor.	3 / 3
Trigger Term Quality	It provides 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"), giving good coverage of natural trigger terms.	3 / 3
Distinctiveness Conflict Risk	Every trigger is Micronaut-specific and the capability list carves a clear niche (Micronaut DI/config/HTTP/operations), making it unlikely to fire for an unrelated skill.	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.