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

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

85%

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 SKILL.md body with a clear workflow, explicit compile/verify validation checkpoints, and clean one-level-deep progressive disclosure to a real reference file. Its main gap is actionability: the core MongoDB design guidance lives entirely in the reference, leaving the body with only build commands and abstract implementation directions.

Suggestions

Add one small inline executable snippet (e.g. a minimal @MongoRepository interface or an index declaration) so the body is copy-paste ready for the skill's core task rather than deferring everything to the reference.

Tighten step 3 of the workflow from 'Implement/refactor documents, repositories, indexes, and error handling' to name the specific concrete actions or link directly to the relevant reference subsections.

Dimension	Reasoning	Score
Conciseness	The body is lean (~40 lines), assumes Claude's competence, and avoids explaining concepts Claude already knows; every section earns its place, matching the level-3 'lean and efficient' anchor.	3 / 3
Actionability	Concrete executable build commands are present ('./mvnw compile', './mvnw clean verify'), but the skill's core task has no inline executable code or examples — step 3 ('Implement/refactor documents, repositories, indexes, and error handling') is abstract direction deferred to the reference, matching the level-2 'some concrete guidance but incomplete' anchor rather than copy-paste-ready level 3.	2 / 3
Workflow Clarity	A clear 4-step sequence is paired with explicit validation checkpoints and a feedback loop in the Constraints section ('Run ./mvnw compile before any change', 'If compilation fails, stop immediately', 'Run ./mvnw clean verify after applying improvements'), matching the level-3 anchor; the database-operation context is covered by present verification steps so it is not capped at 2.	3 / 3
Progressive Disclosure	The body is a concise overview that defers detail to a single one-level-deep reference, clearly signaled in both Workflow step 1 and a dedicated '## Reference' section with a markdown link to references/515-frameworks-micronaut-mongodb.md (a real file), matching the level-3 anchor.	3 / 3
	Total	11 / 12 Passed

Description

90%

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, specific description with explicit 'what' and 'when' guidance and a rich set of natural trigger phrases tied to a clearly distinct Micronaut-MongoDB niche. The only weakness is the second-person 'you need' phrasing in the trigger clause, which the rubric's voice rule penalizes.

Suggestions

Rephrase the trigger clause to third person to avoid the voice penalty, e.g. 'Use when MongoDB persistence in Micronaut is needed — including...' or 'Use when working with MongoDB persistence in Micronaut...'.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ('@MongoRepository design, document modeling, indexes, query patterns, and error handling') which meets the level-3 bar, but reduced by 1 per the rubric's voice rule because the trigger clause uses second person ('Use when you need MongoDB persistence').	2 / 3
Completeness	Explicitly answers both 'what' (MongoDB persistence capabilities in Micronaut) and 'when' with a 'Use when...' clause plus an explicit 'This should trigger for requests such as...' list, matching the level-3 anchor.	3 / 3
Trigger Term Quality	Five natural trigger phrasings users would say are given verbatim ('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'), matching the level-3 anchor of good coverage.	3 / 3
Distinctiveness Conflict Risk	The niche is tightly scoped to MongoDB persistence within Micronaut specifically ('Part of Plinth Toolkit'), with distinct triggers unlikely to fire for unrelated skills, matching the level-3 anchor.	3 / 3
	Total	11 / 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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: jabrena/plinth
Commit: aaee915

Reviewed: 1 day 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.