CtrlK
BlogDocsLog inGet started
Tessl Logo

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

73

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

80%

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

A lean, well-structured overview body with a strong validation-gated workflow and a single one-level reference. Its only gap is that the body itself carries no executable code examples, deferring all concrete patterns to the reference file.

Suggestions

Add 1–2 minimal inline code examples (e.g., a thin main with Micronaut.run, or a @Factory bean) so the body is directly actionable without opening the reference.

Consider including one concrete good/bad snippet for @Requires vs env branching, since the body emphasizes that pattern but shows none of it.

DimensionReasoningScore

Conciseness

The 67-line body is lean and assumes Claude's competence: bullet lists of capabilities, concrete constraints, and a short workflow with no padding or explanation of basic concepts.

3 / 3

Actionability

It provides some concrete commands (./mvnw compile, mvn clean verify) and concrete pointers, but the body itself contains no executable code examples or concrete refactoring patterns — those live in the reference, so on its own the guidance is incomplete.

2 / 3

Workflow Clarity

A clear 4-step workflow with an explicit pre-change compilation gate ('MANDATORY: run mvn compile before applying'), a blocking stop condition, and a post-change verification step — an explicit feedback loop for risky edits.

3 / 3

Progressive Disclosure

The SKILL.md is an overview that cleanly points to a single one-level-deep reference (references/501-frameworks-micronaut-core.md, which exists), with a well-signaled link and no nested references.

3 / 3

Total

11

/

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.

The description is specific, trigger-rich, and explicitly answers both what and when, with a clear Micronaut niche. It is somewhat verbose and contains a stray duplicated semicolon, but no rubric dimension is materially weakened by that.

Suggestions

Trim the redundant trigger list (the 'Use when...' clause and the trailing semicolon-delimited sentences overlap) to reduce verbosity without losing triggers.

Remove the stray duplicated ';' before 'Review Micronaut dependency injection scopes' for a cleaner sentence.

DimensionReasoningScore

Specificity

Lists many concrete capabilities and APIs (Micronaut.run bootstrap, @Singleton/@Prototype, @Factory beans, @ConfigurationProperties, @Requires, @Controller vs services, @Scheduled, @ExecuteOn, Jakarta-consistent APIs), matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

Starts with 'Use when building or reviewing Micronaut applications' (explicit when) and details what it covers, then closes with concrete trigger sentences, so both what and when are explicitly answered.

3 / 3

Trigger Term Quality

Repeats natural trigger phrases a user would say ('Review Java code for Micronaut application structure and beans', 'Apply best practices for Micronaut configuration', 'Improve scheduling, shutdown, or threading in Micronaut services'), giving good coverage of natural request phrasings.

3 / 3

Distinctiveness Conflict Risk

Tightly scoped to the Micronaut framework niche with framework-specific triggers (@Requires, @Factory, Micronaut.run), making it unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
jabrena/cursor-rules-java
Reviewed

Table of Contents

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.