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

89%

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

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

The content is a well-structured, actionable migration guide that assumes competence and offloads detail to clearly signaled reference files. Its main weakness is in conciseness/actionability: a few refinement steps could be executable snippets rather than bullets, and the workflow's fix-and-retry loop could be made explicit.

Suggestions

For the Step 3 refinement items (e.g. inter-module project() deps, [bundles], developmentOnly, kapt/ksp), show short copy-paste Kotlin DSL snippets instead of bare bullets to push actionability toward fully executable.

Make the verification feedback loop explicit in the Step 5 body — e.g. 'if ./gradlew build fails, fix the reported issue and re-run' — mirroring the checklist in references/gotchas.md section 9.

Tighten the Known Limitations list by merging closely related items (e.g. repository credentials and publishing configuration) to reduce token weight without losing information.

Dimension	Reasoning	Score
Conciseness	The body is dense and assumes Claude's competence with no 'what is Gradle' padding, and the gradle-init and Gradle 9 caveats are genuinely additive; minor trimming is possible in the Known Limitations list and some restated refinement bullets.	4 / 5
Actionability	Concrete executable commands are provided throughout (migrate.py invocations, gradle wrapper, ./gradlew build, ./gradlew dependencies) with specific refinement guidance, but several refinement items are bullets rather than full copy-paste code snippets.	4 / 5
Workflow Clarity	A clear five-step sequence (Analyze → Run script → Review/refine → Handle profiles → Verify) with a dry-run-then-write gate and an explicit verify step (build + dependency-tree comparison) addresses the destructive/batch cap; minor gap is an explicit 'fix and re-validate' loop is implied rather than spelled out in the body.	4 / 5
Progressive Disclosure	SKILL.md is a concise overview and the detailed material is split across five verified one-level-deep reference files (plugin-mappings, multi-module, profiles, gotchas, dual-build), each clearly signaled with inline pointers and a Reference Files section; scripts are isolated under scripts/.	5 / 5
	Total	17 / 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.

The description is exemplary: it states concrete capabilities, provides explicit and natural trigger phrases answering both 'what' and 'when', and sharply scopes its applicability with a negative-scope clause. No vague fluff or over-claims are present.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Spring Boot starter-parent conversion', 'dependency-scope and BOM mapping', 'Maven plugin to Gradle plugin translation', 'Maven profile equivalents', and 'dual-build overlay mode' — giving comprehensive coverage rather than generic language.	5 / 5
Completeness	Explicitly answers 'what' (Migrates Maven projects to Gradle Kotlin DSL with version catalogs, covering single/multi-module, Spring Boot, scopes, BOMs, plugins, profiles) and 'when' (an explicit 'Triggers on...' clause with concrete trigger phrases).	5 / 5
Trigger Term Quality	Comprehensive natural triggers including 'convert pom.xml to Gradle', 'migrate from Maven to Gradle', 'generate build.gradle.kts', 'modernize a JVM build system', plus file extensions (pom.xml, build.gradle.kts, libs.versions.toml) and synonyms.	5 / 5
Distinctiveness Conflict Risk	Clear niche (Maven-to-Gradle KTS migration only) reinforced by an explicit negative-scope clause excluding Gradle-to-Maven, brand-new Gradle authoring, Groovy DSL, and non-JVM tools, minimizing conflict risk.	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: ~11 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.