313-frameworks-spring-db-migrations-flyway

Use when you need to add or review Flyway database migrations in a Spring Boot application — Maven dependencies, db/migration scripts, spring.flyway.* configuration, baseline and validation, and alignment with JDBC or Spring Data JDBC. This should trigger for requests such as Add or review Flyway migrations in a Spring Boot project; Configure spring.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.

Well-structured, concise skill with a strong validation-gated workflow and clean one-level-deep reference disclosure. The main gap is actionability of the core task: actual migration SQL/config examples live only in the reference, so the body delegates rather than demonstrating.

Suggestions

Add one small inline example of a versioned migration file (e.g. a V1__create_table.sql snippet) and a minimal spring.flyway.* properties block so the core task is actionable without opening the reference.

Tighten the "What is covered" bullet list to avoid overlapping the description verbatim — the description already enumerates these capabilities, so the body could instead link directly to the relevant reference sections.

Make the "Read reference" step in the workflow name the specific section(s) to read (e.g. "baseline and validation patterns") so navigation is faster and more pointed.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence — terse bullets, short constraint list, and a compact workflow with no padding or explanation of concepts Claude already knows (e.g. no "what is Flyway").	3 / 3
Actionability	It gives concrete commands (./mvnw compile, mvn clean verify) and specifics (V{version}__{description}.sql, spring.flyway.* properties), but the core migration-writing guidance is largely "apply patterns from the reference" with no inline executable SQL or config example, leaving the central task under-specified inline.	2 / 3
Workflow Clarity	A clearly sequenced 4-step workflow with explicit validation checkpoints — MANDATORY compile-before, SAFETY stop-on-failure, VERIFY after — plus edge-case handling and a stop-and-ask guard for ambiguous goals.	3 / 3
Progressive Disclosure	SKILL.md is a concise overview that points to a single one-level-deep reference (references/313-frameworks-spring-db-migrations-flyway.md), clearly signaled both in the workflow and via a markdown link; the referenced file exists and content is appropriately split.	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.

A strong description with explicit trigger guidance, concrete capabilities, and a clearly bounded niche that coordinates with sibling skills. No major gaps; the only mild weakness is that the trigger list largely restates the capability list rather than adding new natural phrasings.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions and components — "add or review Flyway database migrations", "Maven dependencies", "db/migration scripts", "spring.flyway.* configuration", "baseline and validation", and "alignment with JDBC or Spring Data JDBC" — matching the anchor for naming multiple specific concrete actions.	3 / 3
Completeness	It opens with an explicit "Use when you need to..." trigger and pairs it with a clear statement of what the skill covers (dependencies, scripts, config, validation, JDBC alignment), answering both what and when explicitly.	3 / 3
Trigger Term Quality	Phrases such as "Add or review Flyway migrations in a Spring Boot project" and "Configure spring.flyway or db/migration layout" are natural ways a user would request this skill, giving good coverage of real-world trigger phrasings.	3 / 3
Distinctiveness Conflict Risk	The Flyway-in-Spring-Boot niche is narrow and clearly distinct, and the explicit coordination with sibling skills (@311...jdbc, @312...data-jdbc) signals scope boundaries that make triggering for the wrong skill unlikely.	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.