416-frameworks-quarkus-mongodb-migrations-mongock

Use when you need to add or review Mongock MongoDB data migrations in a Quarkus application — including the Quarkiverse Mongock extension, Quarkus MongoDB client configuration, migrate-at-start, @ChangeUnit classes, lock/transaction settings, and Quarkus test verification. This should trigger for requests such as Add Mongock migrations in Quarkus; Configure quarkus-mongock; Review Quarkus MongoDB data migrations; Create Mongock change units for Quarkus MongoDB; Review Mongock migration ordering in a Quarkus service. Part of Plinth Toolkit

Quality

89%

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 overview skill with explicit compile-before/verify-after validation, concrete build commands, and clean one-level-deep reference navigation. The main weaknesses are duplicated compatibility and trigger-list content, and the absence of any inline @ChangeUnit code example or fix-and-retry recovery loop.

Suggestions

Consolidate the extension-compatibility guidance that currently appears in both the Constraints section and Workflow step 2 into a single location to remove the redundancy.

Drop or shorten the 'When to use this skill' section, which repeats the frontmatter description's trigger list verbatim, or fold it into the coverage list.

Add a minimal inline @ChangeUnit example (e.g., one class showing @Execution and a rollback method) so step 3's guidance is executable without opening the references, and replace 'stop immediately' with a fix-and-revalidate recovery instruction.

Dimension	Reasoning	Score
Conciseness	The body is efficient with no concept over-explanation, but extension-compatibility guidance appears both in the Constraints section ('EXTENSION COMPATIBILITY: Before adding quarkus-mongock, verify the latest Quarkiverse Mongock release...') and again in Workflow step 2, and 'When to use this skill' duplicates the description's trigger list verbatim.	4 / 5
Actionability	Concrete commands ('./mvnw compile', 'mvn clean verify'), exact config keys ('quarkus.mongock.*', 'migrate-at-start'), and named artifacts (@ChangeUnit, @Execution) are present, but step 3's 'Implement/refactor @ChangeUnit classes with idempotent operations, explicit ordering, rollback hooks' stays abstract with no inline example, delegating all code detail to the references.	4 / 5
Workflow Clarity	A clear 4-step sequence with explicit validation before (MANDATORY compile) and after (VERIFY) changes, plus stop-on-failure. However 'If compilation fails, stop immediately' halts rather than establishing a fix-and-retry feedback loop, which the guidelines stress for database operations.	4 / 5
Progressive Disclosure	Verified against the actual bundle: all three references/ files (mongock.md, antipatterns.md, parallel-change.md) exist and are cited in Workflow step 1 and again as clearly-signaled one-level-deep markdown links in the Reference section, while SKILL.md stays a concise overview.	5 / 5
	Total	17 / 20 Passed

Description

95%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 with comprehensive, concrete capability coverage and explicit, natural trigger phrases that clearly delimit the skill's niche. Its only defect is second-person phrasing ('Use when you need to'), which slightly weakens the otherwise fully specific capability statement.

Suggestions

Rephrase in third-person voice, e.g., 'Use when adding or reviewing Mongock MongoDB data migrations in a Quarkus application...' — 'Use when you need to' is second person and costs the specificity dimension a point under the rubric.

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete actions comprehensively ('add or review Mongock MongoDB data migrations... including the Quarkiverse Mongock extension, Quarkus MongoDB client configuration, migrate-at-start, @ChangeUnit classes, lock/transaction settings, and Quarkus test verification'), matching the level-5 anchor, but 'Use when you need to' is second-person voice, which the guidelines penalize by reducing specificity by 1.	4 / 5
Completeness	It explicitly answers both questions: a full 'what' (the enumerated extension, configuration, change-unit, lock/transaction, and test-verification capabilities) and an explicit 'when' ('Use when you need to add or review... This should trigger for requests such as...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural user phrasings are comprehensively covered: 'Add Mongock migrations in Quarkus; Configure quarkus-mongock; Review Quarkus MongoDB data migrations; Create Mongock change units for Quarkus MongoDB; Review Mongock migration ordering in a Quarkus service' — these are exactly the requests a user would voice, with synonym variation.	5 / 5
Distinctiveness Conflict Risk	Mongock migrations in Quarkus is a clear niche, and every trigger phrase names Mongock explicitly, so even with a sibling general Quarkus-MongoDB skill the 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/416-frameworks-quarkus-mongodb-migrations-mongock/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.