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
88
85%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
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 with excellent specificity and completeness, including an explicit 'Use when' clause. The main weakness is that trigger terms are heavily technical (annotation names) rather than natural language users might employ when seeking help. The description could benefit from including more user-friendly terms alongside the technical ones.
Suggestions
Add natural language trigger terms users might say, such as 'dependency injection', 'microservices framework', 'REST endpoints', or 'configuration management' alongside the technical annotations.
| 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. | 3 / 3 |
Completeness | Explicitly answers both what (the list of Micronaut concepts and features) and when ('Use when building or reviewing Micronaut applications') with a clear trigger clause at the beginning. | 3 / 3 |
Trigger Term Quality | Includes 'Micronaut applications' and specific annotations like @Singleton, @Controller, @Scheduled which are relevant but highly technical. Missing common user phrases like 'dependency injection', 'microservices', 'REST API', or simpler terms users might naturally say. | 2 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear Micronaut-specific terminology and annotations. The explicit mention of 'Micronaut' and framework-specific concepts like @ConfigurationProperties, @Requires, and Micronaut.run bootstrap make it unlikely to conflict with generic Java or other framework skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured skill that excels at organization, conciseness, and workflow clarity with explicit compilation checkpoints. The main weakness is that actionability relies entirely on the referenced file for concrete code examples, making the skill body more of a navigation document than a standalone actionable guide.
Suggestions
Add 1-2 minimal executable code examples in the body (e.g., a thin @Controller delegating to @Singleton service, or @ConfigurationProperties usage) to improve actionability without requiring reference file access
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, using bullet points to list covered topics without explaining what Micronaut is or how DI works. Every line serves a purpose and assumes Claude's competence with Java frameworks. | 3 / 3 |
Actionability | The skill provides clear constraints and verification commands (./mvnw compile, ./mvnw clean verify), but lacks concrete code examples in the body itself. All detailed guidance is deferred to the reference file, making the skill more of a pointer than executable guidance. | 2 / 3 |
Workflow Clarity | Clear workflow with explicit validation checkpoints: compile before changes, stop if compilation fails, verify after changes. The MANDATORY/PREREQUISITE/SAFETY/VERIFY structure provides an unambiguous sequence with feedback loops. | 3 / 3 |
Progressive Disclosure | Excellent structure with a concise overview, clear scope definition, constraints section, and a single well-signaled reference to detailed documentation. One-level-deep reference pattern is properly implemented. | 3 / 3 |
Total | 11 / 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.
a886986
Table of Contents
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.