Name: kotlin-tooling-gradle-to-kotlin-toolchain-project
Rating: 75.2 (1 reviews)
Author: Kotlin

kotlin-tooling-gradle-to-kotlin-toolchain-project

Load when migrating or converting an entire Gradle Kotlin project (build.gradle(.kts), wrapper, libs.versions.toml, buildSrc) to the Kotlin Toolchain, including rewriting CI and replacing Gradle plugins that have no native Toolchain equivalent. Skip for porting one Gradle plugin or general Toolchain work once Gradle is gone.

Quality

94%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

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

An exceptionally actionable, dense migration guide with a clear phased workflow and validation checkpoints, assuming Claude's competence throughout. The only weakness is mild: some exhaustive inline examples could be offloaded to the references file to lighten the overview.

Suggestions

Move the larger end-to-end code/TOML/XML blocks (e.g. the full CFBundle plist snippet, the convention→template Kotlin+YAML pair) into references/examples.md and link to them, keeping SKILL.md as a tighter overview.

Add an explicit 'if validation fails, fix and re-run' feedback-loop sentence to Phase 5 alongside the command checklist to make the recovery path literal rather than implied.

Consider mentioning 'Amper' as a synonym in the description or an early line, since users may refer to the Kotlin Toolchain by its former name.

Dimension	Reasoning	Score
Conciseness	Dense and assumes Claude's competence throughout — no basic-concept padding about Gradle or version catalogs — and every section is a non-obvious migration gotcha (the ${...} interpolation limit, detekt type-resolution, Skiko native runtime) that earns its tokens.	5 / 5
Actionability	Provides concrete executable commands ('./kotlin show modules', './kotlin build', './kotlin do jib') and copy-paste-ready YAML/TOML/XML examples that cover the common cases (bundle→template, convention→template, detekt patch, plist fix).	5 / 5
Workflow Clarity	A clearly sequenced Phase 1–5 workflow with an explicit per-plugin validation gate (Phase 3 step 6: run './kotlin show modules' after each) and an end-to-end validation checklist (Phase 5); destructive steps (deleting build.gradle.kts/buildSrc) are gated by validation, so the destructive-cap does not apply.	5 / 5
Progressive Disclosure	Well-structured sections with a clearly signaled, one-level-deep reference to the real references/examples.md, but a large amount of detailed inline material (plist XML, TOML/YAML blocks) makes the body denser than a pure overview, a minor organization gap.	4 / 5
	Total	19 / 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, specific description with explicit 'Load when' trigger guidance and negative scoping that sharply delineates the skill from its siblings. Keyword coverage is excellent though it omits a couple of natural synonyms a user might say.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'migrating or converting an entire Gradle Kotlin project', 'rewriting CI', 'replacing Gradle plugins that have no native Toolchain equivalent' — and enumerates the concrete file artifacts (build.gradle(.kts), wrapper, libs.versions.toml, buildSrc), giving comprehensive coverage of the migration scope.	5 / 5
Completeness	Explicitly answers both 'what' (the migration actions) and 'when' ('Load when migrating or converting...') with concrete trigger phrases, plus a negative-scope trigger ('Skip for porting one Gradle plugin...').	5 / 5
Trigger Term Quality	Good natural-term coverage ('migrating/converting Gradle Kotlin project', 'Kotlin Toolchain', 'CI', 'Gradle plugins', libs.versions.toml, buildSrc) that a user would actually say, but a few synonyms a user might use (e.g. 'Amper') are absent.	4 / 5
Distinctiveness Conflict Risk	A clear niche (entire-project Gradle→Toolchain migration) with explicit negative scoping that distinguishes it from the per-plugin port skill and general Toolchain work, minimizing conflict risk.	5 / 5
	Total	19 / 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
relative_links	Relative link issues: 3 suspicious	Warning

	Total	15 / 16 Passed

Repository: Kotlin/kotlin-agent-skills
Path: skills/kotlin-tooling-gradle-to-kotlin-toolchain-project/SKILL.md
Commit: c2f9069

Reviewed: 5 days 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.