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. Part of the skills-for-java project
77
71%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/501-frameworks-micronaut-core/SKILL.mdQuality
Discovery
85%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description that clearly identifies its niche (Micronaut framework) and provides an explicit 'Use when' trigger. It excels in specificity by listing numerous concrete framework concepts and annotations, and is highly distinctive. The main weakness is that trigger terms lean heavily on framework-specific jargon rather than natural user language, which could cause it to be missed when users describe their needs in more general terms.
Suggestions
Add natural-language trigger terms users might say, such as 'microservices with Micronaut', 'Micronaut REST API', 'Micronaut project setup', or 'Micronaut dependency injection'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and concepts: Micronaut.run bootstrap, @Singleton/@Prototype, @Factory beans, @ConfigurationProperties, environments, @Requires, @Controller vs services, @Scheduled, graceful shutdown, @ExecuteOn for blocking work, and Jakarta-consistent APIs. These are highly specific, actionable topics. | 3 / 3 |
Completeness | Clearly answers both 'what' (building/reviewing Micronaut applications with specific framework features listed) and 'when' ('Use when building or reviewing Micronaut applications'). The 'Use when...' clause is explicit and appears at the start. | 3 / 3 |
Trigger Term Quality | Includes strong technical keywords like 'Micronaut', specific annotations (@Singleton, @Controller, @Scheduled, etc.), and 'Jakarta-consistent APIs'. However, these are mostly framework-specific jargon rather than natural user language — a user might say 'Micronaut app' or 'dependency injection in Micronaut' but less likely to mention '@ConfigurationProperties' directly. Missing common variations like 'microservices', 'REST API with Micronaut', or 'Micronaut project setup'. | 2 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — focuses specifically on the Micronaut framework with framework-specific annotations and concepts. Unlikely to conflict with generic Java skills, Spring skills, or other framework-specific skills. The mention of 'Part of the skills-for-java project' further contextualizes it. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is a reasonable overview/pointer document with good progressive disclosure and clear compilation safety constraints. However, it lacks any concrete code examples or patterns in the body itself, relying entirely on the reference file for actionable content. The constraints section could be tightened by deduplicating the compile-first requirement stated three different ways.
Suggestions
Add at least one concrete good/bad code example inline (e.g., constructor injection pattern or thin controller pattern) so the skill is actionable without requiring the reference file.
Restructure the constraints as a numbered workflow sequence (1. compile → 2. apply changes → 3. verify → 4. if failure, rollback) rather than a flat list of overlapping bullet points.
Consolidate the MANDATORY/PREREQUISITE/SAFETY bullets into a single clear statement to reduce redundancy.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The bullet list of what's covered is somewhat redundant with the reference file and could be trimmed. The constraints section is useful but slightly verbose with the bold labels repeating similar ideas (MANDATORY/PREREQUISITE/SAFETY all say 'must compile first'). | 2 / 3 |
Actionability | The constraints provide concrete commands (`./mvnw compile`, `./mvnw clean verify`) which is good, but the skill itself contains no code examples, no concrete patterns, and delegates everything to the reference file. A reader gets direction but not executable guidance from this file alone. | 2 / 3 |
Workflow Clarity | There is a clear pre/post workflow (compile before, verify after, stop on failure), but it's presented as a flat list of constraints rather than a sequenced workflow with explicit feedback loops. The error recovery path ('stop immediately') is mentioned but there's no guidance on what to do next. | 2 / 3 |
Progressive Disclosure | The skill provides a clear overview with a well-signaled single-level reference to the detailed file. The structure is clean: overview → constraints → when to use → reference link. This is appropriate progressive disclosure. | 3 / 3 |
Total | 9 / 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- jabrena/cursor-rules-java
- Commit
1847adc
- 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.