513-frameworks-micronaut-db-migrations-flyway

Use when you need to add or review Flyway database migrations in a Micronaut application — micronaut-flyway, db/migration scripts, flyway.datasources.* configuration, and alignment with JDBC or Micronaut Data. This should trigger for requests such as Add or review Flyway migrations in a Micronaut project; Configure micronaut-flyway or db/migration layout. Part of cursor-rules-java project

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

85%

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-structured and concise with a clear, validated workflow and proper one-level-deep progressive disclosure. Its main weakness is actionability: the central implementation step is an abstract pointer to the reference file rather than inline executable guidance.

Suggestions

Add at least one concrete, copy-paste-ready example inline (e.g., a sample V{version}__{description}.sql migration and a minimal flyway.datasources.* YAML snippet) so the 'Apply framework-aligned changes' step is executable without opening the reference.

Make the 'Run verification and report results' step concrete by stating the expected success signal (e.g., 'BUILD SUCCESS' or which tests/migration checks to confirm) rather than 'execute appropriate build/tests'.

Tighten step 3 with a minimal checklist of what a framework-aligned change must include (naming convention, per-datasource config key, forward-only direction) so the action is reproducible before consulting the reference.

Dimension	Reasoning	Score
Conciseness	The body is lean and does not explain concepts Claude already knows (no preamble on what Flyway or Micronaut is); every section earns its place and assumes Claude's competence, matching the score-3 anchor.	3 / 3
Actionability	Concrete commands are present ('./mvnw compile', 'mvn clean verify'), but the core 'Apply framework-aligned changes' step delegates actual implementation to the reference ('following the reference patterns and project conventions') without inline executable code or specifics, leaving key details for the referenced file rather than being copy-paste ready.	2 / 3
Workflow Clarity	A clear 4-step sequence carries explicit validation checkpoints — compile before changes, stop immediately on failure, verify after — plus edge-case handling; for destructive/batch DB operations this satisfies the feedback-loop requirement that would otherwise cap at 2.	3 / 3
Progressive Disclosure	SKILL.md is a concise overview pointing to a single, real one-level-deep reference (references/513-frameworks-micronaut-db-migrations-flyway.md, verified present) via a clearly signaled markdown link, with content appropriately split rather than inlined.	3 / 3
	Total	11 / 12 Passed

Description

100%

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 strong: it states concrete capabilities, includes natural trigger phrasing, answers both 'what' and 'when' with an explicit 'Use when' clause, and is clearly demarcated from sibling JDBC/Data skills. It is concise and free of vague fluff.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capabilities — 'micronaut-flyway', 'db/migration scripts', 'flyway.datasources.* configuration', and 'alignment with JDBC or Micronaut Data' — matching the score-3 anchor for listing several specific actions rather than a single domain.	3 / 3
Completeness	Opens with an explicit 'Use when you need to add or review Flyway database migrations...' trigger and enumerates what the skill covers, clearly answering both what and when; the explicit trigger guidance prevents a cap at 2.	3 / 3
Trigger Term Quality	Includes natural phrasings users would actually say — 'Add or review Flyway migrations in a Micronaut project' and 'Configure micronaut-flyway or db/migration layout' — giving good coverage of natural terms, not just technical jargon.	3 / 3
Distinctiveness Conflict Risk	Scoped to Flyway migrations within Micronaut and explicitly distinguishes sibling skills ('@511-frameworks-micronaut-jdbc', '@512-frameworks-micronaut-data'), making it a clear niche unlikely to trigger for the wrong skill.	3 / 3
	Total	12 / 12 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
Commit: 86eb63d

Reviewed: 4 days 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.