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; Add versioned Flyway SQL migrations for Micronaut; Review Micronaut database migration ordering; Configure Flyway datasources in a Micronaut project. Part of Plinth Toolkit

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

70%

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

A well-structured overview body with strong validation/feedback checkpoints and clean one-level-deep progressive disclosure; the main gaps are duplicated trigger phrasing between body and description and abstractness in the middle workflow step.

Suggestions

Remove or condense the 'When to use this skill' section since its five bullets duplicate the description's triggers, saving tokens.

Add one or two concrete inline examples (e.g. a sample versioned SQL filename like V001__add_users_table.sql or a flyway.datasources snippet) so the body is actionable without requiring the references.

Make workflow step 3 more concrete by naming the specific reference patterns to apply (e.g. 'follow the good/bad patterns in the antipatterns reference') instead of 'Apply framework-aligned changes'.

Dimension	Reasoning	Score
Conciseness	The body is lean and avoids explaining concepts Claude already knows, but the 'When to use this skill' section duplicates the five triggers already listed in the description almost verbatim, which could be tightened or removed.	2 / 3
Actionability	Provides concrete executable commands ('./mvnw compile', 'mvn clean verify') and specific reference file paths, but inline migration examples are deferred to references and step 3 ('Apply framework-aligned changes') stays abstract rather than giving concrete patterns.	2 / 3
Workflow Clarity	A clear 4-step sequence reinforced by explicit validation checkpoints and feedback loops in the Constraints (MANDATORY compile before, SAFETY stop on failure, VERIFY after, breaking-change review), appropriate for destructive database operations.	3 / 3
Progressive Disclosure	SKILL.md acts as an overview pointing to three real, one-level-deep reference files, clearly signaled with markdown links in a Reference section and referenced again in the workflow; content is appropriately split.	3 / 3
	Total	10 / 12 Passed

Description

90%

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 trigger guidance and a clear Micronaut+Flyway niche; the only weakness is second-person voice ('you need to') instead of the recommended third person, which caps specificity.

Suggestions

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

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capabilities ('micronaut-flyway, db/migration scripts, flyway.datasources.* configuration, and alignment with JDBC or Micronaut Data'), which would merit a 3, but the opening 'Use when you need to' is second person and the rubric penalizes non-third-person voice by reducing specificity by 1.	2 / 3
Completeness	Clearly answers both what (add/review Flyway migrations with concrete specifics) and when, via the explicit 'Use when you need to...' clause and 'This should trigger for requests such as...' triggers.	3 / 3
Trigger Term Quality	Covers natural phrasings a user would say ('Add or review Flyway migrations', 'Configure micronaut-flyway or db/migration layout', 'Add versioned Flyway SQL migrations', 'Review Micronaut database migration ordering', 'Configure Flyway datasources') with good coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	A tight niche (Flyway database migrations specifically within Micronaut) with triggers tied to that combination, making it unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 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/plinth
Commit: aaee915

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