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. Part of the skills-for-java project
79
73%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/413-frameworks-quarkus-db-migrations-flyway/SKILL.mdQuality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a solid skill description with strong trigger terms and clear 'when' guidance. Its main weakness is that the 'what' portion could be more specific about concrete actions beyond 'add or review' — for example, listing actions like creating versioned migration scripts, configuring flyway properties, or troubleshooting migration failures. The description also uses second person ('you need to') which is slightly off from the preferred third person voice, though this is a minor issue.
Suggestions
Expand the concrete actions beyond 'add or review' — e.g., 'Creates versioned migration SQL scripts, configures quarkus.flyway.* properties, troubleshoots migration failures, and ensures alignment with JDBC/Panache entities.'
Rephrase to third person voice: instead of 'Use when you need to add or review', use 'Adds and reviews Flyway database migrations... Use when working with Flyway migrations in a Quarkus application.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (Flyway database migrations in Quarkus) and mentions some specific elements (quarkus-flyway extension, db/migration scripts, quarkus.flyway.* configuration, migrate-at-start), but it frames them more as context/keywords than as concrete actions. The actions are limited to 'add or review' migrations. | 2 / 3 |
Completeness | The description explicitly answers both 'what' (add or review Flyway database migrations, quarkus-flyway extension, db/migration scripts, configuration) and 'when' (starts with 'Use when you need to add or review Flyway database migrations in a Quarkus application'), providing clear trigger guidance. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms a user would mention: 'Flyway', 'database migrations', 'Quarkus', 'quarkus-flyway', 'db/migration', 'migrate-at-start', 'JDBC', 'Panache'. These are terms a developer would naturally use when working in this domain. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — the combination of Flyway + Quarkus + specific configuration properties (quarkus.flyway.*, migrate-at-start) creates a very clear niche that is unlikely to conflict with other skills, even in a large skill library. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill is well-structured with good progressive disclosure and clear safety constraints including compile/verify checkpoints. However, it lacks concrete actionable examples (e.g., a sample migration file, application.properties snippet) in the main body, deferring almost all substantive content to the reference file. This makes the SKILL.md itself feel like a thin pointer rather than a useful quick-start guide.
Suggestions
Add a minimal concrete example showing a versioned migration file (e.g., V1__create_table.sql) and the corresponding quarkus.flyway.* configuration in application.properties.
Include a brief quick-start workflow with numbered steps: add dependency, create migration file, configure properties, run — rather than only compile/verify guards.
Remove the 'What is covered in this Skill?' bullet list or merge it into the description to reduce redundancy and improve conciseness.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The 'What is covered in this Skill?' section is somewhat redundant with the description and could be tightened. The bullet list explaining scope is mildly verbose but not egregiously so. The 'Scope' line restates what's already implied. | 2 / 3 |
Actionability | Provides concrete commands (./mvnw compile, mvn clean verify) which is good, but lacks any executable code examples for actual Flyway migration setup, configuration snippets, or SQL migration file examples. The real content is deferred entirely to the reference file. | 2 / 3 |
Workflow Clarity | There is a clear compile-before/verify-after sequence with a stop-on-failure checkpoint, which is good. However, the actual migration workflow steps (creating migration files, configuring properties, testing) are absent from this file and fully deferred to the reference, leaving gaps in the visible workflow. | 2 / 3 |
Progressive Disclosure | Clean structure with a concise overview, clear sections, and a single well-signaled reference link to the detailed guide. One level deep, easy to navigate. | 3 / 3 |
Total | 9 / 12 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 — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- jabrena/cursor-rules-java
- Commit
d3c81ef
- 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.