512-frameworks-micronaut-data
Use when you need data access with Micronaut Data — @MappedEntity, CrudRepository/PageableRepository, @Query with parameters, @Transactional services, projections, @Version, and @MicronautTest with TestPropertyProvider and Testcontainers. For raw java.sql access without generated repositories, use @511-frameworks-micronaut-jdbc. 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/512-frameworks-micronaut-data/SKILL.mdQuality
Discovery
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.
This is an excellent skill description that clearly enumerates specific Micronaut Data capabilities, includes natural trigger terms developers would use, explicitly states when to use it, and even provides guidance on when NOT to use it (directing to the JDBC skill instead). The only minor note is the trailing 'Part of the skills-for-java project' which adds little selection value but doesn't detract significantly.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and concepts: @MappedEntity, CrudRepository/PageableRepository, @Query with parameters, @Transactional services, projections, @Version, and @MicronautTest with TestPropertyProvider and Testcontainers. Very detailed enumeration of capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (data access with Micronaut Data including specific annotations and patterns) and 'when' (opens with 'Use when you need data access with Micronaut Data'). Also explicitly distinguishes from a related skill (@511-frameworks-micronaut-jdbc for raw java.sql access), providing negative trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes highly relevant natural keywords a developer would use: 'Micronaut Data', '@MappedEntity', 'CrudRepository', 'PageableRepository', '@Query', '@Transactional', 'projections', '@Version', '@MicronautTest', 'Testcontainers'. These are the exact terms a Java developer would mention when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche (Micronaut Data ORM-style repositories) and explicitly differentiates itself from the related JDBC skill, reducing conflict risk. The specific annotations and framework terms make it very unlikely to trigger incorrectly. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill is well-structured with good progressive disclosure and a clear reference link, but it is essentially a thin pointer to an external file with almost no actionable content in the body itself. It lacks any concrete code examples, specific patterns, or executable guidance that would make it useful without reading the reference. The workflow steps are present but generic.
Suggestions
Add at least one concrete, executable code example in the body (e.g., a minimal @MappedEntity + @Repository definition) so the skill is actionable without requiring the reference file.
Include a specific 'Quick Start' or 'Common Pattern' section showing a copy-paste-ready entity, repository, and service with @Transactional.
Remove or condense the 'What is covered' bullet list — it reads like a table of contents for the reference file and adds little value in the skill body itself.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The 'What is covered in this Skill?' bullet list is somewhat redundant with the description and reference file. The constraints section is reasonably tight, but the overall content could be leaner by removing the summary list and letting the reference file handle details. | 2 / 3 |
Actionability | There are no concrete code examples, no executable commands beyond generic mvnw invocations, and no specific patterns shown. The skill entirely defers to a reference file for 'detailed rules and examples,' leaving the body itself vague and non-actionable. | 1 / 3 |
Workflow Clarity | The constraints section provides a reasonable sequence (compile → check → verify) with a stop-on-failure checkpoint, but it lacks explicit feedback loops for error recovery and the steps are generic rather than tied to specific Micronaut Data operations. | 2 / 3 |
Progressive Disclosure | The skill provides a clear overview with a well-signaled, one-level-deep reference to the detailed file. The structure is clean with distinct sections for constraints, when to use, and the reference link. | 3 / 3 |
Total | 8 / 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.