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. Covers JDBC/JPA-style Micronaut Data in one prompt (no separate 511 JDBC rule). 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 and comprehensive capability listing. The main weakness is that trigger terms are heavily technical/framework-specific, which may not match how users naturally phrase requests (e.g., 'help me set up database access' vs '@MappedEntity'). The description correctly uses third person voice throughout.
Suggestions
Add natural language trigger terms alongside technical ones, such as 'database access', 'ORM', 'persistence layer', 'data repositories', or 'database entities' to capture how users might phrase requests
| 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. These are highly specific technical capabilities. | 3 / 3 |
Completeness | Has explicit 'Use when' clause at the start that specifies the trigger condition ('when you need data access with Micronaut Data'), and comprehensively lists what it does (entity mapping, repositories, queries, transactions, testing). Both what and when are clearly answered. | 3 / 3 |
Trigger Term Quality | Includes relevant technical terms like 'Micronaut Data', 'CrudRepository', '@Query', 'Testcontainers', but these are framework-specific jargon. Missing natural user phrases like 'database access', 'ORM', 'persistence', or 'data layer' that users might actually say. | 2 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear niche: specifically targets Micronaut Data framework with explicit mention that it covers 'JDBC/JPA-style Micronaut Data in one prompt (no separate 511 JDBC rule)'. The framework-specific annotations and tools make it unlikely to conflict with generic database 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 skill is well-structured with excellent conciseness and clear workflow validation steps. The main weakness is the lack of inline executable code examples - the skill describes what it covers but delegates all concrete implementation guidance to a reference file, reducing immediate actionability.
Suggestions
Add at least one minimal executable code example showing a basic @MappedEntity and @Repository pattern inline
Include a brief code snippet demonstrating @Transactional usage on a service to make the skill immediately actionable without requiring reference file access
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, listing only what Claude needs to know without explaining basic concepts. The bullet points are terse and assume Claude understands Micronaut Data terminology. | 3 / 3 |
Actionability | Provides clear constraints with specific commands (./mvnw compile, mvn clean verify) but lacks executable code examples. The skill relies entirely on a reference file for actual implementation guidance. | 2 / 3 |
Workflow Clarity | Clear sequence with explicit validation checkpoints: compile before changes, stop on failure, verify after. The MANDATORY/SAFETY/VERIFY structure provides a clear feedback loop for error recovery. | 3 / 3 |
Progressive Disclosure | Well-structured overview with clear sections and a single-level reference to detailed documentation. The skill appropriately keeps the overview concise while pointing to the reference file for detailed rules and examples. | 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.
- Repository
- jabrena/cursor-rules-java
- Commit
a886986
- 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.