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
83
78%
Does it follow best practices?
Impact
—
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 covers all key dimensions well. It provides specific concrete capabilities, natural trigger terms, explicit 'Use when' and 'trigger for' clauses, and even draws a clear boundary against a closely related skill to minimize conflict. The only minor weakness is that it's somewhat dense with technical terms, but this is appropriate for its target audience.
| 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 annotations and patterns) and 'when' (explicit 'Use when' clause at the start, plus 'This should trigger for requests such as...' with concrete examples). Also includes a boundary condition 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', 'CrudRepository', 'PageableRepository'. Also provides example trigger phrases like 'Review or implement Micronaut Data repositories and entities'. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with explicit boundary drawn against the related @511-frameworks-micronaut-jdbc skill for raw java.sql access. The specific Micronaut Data annotations and repository patterns create a clear niche that is unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 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 well-structured as an overview with good progressive disclosure to a reference file, and includes useful build verification commands. However, it lacks any concrete code examples (entity definitions, repository interfaces, test patterns), making it more of a process guide than an actionable skill. The workflow steps are generic and could apply to almost any framework skill.
Suggestions
Add at least one concrete, executable code example inline — e.g., a minimal @MappedEntity + CrudRepository pair — so Claude has an immediate actionable pattern without needing to read the reference file.
Make the workflow steps more specific to Micronaut Data rather than generic (e.g., step 3 could show specific patterns like 'ensure @Repository interfaces extend CrudRepository<Entity, Long>' or 'wrap service methods in @Transactional').
Add a feedback loop in the workflow for handling compilation or test failures — e.g., 'If `mvn compile` fails, inspect error output, fix the issue, and re-run before proceeding to step 4.'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The 'What is covered' bullet list is somewhat redundant with the reference file and the workflow is generic. The constraints section has useful content but the edge case bullets feel templated and padded. Some unnecessary framing like 'Apply recommendations based on the reference rules and good/bad code examples.' | 2 / 3 |
Actionability | The skill provides concrete build commands (`./mvnw compile`, `./mvnw clean verify`) and references a detailed file, but contains zero code examples, no executable snippets for entity definitions, repository patterns, or test setup. All actual guidance is deferred to the reference file. | 2 / 3 |
Workflow Clarity | The 4-step workflow is clearly sequenced and includes a compilation check before changes and verification after, but the steps are generic (read, gather, apply, verify) without explicit validation checkpoints between steps or feedback loops for handling build failures beyond 'stop immediately.' | 2 / 3 |
Progressive Disclosure | The skill is a clean overview that lists what's covered, provides constraints and workflow, and clearly points to a single reference file for detailed rules and examples. Navigation is one level deep and well-signaled. | 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
899d988
- 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.