413-frameworks-quarkus-db-migrations-flyway

Use when you need to add or review Flyway database migrations in a Quarkus application — quarkus-flyway extension, db/migration scripts, quarkus.flyway.* configuration, migrate-at-start, and alignment with JDBC or Panache. This should trigger for requests such as Add or review Flyway migrations in a Quarkus project; Configure quarkus-flyway or db/migration layout; Add versioned Flyway SQL migrations for Quarkus; Review Quarkus database migration ordering; Configure Flyway clean migrate or baselines in Quarkus. Part of Plinth Toolkit

Quality

92%

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

85%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 with strong validation checkpoints and clean progressive disclosure into verified reference files. Its main weakness is mild redundancy between the body's trigger list and the description, and the absence of an inline migration example.

Suggestions

Remove or condense the 'When to use this skill' section since those trigger phrases already appear in the description frontmatter, avoiding token redundancy.

Add one short inline versioned-migration example (e.g., a V1__init.sql snippet and the matching quarkus.flyway.* application.properties block) so the body is self-sufficient for the most common task before deferring detail to references.

Make the verification feedback loop explicit as a numbered retry step ('if verify fails, fix and re-run mvn clean verify') rather than relying on the safety directives to imply it.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence with no padded concept explanations, but the 'When to use this skill' section duplicates the trigger phrases already in the description frontmatter, a redundancy that could be trimmed.	4 / 5
Actionability	Concrete executable commands (./mvnw compile, mvn clean verify) and specific config keys/paths (quarkus.flyway.migrate-at-start, src/main/resources/db/migration) are present, but the body defers all SQL/config code examples to references with no inline migration sample, leaving a minor gap.	4 / 5
Workflow Clarity	The four-step sequence has explicit validation checkpoints (MANDATORY compile before, 'If compilation fails, stop immediately', VERIFY after) plus a BREAKING CHANGE REVIEW human-approval gate and edge-case clarification rules, satisfying the destructive/batch feedback-loop requirement for a database-migration skill.	5 / 5
Progressive Disclosure	The body is a concise overview pointing one level deep to three real reference files (verified present in references/), each clearly signaled with markdown links in both the Workflow and a dedicated Reference section; content is appropriately split with no nested references.	5 / 5
	Total	18 / 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.

A strong, specific description that explicitly pairs what the skill does with concrete natural-language trigger phrases and niche-specific technical markers. It is comprehensive, distinct, and free of vague fluff.

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete actions across the migration lifecycle ('add or review Flyway database migrations', 'Configure quarkus-flyway or db/migration layout', 'Add versioned Flyway SQL migrations', 'Review Quarkus database migration ordering', 'Configure Flyway clean migrate or baselines'), matching the comprehensive-coverage anchor.	5 / 5
Completeness	An explicit 'Use when you need to...' clause and a 'This should trigger for requests such as...' list answer both what (extension, scripts, config, JDBC/Panache alignment) and when with concrete trigger phrases, hitting the top anchor.	5 / 5
Trigger Term Quality	It bundles natural user phrasings ('Add or review Flyway migrations in a Quarkus project', 'Configure Flyway clean migrate or baselines in Quarkus') with technical synonyms (quarkus-flyway, db/migration, migrate-at-start, quarkus.flyway.*), giving comprehensive keyword coverage; only a file-extension trigger (.sql) is absent.	5 / 5
Distinctiveness Conflict Risk	Scoping to 'Flyway database migrations in a Quarkus application' with niche triggers (quarkus-flyway, migrate-at-start, db/migration) carves a clear niche with minimal overlap, and explicit coordination with sibling skills 411-jdbc and 412-panache sharpens boundaries rather than blurring them.	5 / 5
	Total	20 / 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/cursor-rules-java
Path: skills/413-frameworks-quarkus-db-migrations-flyway/SKILL.md
Commit: 77b8825

Reviewed: about 21 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.