515-frameworks-micronaut-mongodb

Use when you need MongoDB persistence in Micronaut — including @MongoRepository design, document modeling, indexes, query patterns, and error handling. This should trigger for requests such as Add MongoDB in Micronaut; Review Micronaut Data Mongo design; Improve error handling for Micronaut Mongo operations; Model MongoDB documents for a Micronaut service; Configure Micronaut MongoDB codecs indexes or transactions. Part of Plinth Toolkit

Quality

88%

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

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

A well-structured, token-efficient overview body with explicit build/validation gates and a clean single-reference progressive-disclosure design. The main gaps are redundant repetition of the read-the-reference instruction and trigger list, and a high-level middle workflow that defers all technical substance to the reference without a fix-and-retry loop on verification failure.

Suggestions

State the read-the-reference instruction once (e.g., keep the Workflow step and drop the Constraints 'BEFORE APPLYING' bullet and/or the trailing Reference section) to remove the triple repetition.

Trim or differentiate the 'When to use this skill' list, which currently duplicates the frontmatter description's trigger phrases verbatim.

Add an explicit fix-and-retry loop after verification (e.g., 'If verify fails, fix the failing tests/compile errors and re-run mvn clean verify') to complete the error-recovery feedback cycle.

Dimension	Reasoning	Score
Conciseness	The body is lean and free of concept explanations, but the "read the reference" instruction is stated three times (Constraints' "BEFORE APPLYING", Workflow step 1, and the Reference section) and the "When to use this skill" list duplicates the frontmatter trigger phrases. These minor redundancies keep it below the top 'every token earns its place' anchor.	4 / 5
Actionability	It provides concrete executable commands ("./mvnw compile or mvn compile", "./mvnw clean verify or mvn clean verify") and an explicit reference path, with a clear stop-on-failure rule. It is not 5 because the workflow's middle steps ("Gather scope and decide target improvements", "Apply framework-aligned changes") remain high-level and delegate all technical specifics to the reference.	4 / 5
Workflow Clarity	The four-step workflow is clearly sequenced with explicit checkpoints: a MANDATORY pre-change compile gate, a SAFETY stop if compilation fails, and a VERIFY step after changes. It is not 5 because the error-recovery path only says "stop immediately" — there is no fix-and-revalidate feedback loop for the post-change verify step.	4 / 5
Progressive Disclosure	The SKILL.md body is a clean overview that delegates all detail to a single, one-level-deep reference (references/515-frameworks-micronaut-mongodb.md, verified to exist), clearly signaled both as an inline path in Workflow step 1 and as a markdown link in the Reference section. No scripts or assets exist to organize, and navigation is unambiguous.	5 / 5
	Total	17 / 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 concrete capabilities in the MongoDB-in-Micronaut niche and gives explicit, natural-language trigger phrases covering add/review/improve/model/configure requests. Third-person voice is used, and only minor synonym coverage is missing.

Dimension	Reasoning	Score
Specificity	The description enumerates multiple concrete capability areas — "@MongoRepository design, document modeling, indexes, query patterns, and error handling" plus codecs and transactions in the trigger list — giving comprehensive coverage of the MongoDB-in-Micronaut domain. It is not 4 because coverage extends beyond 'several specific actions' to essentially all sub-tasks of the niche.	5 / 5
Completeness	It explicitly answers both what ("MongoDB persistence in Micronaut — including @MongoRepository design, document modeling, indexes, query patterns, and error handling") and when ("Use when you need MongoDB persistence in Micronaut… This should trigger for requests such as…") with concrete trigger phrases. This matches the top anchor exactly.	5 / 5
Trigger Term Quality	Trigger phrasings like "Add MongoDB in Micronaut", "Review Micronaut Data Mongo design", "Improve error handling for Micronaut Mongo operations", and "Model MongoDB documents for a Micronaut service" are natural user requests. It is not 5 because a few natural synonyms are missing (e.g., "Mongo repositories", "Micronaut Data MongoDB", "data access layer").	4 / 5
Distinctiveness Conflict Risk	The scope is tightly pinned to MongoDB persistence within Micronaut specifically, so it is clearly distinguishable from generic MongoDB, Micronaut, or other framework-persistence skills. Conflict risk is minimal.	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/515-frameworks-micronaut-mongodb/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.