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
56
62%
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, explicit 'Use when' and 'trigger for' clauses, and a highly distinctive niche. Its main weakness is that the specific capabilities could be more concretely enumerated (e.g., 'create versioned migration scripts, validate migration naming conventions, configure baseline-on-migrate') rather than the somewhat generic 'add or review'. The 'Part of cursor-rules-java project' suffix adds no selection value.
Suggestions
Expand the action verbs beyond 'add or review' to list more concrete capabilities like 'create versioned migration scripts, validate naming conventions, configure baseline-on-migrate, troubleshoot migration failures'.
Remove 'Part of cursor-rules-java project' as it provides no value for skill selection and adds noise.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (Flyway database migrations in Quarkus) and mentions several specific elements (quarkus-flyway extension, db/migration scripts, quarkus.flyway.* configuration, migrate-at-start, JDBC/Panache alignment), but it doesn't clearly list concrete actions beyond 'add or review'. It's more of a list of related concepts than distinct actionable capabilities. | 2 / 3 |
Completeness | The description clearly answers both 'what' (add or review Flyway database migrations, configure quarkus-flyway, db/migration layout) and 'when' with an explicit 'Use when' clause and a 'This should trigger for' clause listing specific request examples. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms a user would say: 'Flyway', 'database migrations', 'Quarkus', 'quarkus-flyway', 'db/migration', 'migrate-at-start', 'JDBC', 'Panache'. These are the exact terms a developer working in this space would use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — the combination of Flyway + Quarkus + specific configuration keys (quarkus.flyway.*) creates a very narrow 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
35%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill functions primarily as a thin wrapper around a reference file, providing almost no actionable content of its own — no SQL migration examples, no configuration snippets, no naming conventions. The workflow is structured but abstract, and the constraints section includes useful safety checks but also generic boilerplate edge cases. The skill would benefit significantly from including at least one concrete example of a Flyway migration and key configuration properties inline.
Suggestions
Add at least one concrete example of a versioned migration file (e.g., V1__create_users_table.sql) and the corresponding quarkus.flyway.* configuration in application.properties to make the skill actionable without requiring the reference file.
Replace abstract workflow steps like 'Apply framework-aligned changes' with specific actions such as 'Create migration file under src/main/resources/db/migration/ following V{version}__{description}.sql naming convention'.
Add a Flyway-specific validation checkpoint in the workflow, such as checking that migration files follow the naming convention and that quarkus.flyway.migrate-at-start is properly configured before running verification.
Trim the boilerplate edge cases to a single concise bullet and remove the 'What is covered' section, folding any unique information into the workflow or reference pointer.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill has some unnecessary padding — the 'What is covered' bullet list and scope statement are somewhat redundant with the description and reference file. The edge case handling is boilerplate-heavy. However, it's not egregiously verbose. | 2 / 3 |
Actionability | The skill provides no concrete code, SQL examples, configuration snippets, or executable commands beyond generic 'mvnw compile' and 'mvn clean verify'. All actual guidance is deferred to the reference file, leaving the skill body with only vague direction like 'Apply framework-aligned changes' and 'Implement or refactor configuration/code following the reference patterns.' | 1 / 3 |
Workflow Clarity | The workflow has a clear 4-step sequence with compilation checks before and verification after, which is good. However, the steps themselves are abstract ('Gather scope and decide target improvements', 'Apply framework-aligned changes') rather than specific, and the validation is limited to generic build commands without Flyway-specific validation checkpoints (e.g., checking migration naming, verifying migration execution). | 2 / 3 |
Progressive Disclosure | The skill references a single detailed reference file with a clear path, which is appropriate one-level-deep disclosure. However, since no bundle files were provided, we cannot verify the reference exists or assess its quality. The skill also references two other skills (@411, @412) without clear navigation paths. The overview itself is thin — almost too much is deferred to the reference. | 2 / 3 |
Total | 7 / 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
26e9744
- 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.