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. Part of cursor-rules-java project
76
70%
Does it follow best practices?
Impact
—
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 well-crafted skill description with strong trigger terms and explicit 'Use when' and 'trigger for' clauses that make it highly selectable. Its main weakness is that the specific capabilities are described more as configuration topics than concrete actions. The description is distinctive and would be easy for Claude to correctly select from a large skill set.
Suggestions
Reframe configuration topics as concrete actions, e.g., 'Creates versioned migration scripts, validates naming conventions (V1__description.sql), configures migrate-at-start behavior, and reviews migration ordering.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (Flyway database migrations in Quarkus) and mentions several specific concepts (quarkus-flyway extension, db/migration scripts, quarkus.flyway.* configuration, migrate-at-start, JDBC/Panache alignment), but it doesn't clearly list multiple concrete actions — it's more about configuration topics than discrete actions like 'create migration scripts, validate naming conventions, configure migration execution order'. | 2 / 3 |
Completeness | The description explicitly answers both 'what' (add or review Flyway database migrations, configure quarkus-flyway extension, db/migration layout) and 'when' with a clear 'Use when...' clause and a 'This should trigger for requests such as...' section providing explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'Flyway', 'database migrations', 'Quarkus', 'quarkus-flyway', 'db/migration', 'migrate-at-start', 'JDBC', 'Panache'. These are the exact terms a developer would use when asking about this topic. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — the combination of Flyway + Quarkus + specific configuration properties creates a very clear niche that is unlikely to conflict with other skills. Even a general 'database' or 'Quarkus' skill would be distinguishable from this. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is a lightweight procedural wrapper that defers nearly all substantive guidance to an external reference file. While it has reasonable structure and safety constraints, it lacks concrete examples (SQL migration naming, configuration snippets, common patterns) that would make it actionable on its own. The workflow steps are generic and could apply to almost any Quarkus skill, reducing their value for Flyway-specific tasks.
Suggestions
Add at least one concrete SQL migration example (e.g., V1__create_users_table.sql) and a quarkus.flyway.* configuration snippet directly in the skill body so Claude has copy-paste-ready patterns without needing to read the reference file.
Make the workflow Flyway-specific: include a validation step for migration file naming conventions (V{version}__{description}.sql) and a checkpoint to verify Flyway executed successfully (e.g., checking Flyway history table or startup logs).
Remove or condense the 'What is covered' section — the bullet list largely restates the skill description and adds tokens without actionable value.
Add a brief 'Common mistakes' or 'Bad patterns' section inline (e.g., using repeatable migrations when versioned are needed, wrong migration directory) to provide immediate value beyond the reference file.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill has some unnecessary padding — the 'What is covered' bullet list and 'Scope' line add little value since the reference file contains the actual details. The edge case bullets are somewhat boilerplate. However, it's not egregiously verbose. | 2 / 3 |
Actionability | The skill provides concrete commands (./mvnw compile, mvn clean verify) but lacks any executable code examples, SQL migration templates, or specific configuration snippets. All substantive guidance is deferred to the reference file, leaving the skill itself as mostly procedural direction without copy-paste-ready content. | 2 / 3 |
Workflow Clarity | The workflow has a clear 4-step sequence with compilation checks before and verification after, but the steps are generic (read reference, gather scope, apply changes, verify). There's no explicit validation checkpoint between steps 3 and 4 for the migration itself (e.g., checking migration naming, verifying Flyway execution), and the feedback loop for failed verification is not spelled out. | 2 / 3 |
Progressive Disclosure | The skill correctly references a single external file (references/413-frameworks-quarkus-db-migrations-flyway.md) and cross-references related skills. However, since no bundle files were provided, we cannot verify the reference exists. The skill itself is thin — almost all substance is deferred to the reference, making the SKILL.md feel like a wrapper rather than a useful overview with key patterns inline. | 2 / 3 |
Total | 8 / 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
762cb86
- 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.