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. This should trigger for requests such as Review or implement Micronaut Data repositories and entities; Add transactions, pagination, or projections in Micronaut persistence layer. Part of cursor-rules-java project
68
81%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Quality
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 covers all key dimensions well. It enumerates specific capabilities, provides natural trigger terms, explicitly states both what and when, and even includes boundary guidance to distinguish it from a closely related skill. The only minor note is that it's somewhat dense, but the information density is appropriate for disambiguation among many skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and concepts: @MappedEntity, CrudRepository/PageableRepository, @Query with parameters, @Transactional services, projections, @Version, @MicronautTest with TestPropertyProvider and Testcontainers. Very detailed enumeration of capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (data access with Micronaut Data including specific features) and 'when' ('Use when you need data access with Micronaut Data', 'This should trigger for requests such as...'). Also includes explicit boundary guidance distinguishing it from the JDBC skill. | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms users would say: 'Micronaut Data', 'repositories', 'entities', 'transactions', 'pagination', 'projections', 'persistence layer'. Also includes specific annotations like @MappedEntity, @Query, @Transactional that developers would reference. The example trigger phrases ('Review or implement Micronaut Data repositories and entities') are realistic. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche (Micronaut Data ORM-style repositories) and explicitly differentiates itself from the related @511-frameworks-micronaut-jdbc skill for raw java.sql access. This boundary guidance significantly reduces conflict risk. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
62%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill has a well-structured workflow with strong safety constraints and validation checkpoints, but it functions primarily as a routing document to an external reference file rather than providing standalone actionable guidance. It lacks any concrete code examples (entities, repositories, queries) that would make it immediately useful, and the bullet list of covered topics adds moderate value but borders on restating what Claude already knows about Micronaut Data annotations.
Suggestions
Add at least one concrete, executable code example showing a minimal @MappedEntity + @Repository pattern so the skill is immediately actionable without reading the reference file.
Include a brief good/bad code comparison inline (e.g., correct @Transactional usage vs. common mistake) to provide immediate value beyond the reference pointer.
Trim the 'What is covered' bullet list or convert it into a more compact table/summary — listing annotation names Claude already knows adds little value.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The 'What is covered' bullet list is somewhat useful as a scope declaration, but the edge case bullets and some phrasing are verbose. The skill explains what Micronaut Data concepts are (e.g., listing annotations) without adding much beyond what Claude already knows, though it avoids lengthy explanations of basic concepts. | 2 / 3 |
Actionability | The skill provides concrete build commands (./mvnw compile, mvn clean verify) and a clear workflow, but lacks any executable code examples for entities, repositories, or queries. All actual guidance is deferred to the reference file, making the skill itself more of a pointer than actionable instruction. | 2 / 3 |
Workflow Clarity | The four-step workflow is clearly sequenced with explicit validation checkpoints (compile before changes, stop on failure, verify after). The constraints section adds safety gates and edge case handling with feedback loops for ambiguous or failing scenarios. | 3 / 3 |
Progressive Disclosure | The skill correctly references a single external file (references/512-frameworks-micronaut-data.md) for detailed rules and examples, which is good one-level-deep disclosure. However, since no bundle files were provided to verify the reference exists, and the SKILL.md itself contains almost no substantive content beyond the pointer, it feels like too much is deferred — the overview lacks a quick-start example or any concrete code to be immediately useful. | 2 / 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
3b97275
- 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.