maven-to-gradle

Migrates Maven projects to Gradle Kotlin DSL (build.gradle.kts) with version catalogs (libs.versions.toml). Covers single-module and multi-module projects, Spring Boot starter-parent conversion, dependency-scope and BOM mapping, Maven plugin to Gradle plugin translation, and Maven profile equivalents. Also supports a dual-build overlay mode that adds Gradle alongside Maven without removing pom.xml. Triggers on requests to convert pom.xml to Gradle, migrate from Maven to Gradle, generate build.gradle.kts, set up a Gradle version catalog from Maven, modernize a JVM build system, or add Gradle alongside Maven for gradual migration. Does not apply to Gradle-to-Maven conversion, authoring brand-new Gradle projects from scratch with no Maven source, Groovy DSL (build.gradle) authoring unrelated to migration, or non-JVM build tools (npm, Bazel, sbt, Make).

Quality

93%

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

86%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.

Strong, action-dense body with executable commands, a sequenced workflow with dry-run and verification checkpoints, and exemplary one-level-deep reference structure. The only gaps are minor: slight duplication of reference mentions, a long blockquote, and no explicit guidance for recovering from a failed verification build.

Suggestions

Add an error-recovery branch to Step 5 (e.g., 'If ./gradlew build fails: check the scope/resource-filtering sections of references/gotchas.md, re-run ./gradlew dependencies, and compare against mvn dependency:tree') to close the workflow-clarity gap.

Remove the duplication between the inline reference pointers (Steps 1, 3, 4, 5) and the final 'Reference Files' section — keep the inline pointers and drop the trailing list, or vice versa.

Tighten the Gradle 9 blockquote in Step 2 to the two or three behavior-changing facts, or move the detail into references/gotchas.md.

Dimension	Reasoning	Score
Conciseness	Mostly lean with no concept-explanation padding and a Currency section that defuses version staleness, but the Gradle 9 blockquote runs long and each of the five reference files is introduced inline and then re-listed in a 'Reference Files' section — minor trims remain. Not 5: not every token earns its place; not 3: the padding is incidental, not whole unnecessary explanations.	4 / 5
Actionability	Fully executable, copy-paste-ready commands throughout — 'python3 scripts/migrate.py <path-to-maven-project> --dry-run', '--mode overlay', 'gradle wrapper --gradle-version=9.6.1', './gradlew build', './gradlew dependencies # compare with: mvn dependency:tree' — plus concrete refinement guidance (kapt/ksp wiring, 'developmentOnly', convention plugins for 5+ modules) covering the common cases.	5 / 5
Workflow Clarity	Clear five-step sequence with real checkpoints: dry-run before writing, explicit verify step (build + tests + dependency-tree comparison against mvn dependency:tree), and a pointer to the full checklist in references/gotchas.md section 9. Not 5: there is no explicit error-recovery loop telling Claude what to do when './gradlew build' fails.	4 / 5
Progressive Disclosure	The body is a well-organized overview and all five references (plugin-mappings.md, multi-module.md, profiles.md, gotchas.md, dual-build.md) are real, one level deep, and clearly signaled with markdown links plus a one-line scope description at the point of need — no nested reference chains, no bulk content inlined that belongs in a separate file.	5 / 5
	Total	18 / 20 Passed

Description

100%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.

Excellent description: concrete third-person capabilities, an explicit trigger clause with natural phrasings and file extensions, and explicit exclusions that sharply delimit the skill's niche. No vague or padded language.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions — 'Migrates Maven projects to Gradle Kotlin DSL (build.gradle.kts) with version catalogs (libs.versions.toml)', 'Spring Boot starter-parent conversion, dependency-scope and BOM mapping, Maven plugin to Gradle plugin translation, and Maven profile equivalents', and 'a dual-build overlay mode' — with comprehensive capability coverage, all in third person ('Migrates', 'Covers', 'supports').	5 / 5
Completeness	Explicitly answers both 'what' (detailed capability sentences) and 'when' (a dedicated 'Triggers on…' clause with concrete trigger phrases), plus explicit exclusions; nothing is left merely implied.	5 / 5
Trigger Term Quality	'Triggers on requests to convert pom.xml to Gradle, migrate from Maven to Gradle, generate build.gradle.kts, set up a Gradle version catalog from Maven, modernize a JVM build system, or add Gradle alongside Maven for gradual migration' covers natural user phrasings, synonyms ('add Gradle alongside Maven', 'gradual migration'), and file extensions/names (pom.xml, build.gradle.kts, libs.versions.toml).	5 / 5
Distinctiveness Conflict Risk	Clear niche (Maven-to-Gradle migration) with explicit boundary carving: 'Does not apply to Gradle-to-Maven conversion, authoring brand-new Gradle projects from scratch with no Maven source, Groovy DSL (build.gradle) authoring unrelated to migration, or non-JVM build tools (npm, Bazel, sbt, Make)' — minimal overlap risk with adjacent skills.	5 / 5
	Total	20 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning

	Total	15 / 16 Passed

Repository: adityamparikh/maven-to-gradle
Path: SKILL.md
Commit: f1566f5

Reviewed: 19 hours 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.