flyway-migrations • testland • Registry • Tessl

PluginPublic

testland/flyway-migrations

Use whenever a schema is managed with Flyway: versioned, repeatable and undo migration files, migrate, info, validate, baseline and repair, the schema history table, migration ordering questions, and CI gates on schema changes, via CLI, Maven, Gradle or Docker.

Quality

91%

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

85%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, mostly executable skill body with an ordered seven-step workflow, explicit validation checkpoints, and clean one-level-deep use of its single bundle reference. The main improvements are consolidating the repeated clean-guard warning and making the Maven/Gradle paths concrete.

Suggestions

State the cleanDisabled=true production guard once (e.g., in Step 5) and have the config comment and anti-patterns table point back to it instead of restating the rationale.

Replace the Maven pom.xml comment stub with a minimal executable plugin snippet, or move Maven/Gradle setup into references/commands.md alongside the CI job.

Tighten Step 7 by either listing the classification criteria for additive/breaking/data-loss/locking or pointing to a reference that defines them, since 'apply adversarial review' is currently the vaguest instruction in the workflow.

Dimension	Reasoning	Score
Conciseness	The body is lean — tables, terse steps, a two-line overview — and assumes Claude's competence, but the cleanDisabled=true production guard is repeated three times (config comment, following paragraph, and the anti-patterns table), which could be consolidated.	4 / 5
Actionability	Docker/brew commands, a real flyway.conf block, and a worked example with actual SQL are copy-paste ready, but the Maven and Gradle install paths are only comment stubs ('# add to pom.xml under <build><plugins>') rather than executable snippets.	4 / 5
Workflow Clarity	Steps 1-7 are explicitly ordered with validation woven in: the 'info -> migrate -> validate' daily loop, 'flyway repair' after failed migrations, the checksum-mismatch recovery path in the worked example, and a CI migration gate — a real feedback loop despite the destructive-operation context.	5 / 5
Progressive Disclosure	The body stays an overview and appropriately delegates the full command table and CI job to references/commands.md, which exists in the bundle, is one level deep, and is clearly signaled with its content described in Step 3, Step 6, and the References section.	5 / 5
	Total	18 / 20 Passed

Description

92%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 description with explicit what-and-when structure, concrete capability enumeration, and a tool-named trigger that sharply limits conflict risk. The only gap is a handful of missing natural synonyms (file-pattern terms like V*.sql, 'rollback', 'schema migration') that would broaden trigger matching.

Suggestions

Add natural trigger synonyms such as 'schema migrations', 'rollback', or the V*.sql / R__*.sql file patterns users commonly mention when asking for help.

Mention the CI-gate tooling context users would name (e.g., Testcontainers or ephemeral database) to catch CI-gate questions phrased without the word 'Flyway'.

Dimension	Reasoning	Score
Specificity	The description enumerates concrete capabilities — 'versioned, repeatable and undo migration files, migrate, info, validate, baseline and repair, the schema history table, migration ordering questions, and CI gates' — giving comprehensive, third-person coverage of the skill's actions rather than vague abstractions.	5 / 5
Completeness	It explicitly answers both questions: the 'what' is the enumerated commands, migration file types, history table, ordering, and CI gates, and the 'when' is the explicit clause 'Use whenever a schema is managed with Flyway'.	5 / 5
Trigger Term Quality	Natural terms like 'Flyway', 'migrations', 'schema history table', 'migration ordering', 'CI gates', and 'CLI, Maven, Gradle or Docker' cover what affected users would say, but common variations such as the V*.sql file patterns, 'schema migration', or 'rollback' are absent.	4 / 5
Distinctiveness Conflict Risk	The trigger is gated on Flyway by name — 'Use whenever a schema is managed with Flyway' — creating a clear niche with distinct triggers and minimal risk of firing for competing tools like Liquibase or Atlas.	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.

Reviewed

11 days ago

testland/flyway-migrations

On this page