316-frameworks-spring-mongodb-migrations-mongock

Use when you need to add or review Mongock MongoDB data migrations in a Spring Boot application — including Maven coordinates, Spring Data MongoDB drivers, migration scan packages, @ChangeUnit classes, lock/transaction settings, and optional policy-approved MongoDB integration verification. This should trigger for requests such as Add Mongock migrations in Spring Boot; Review Spring MongoDB data migrations; Configure Mongock change units for Spring Data MongoDB; Create Mongock change units for Spring Boot MongoDB; Review Mongock migration ordering in a Spring service. Part of Plinth Toolkit

Quality

86%

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 that defers detail to references appropriately and includes strong validation discipline for destructive migration work. Main gaps are duplicated trigger/reference listings and validation that is segregated from the workflow steps rather than inline.

Suggestions

Inline one minimal @ChangeUnit example and one pom.xml Mongock BOM snippet so the most common action is executable without opening a reference file.

Fold the MANDATORY/VERIFY checkpoints directly into the Workflow steps (e.g. '5. Validate: run mvn clean verify') so the feedback loop is visible in sequence rather than only in the Constraints block.

Remove the duplicate reference-file listing in Workflow step 1 or the Reference section, and consider dropping the 'When to use' bullets since they repeat the description's triggers.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence (no explanation of what Mongock/MongoDB is), but the 'When to use' section duplicates the description's triggers and the three reference files are listed both in Workflow step 1 and the Reference section, so minor trimming is possible.	4 / 5
Actionability	Provides concrete commands ('./mvnw compile', 'mvn clean verify', 'mongock.enabled=false') and specific files to read, but the core migration code (@ChangeUnit examples, pom.xml coordinates) is deferred entirely to references rather than shown inline.	4 / 5
Workflow Clarity	A clear 4-step workflow with explicit validation checkpoints (MANDATORY compile before, SAFETY stop on failure, VERIFY after) and a checklist-style Constraints section, but validation lives in a separate Constraints block rather than being woven inline into the workflow steps as in the anchor-5 example.	4 / 5
Progressive Disclosure	The body is a concise overview pointing to three real, one-level-deep reference files (confirmed present in ./references/) via clearly signaled markdown links in the Reference section, with detailed rules appropriately split out.	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, specific description with clear what/when structure and comprehensive natural trigger phrases. The only weakness is the second-person 'you need to' phrasing instead of the recommended third-person/imperative voice.

Suggestions

Rewrite the opening in third person / imperative voice (e.g. 'Adds and reviews Mongock MongoDB data migrations in Spring Boot applications. Use when adding or reviewing...') to match the anchor examples and recover the specificity penalty.

Dimension	Reasoning	Score
Specificity	Lists many concrete capabilities ('Maven coordinates, Spring Data MongoDB drivers, migration scan packages, @ChangeUnit classes, lock/transaction settings'), which is comprehensive; reduced by 1 for second-person voice ('Use when you need to add or review') rather than the third-person form used in the anchor examples.	4 / 5
Completeness	Explicitly answers both what ('add or review Mongock MongoDB data migrations... including... lock/transaction settings') and when ('Use when you need to... This should trigger for requests such as...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Five natural trigger phrases ('Add Mongock migrations in Spring Boot; Review Spring MongoDB data migrations; Configure Mongock change units...') give comprehensive coverage of the variations a user would actually say for this domain.	5 / 5
Distinctiveness Conflict Risk	The narrow niche of 'Mongock MongoDB data migrations in a Spring Boot application' with domain-specific triggers and explicit coordination with '@315-frameworks-spring-mongodb' gives a clear niche with minimal conflict risk.	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/316-frameworks-spring-mongodb-migrations-mongock/SKILL.md
Commit: 05bf9d1

Reviewed: 8 minutes 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.