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; Add versioned Flyway SQL migrations for Spring Boot; Review Spring Boot database migration ordering; Fix repeatable Flyway migrations in a Spring project. Part of Plinth Toolkit

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

71%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, safety-conscious skill body with strong progressive disclosure and explicit compile/verify validation gates. Its main gap is actionability: the actual migration-writing patterns live entirely in the reference files, so the body offers orientation and guardrails rather than inline executable examples of the core task.

Suggestions

Add one short inline example of a versioned migration (a minimal V{version}__{description}.sql snippet) and one spring.flyway.* property block so the body is actionable without forcing a reference read for the common case.

Remove or condense the 'When to use this skill' section, which duplicates the frontmatter description's trigger list.

Make the migration-level feedback loop explicit in the workflow (e.g., validate migration ordering / flyway info, fix, re-run) rather than relying only on the build compile/verify loop.

Dimension	Reasoning	Score
Conciseness	The body is lean, assumes Claude knows what Flyway is, and avoids concept over-explanation; the 'When to use this skill' section duplicates the description's trigger phrases almost verbatim, a minor instance of content that could be trimmed.	4 / 5
Actionability	Concrete commands are present ('./mvnw compile', 'mvn clean verify') and file conventions are named ('V{version}__{description}.sql', 'BaseJavaMigration'), but the core actionable patterns for writing/structuring migrations are deferred to the reference files rather than shown inline, leaving key details in the body incomplete.	3 / 5
Workflow Clarity	A clear four-step sequence with explicit validation checkpoints (MANDATORY compile before, SAFETY stop-on-failure, VERIFY clean verify after) and a breaking-change review gate; held at 4 because the workflow step descriptions themselves are fairly high-level and the migration-level validate/fix/retry loop is only implied via the build loop.	4 / 5
Progressive Disclosure	The body is a concise overview pointing to three real one-level-deep reference files (all verified present in references/), clearly signaled in both the Workflow and a dedicated Reference section with links; content is appropriately split for easy navigation.	5 / 5
	Total	16 / 20 Passed

Description

95%Weight 40%Scale 1-5

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, specific description with explicit 'what' and 'when' coverage and natural trigger phrasing. The only weakness is second-person voice ('Use when you need to'), which costs one specificity point under the rubric.

Suggestions

Rewrite in third person (e.g., 'Use when adding or reviewing Flyway database migrations...') to avoid the second-person voice penalty.

Trim the 'Part of Plinth Toolkit' suffix and consider condensing the trigger list, since the five example triggers partially duplicate the opening clause.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions and domain areas — 'add or review Flyway database migrations', 'Maven dependencies', 'db/migration scripts', 'spring.flyway.* configuration, baseline and validation' — giving broad coverage; reduced from 5 to 4 because the description uses second person ('Use when you need to'), which the rubric penalizes by one specificity point.	4 / 5
Completeness	Explicitly answers both what (Flyway migrations, Maven deps, db/migration scripts, spring.flyway.* config, baseline/validation, JDBC alignment) and when ('Use when you need to...' plus concrete trigger phrases), matching the top anchor.	5 / 5
Trigger Term Quality	The 'This should trigger for requests such as' clause provides five natural user phrasings — 'Add or review Flyway migrations in a Spring Boot project', 'Configure spring.flyway or db/migration layout', 'Fix repeatable Flyway migrations' — comprehensive coverage of terms a user would actually say.	5 / 5
Distinctiveness Conflict Risk	Scoped tightly to Flyway database migrations in Spring Boot with explicit sibling-skill coordination (@311-jdbc, @312-spring-data-jdbc), giving a clear niche with minimal overlap risk.	5 / 5
	Total	19 / 20 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/plinth
Path: skills/313-frameworks-spring-db-migrations-flyway/SKILL.md
Commit: f6dfc6f

Reviewed: about 1 hour 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.