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

Quality

81%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

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 clear validation checkpoints and appropriate safety constraints, which is its strongest aspect. However, it lacks concrete code examples and actionable content in the body itself, deferring nearly everything to an external reference file. The content is moderately concise but includes some unnecessary enumeration of concepts Claude already understands.

Suggestions

Add at least one concrete, executable code example inline (e.g., a minimal @MappedEntity + CrudRepository pair) so the skill is actionable without requiring the reference file.

Trim the 'What is covered' bullet list — Claude doesn't need a table of contents of annotation names; instead, show a quick-start pattern that demonstrates the key concepts.

Consider inlining a brief 'good vs bad' code snippet for the most common pattern (e.g., @Transactional usage) to make the skill immediately useful.

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 changes. The edge cases for ambiguity, missing context, and conflicting constraints add good error-handling guidance.	3 / 3
Progressive Disclosure	The skill correctly references a single external file (references/512-frameworks-micronaut-data.md) for detailed guidance, which is good one-level-deep disclosure. However, since no bundle files were provided, we cannot verify the reference exists, and the SKILL.md itself contains very little substantive content — it's almost entirely a wrapper pointing elsewhere with no quick-start examples inline.	2 / 3
	Total	9 / 12 Passed

Description

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 thoroughly covers specific capabilities, includes natural trigger terms, explicitly states when to use it (and when not to), and clearly distinguishes itself from a closely related skill. The explicit boundary-drawing with the JDBC skill is particularly effective for disambiguation. The description uses appropriate third-person/imperative voice throughout.

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' (opens with 'Use when', provides explicit trigger examples like 'Review or implement Micronaut Data repositories', and even clarifies when NOT to use it by pointing to the JDBC skill for raw java.sql access).	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 includes example trigger phrases like 'Review or implement Micronaut Data repositories and entities'.	3 / 3
Distinctiveness Conflict Risk	Highly distinctive — explicitly differentiates itself from the related @511-frameworks-micronaut-jdbc skill for raw java.sql access, carving out a clear niche for Micronaut Data's repository-based approach. The specific framework and pattern references make conflicts with other skills very unlikely.	3 / 3
	Total	12 / 12 Passed

Validation

100%

Warnings & errors only

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: 0d8350f

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.