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; Model Micronaut Data entities and repositories; Review Micronaut Data transactions and pageable queries; Improve projections or optimistic locking with Micronaut Data. Part of Plinth Toolkit

Quality

94%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

88%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a well-organized, token-efficient overview that delegates detail to a real one-level reference and includes compile/verify checkpoints for persistence changes. Main weakness is that no inline code examples are provided, relying entirely on the reference for executable patterns.

Suggestions

Add 1-2 short inline entity/repository code snippets (e.g., a minimal @MappedEntity + CrudRepository pair) so the most common pattern is actionable without opening the reference.

Make the error-recovery feedback loop explicit (e.g., 'If mvn compile fails, fix the error and re-run compile before continuing') to turn the implicit retry into a stated checkpoint.

Consider trimming the duplicated 'When to use this skill' list, which repeats the trigger phrases already present in the description frontmatter.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence: a short topic list, tight constraints, and a brief numbered workflow with no padding or explanations of concepts Claude already knows. Every line earns its place.	5 / 5
Actionability	Concrete executable commands are present ('./mvnw compile', 'mvn clean verify') and the reference path is explicit, but the body itself contains no code examples or entity/repository snippets — those live entirely in the reference file, leaving minor gaps for the common cases.	4 / 5
Workflow Clarity	A clear four-step sequence is given with explicit compile-before and verify-after checkpoints and a stop-on-failure guard for the destructive/batch persistence changes. It is not a 5 because the error-recovery feedback loop (compile fails -> fix -> recompile) is implicit rather than spelled out.	4 / 5
Progressive Disclosure	The SKILL.md is an overview that cleanly offloads detailed rules and examples to a single one-level-deep reference file (references/512-frameworks-micronaut-data.md, which exists), signaled with a clear markdown link and a 'BEFORE APPLYING: Read the reference' instruction.	5 / 5
	Total	18 / 20 Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is strong across all dimensions: it enumerates concrete capabilities, supplies natural trigger phrases, answers both 'what' and 'when', and draws a clear boundary against sibling JDBC/migration skills. Only minor improvement is possible.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions and capabilities: '@MappedEntity, CrudRepository/PageableRepository, @Query with parameters, @Transactional services, projections, @Version' with specific test tooling, giving comprehensive coverage of the domain.	5 / 5
Completeness	Explicitly answers both 'what' (data access with Micronaut Data plus enumerated capabilities) and 'when' via the 'Use when you need...' opening clause and the 'This should trigger for requests such as...' list of concrete triggers.	5 / 5
Trigger Term Quality	Provides extensive natural trigger phrases users would say, including 'Review or implement Micronaut Data repositories and entities', 'Add transactions, pagination, or projections', 'Model Micronaut Data entities and repositories', with full sample request strings and a sibling-skill redirect.	5 / 5
Distinctiveness Conflict Risk	The skill is scoped tightly to Micronaut Data generated repositories and explicitly disambiguates the raw JDBC case via the '@511-frameworks-micronaut-jdbc' pointer, giving it a clear niche with minimal conflict risk.	5 / 5
	Total	20 / 20 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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: jabrena/plinth
Path: skills/512-frameworks-micronaut-data/SKILL.md
Commit: 77b8825

Reviewed: about 23 hours 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.