CtrlK
BlogDocsLog inGet started
Tessl Logo

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

72

Quality

89%

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

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.

The body is well-organized with a clear workflow, explicit compile/verify validation gates, and exemplary progressive disclosure to three real reference files. The main gaps are minor redundancy with the description's triggers and the absence of an inline @ChangeUnit code example.

Suggestions

Add one minimal copy-paste @ChangeUnit example (with @Execution and a rollback hook) in the body so the core task is actionable without opening a reference.

Replace the stop-on-failure instruction with an explicit fix-and-re-validate loop ('review the error, fix, re-run compile, only proceed when it passes') to reach full feedback-loop clarity.

Drop or compress the 'When to use this skill' section since its bullets duplicate the description's trigger phrases, reclaiming token budget.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence, but the 'When to use this skill' section duplicates the trigger phrases already in the description, and the Constraints block partially restates reference-file constraints, offering minor trim opportunities.

4 / 5

Actionability

Concrete commands ('./mvnw compile', 'mvn clean verify') and specific API/config tokens ('quarkus.mongock.*', 'migrate-at-start', '@ChangeUnit', '@Execution') are present, but the body shows no copy-paste @ChangeUnit code example — that detail is deferred to references.

4 / 5

Workflow Clarity

A clear four-step sequence with explicit validation checkpoints (MANDATORY compile before, SAFETY stop on failure, VERIFY after) is provided, but the recovery loop is 'stop immediately' rather than an explicit fix-and-re-validate retry cycle.

4 / 5

Progressive Disclosure

The body is a concise overview with three clearly signaled, one-level-deep reference links (all verified to exist), listed in both Workflow step 1 and a dedicated Reference section, with detailed rules/examples/antipatterns appropriately split into separate files.

5 / 5

Total

17

/

20

Passed

Description

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

The description is comprehensive and well-structured, clearly stating both capabilities and explicit trigger phrases in third-person imperative voice. It is highly specific to its niche and proactively disambiguates from the related Quarkus MongoDB skill.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities — 'Quarkiverse Mongock extension, Quarkus MongoDB client configuration, migrate-at-start, @ChangeUnit classes, lock/transaction settings, and Quarkus test verification' — giving comprehensive coverage rather than vague abstractions.

5 / 5

Completeness

Explicitly answers both 'what' (add/review Mongock MongoDB data migrations with enumerated sub-tasks) and 'when' ('Use when you need to... This should trigger for requests such as...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Provides explicit natural request phrases users would say ('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'), covering the common phrasings comprehensively.

5 / 5

Distinctiveness Conflict Risk

Narrowly niched to Mongock + Quarkus + MongoDB migrations, and explicitly routes general Quarkus MongoDB persistence to '@415-frameworks-quarkus-mongodb', minimizing overlap with sibling skills.

5 / 5

Total

20

/

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.

Validation16 / 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.