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

85%

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

71%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-structured router: correct progressive disclosure to a real one-level-deep reference, explicit validation commands around persistence changes, and a clear workflow. Weaknesses are token redundancy (the "When to use" section duplicates the description) and vague, non-domain-specific middle workflow steps.

Suggestions

Remove the "When to use this skill" section or replace it with a one-line pointer — it duplicates the description's five trigger phrases verbatim and adds no new information to the loaded context.

Make workflow step 2 Micronaut-specific (e.g., "Inspect build dependencies to determine JDBC vs JPA backend and existing entity/repository packages") instead of the generic "Identify requested outcomes, constraints, and the minimum safe set of changes".

Consider adding a stop-if-fails-then-fix-and-recompile feedback loop to the verification step so failed builds route back to remediation rather than just stopping.

Dimension	Reasoning	Score
Conciseness	The coverage list and constraints are tight, but the "When to use this skill" section repeats the description's five trigger phrases verbatim and workflow steps like "Identify requested outcomes, constraints, and the minimum safe set of changes to apply" are generic filler that could be trimmed or tightened.	3 / 5
Actionability	Concrete executable commands are present ("Run `./mvnw compile` or `mvn compile`", "Run `./mvnw clean verify` or `mvn clean verify`") plus a concrete directive to "Read `references/512-frameworks-micronaut-data.md`". Falls short of 5 because steps 2 and 4 ("Gather scope and decide target improvements", "summarize what changed") are abstract and all domain detail is delegated to the reference.	4 / 5
Workflow Clarity	A clear 4-step sequence (read reference → gather scope → apply → verify) with explicit checkpoints: MANDATORY compile before changes, "If compilation fails, stop immediately", and VERIFY after. Not 5 because there is no fix-and-retry feedback loop — it stops on failure rather than iterating — and step 2's checkpoint is implicit.	4 / 5
Progressive Disclosure	Verified against the actual bundle: a short overview body with a well-signaled single reference (references/512-frameworks-micronaut-data.md) that exists, is one level deep with no nested references, and is linked from both the Workflow and Reference sections — matching the top anchor exactly.	5 / 5
	Total	16 / 20 Passed

Description

92%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.

A strong description: it states comprehensive concrete capabilities, gives an explicit "Use when" trigger with five enumerated example requests, and disambiguates a sibling skill. The only weakness is a handful of missing natural synonyms (e.g., JPA, database) in the trigger vocabulary.

Dimension	Reasoning	Score
Specificity	The description enumerates concrete, comprehensive capabilities — "@MappedEntity, CrudRepository/PageableRepository, @Query with parameters, @Transactional services, projections, @Version, and @MicronautTest with TestPropertyProvider and Testcontainers" — covering entities, repositories, queries, transactions, pagination, locking, and testing with no significant gaps.	5 / 5
Completeness	It explicitly answers both "what" (annotation-level capability list) and "when" — "Use when you need data access with Micronaut Data" plus "This should trigger for requests such as Review or implement Micronaut Data repositories and entities..." with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural phrases users would say are well covered ("Micronaut Data repositories and entities", "transactions, pagination, or projections", "optimistic locking", "pageable queries"), but a few natural synonyms such as "JPA", "database", or ORM/DAO phrasing are missing, keeping it just below comprehensive.	4 / 5
Distinctiveness Conflict Risk	Clear niche (Micronaut Data) with explicit disambiguation against the sibling skill — "For raw java.sql access without generated repositories, use @511-frameworks-micronaut-jdbc" — minimizing wrong-skill triggers.	5 / 5
	Total	19 / 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: dca88dc

Reviewed: 3 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.