CtrlK
BlogDocsLog inGet started
Tessl Logo

516-frameworks-micronaut-mongodb-migrations-mongock

Use when you need to add or review Mongock MongoDB data migrations in a Micronaut application — including Mongock runner/driver selection, Micronaut bean wiring, migration scan packages, @ChangeUnit classes, lock/transaction settings, and Testcontainers verification. This should trigger for requests such as Add Mongock migrations in Micronaut; Review Micronaut MongoDB data migrations; Configure Mongock change units with Micronaut Data MongoDB; Create Mongock change units for Micronaut MongoDB; Review Mongock migration ordering in a Micronaut service. Part of Plinth Toolkit

68

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

72%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, lean overview body with real one-level-deep references and explicit compile/verify checkpoints. Its weaknesses are the missing fix-and-retry feedback loop for a database-migration workflow (capping workflow clarity at 3) and a 'When to use' section that duplicates the frontmatter description.

Suggestions

Add an explicit feedback loop for the database-migration workflow, e.g. after 'VERIFY: mvn clean verify', add 'If verification fails, fix the failing @ChangeUnit and re-run verification before proceeding' — the current 'SAFETY: stop immediately' halts without a recovery path.

Remove or trim the 'When to use this skill' section, which duplicates the frontmatter description's trigger list verbatim and costs tokens without adding guidance.

Include one minimal inline @ChangeUnit skeleton (or a pointer to the exact example section in the reference file) so workflow step 3 is executable without first opening the full reference.

DimensionReasoningScore

Conciseness

The body is efficient with no concept re-teaching, containing only minor trimmable redundancy — the 'When to use this skill' list exactly duplicates the frontmatter description's trigger phrases, and 'What is covered' overlaps it too. It sits above the score-3 anchor (which implies editorializing) but short of 5 because of that duplication.

4 / 5

Actionability

Concrete commands are given ('./mvnw compile', 'mvn compile', './mvnw clean verify'), specific files to inspect ('pom.xml', the three named reference files), and concrete artifacts (@ChangeUnit, @MicronautTest, Testcontainers). Minor gap: no inline @ChangeUnit or bean-wiring code skeleton, so step 3 relies entirely on the reference files — mostly executable guidance with minor gaps.

4 / 5

Workflow Clarity

A clear 4-step sequence exists with explicit checkpoints (MANDATORY compile before, SAFETY stop on failure, VERIFY after), but this is a database-migration skill and the rubric caps workflow_clarity at 3 when no validate→fix→retry feedback loop is present — 'If compilation fails, stop immediately' halts rather than loops, and the verify step has no 'if it fails, fix and re-run' instruction.

3 / 5

Progressive Disclosure

SKILL.md is a genuine overview; the three referenced files (main guide, antipatterns, parallel-change) all exist, are one level deep, and are clearly signaled both in workflow step 1 and in a dedicated Reference section with markdown links. Content is appropriately split with easy navigation.

5 / 5

Total

16

/

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, five natural trigger phrases, and explicit what/when structure. Its only deduction is the second-person 'Use when you need to' trigger clause, which the rubric penalizes on specificity.

Suggestions

Rewrite the trigger clause in third person or plain imperative (e.g., 'Use when adding or reviewing Mongock MongoDB data migrations in a Micronaut application') to avoid the second-person voice penalty.

DimensionReasoningScore

Specificity

The description lists six-plus concrete capabilities ('Mongock runner/driver selection, Micronaut bean wiring, migration scan packages, @ChangeUnit classes, lock/transaction settings, and Testcontainers verification'), matching the comprehensive score-5 anchor — but the opening 'Use when you need to' uses second-person voice, which the judging guidelines penalize by reducing specificity by 1.

4 / 5

Completeness

It explicitly answers both questions: the 'what' ('add or review Mongock MongoDB data migrations in a Micronaut application — including…') and the 'when' ('Use when you need to… This should trigger for requests such as…') with concrete trigger phrases, matching the score-5 anchor.

5 / 5

Trigger Term Quality

It enumerates five verbatim natural user requests ('Add Mongock migrations in Micronaut; Review Micronaut MongoDB data migrations; Configure Mongock change units with Micronaut Data MongoDB; Create Mongock change units for Micronaut MongoDB; Review Mongock migration ordering in a Micronaut service'), giving comprehensive coverage of the natural phrasings a user would actually say.

5 / 5

Distinctiveness Conflict Risk

The intersection of Mongock + Micronaut + MongoDB migrations is a clear niche with distinct triggers, and no generic language that would fire sibling skills; minimal conflict risk.

5 / 5

Total

19

/

20

Passed

Validation

100%

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
Reviewed

Table of Contents

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.