CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

agp-9-upgrade

Upgrades, or migrates, an Android project to use Android Gradle Plugin (AGP) version 9. Do not use this skill for migrating Kotlin Multiplatform (KMP) projects.

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./build-system/agp/agp-9-upgrade/SKILL.md
SKILL.md
Quality
Evals
Security

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 body is a well-structured, lean migration runbook: a proper entry gate, six sequenced steps with concrete version requirements and exact flags, explicit verification commands, and clean one-level-deep delegation to real reference files. The only meaningful weaknesses are steps that are pure pointers without inline orientation, and verification steps that lack an explicit failure-handling loop.

DimensionReasoningScore

Conciseness

The body is lean, assumes Claude's competence (never explains what AGP, KSP, or Hilt are), and delegates detail to references. Minor trimmable instances remain: the paragraph explaining that each AGP version's release notes include a Compatibility table, and time-sensitive version pins (KSP 2.3.6, Hilt 2.59.2, Paparazzi v2.0.0-alpha04) inlined in the main body rather than isolated in a reference. This fits anchor 4 (efficient with minor over-explanation) rather than 5, and nothing is padded enough to drop to 3.

4 / 5

Actionability

Concrete, executable guidance throughout: exact minimum versions ("ensure it is on version 2.3.6 or higher"), a numbered list of exact gradle.properties flags to remove, specific verification commands ("./gradlew help", "./gradlew build --dry-run"), and precise prohibitions ("Never add android.disallowKotlinSourceSets=false", "don't run the clean task"). Minor gaps keep it at 4: several steps (2, 3, 4, 5) consist almost entirely of "See [the guide]" pointers with no inline how-to, and the core version-bump action is also fully delegated.

4 / 5

Workflow Clarity

Clear gating and sequence: check the current AGP version first (stop and ask the user to run the Upgrade Assistant if below 9, with an explicit skip path), then Steps 1-6 in order, then an explicit Verification section with three concrete checks. Validation is present, so the missing-validation cap does not apply. It falls short of anchor 5 because error-recovery feedback loops are not tied to the verification checks — Troubleshooting covers only the known Paparazzi issue and gives no 'if sync/build fails, do X' loop.

4 / 5

Progressive Disclosure

A concise overview body with every one of the six bundle files clearly signaled and linked at the point of use (each "See [the guide]" states what it covers), and references are one level deep — the reference files link only to external documentation, never to each other, so there is no reference chaining. This matches the anchor for a clear overview with well-signaled one-level-deep references and easy navigation.

5 / 5

Total

17

/

20

Passed

Description

61%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 states a clear, well-bounded niche with a concrete primary action and an explicit KMP exclusion, but it omits any positive 'use when' trigger guidance and enumerates only one action, so it under-communicates both when to invoke it and the breadth of what the migration covers.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks to upgrade or migrate an Android project to AGP 9 / Android Gradle Plugin 9".

Enumerate the major migration actions to improve specificity, e.g. "...including migrating to built-in Kotlin, the new AGP DSL, kapt to KSP, and BuildConfig changes".

Include a couple of natural user phrasings or synonyms (e.g. "AGP 9 upgrade", "update Android Gradle Plugin") to strengthen trigger-term coverage.

DimensionReasoningScore

Specificity

"Upgrades, or migrates, an Android project to use Android Gradle Plugin (AGP) version 9" names the domain and one concrete action (upgrade/migrate to AGP 9) but, scoring only what is explicitly stated, lists no other actions — the sub-tasks (built-in Kotlin, new DSL, kapt migration, BuildConfig) are absent. This matches the 'names domain and 1-2 concrete actions, but not comprehensive' anchor; it is not 4 because it does not list several specific actions.

3 / 5

Completeness

The 'what' is clear (migrate an Android project to AGP 9), but there is no 'Use when...' clause or equivalent positive trigger guidance — only the negative exclusion "Do not use this skill for migrating Kotlin Multiplatform (KMP) projects". Per the rubric guideline, a missing 'Use when' clause caps completeness at 3, which is the best-fitting anchor.

3 / 5

Trigger Term Quality

Includes natural action synonyms ("Upgrades, or migrates") plus domain terms users would actually say ("Android project", "Android Gradle Plugin", "AGP", "version 9", "Kotlin Multiplatform (KMP)"). Good keyword coverage but a few natural terms/variations are missing, matching anchor 4 rather than the comprehensive synonym coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

A clear niche (AGP 9 migration for Android projects) with an explicit KMP boundary, giving minimal confusion risk. It is not 5 because closely related skills exist (general Gradle/AGP upgrade or KMP migration skills) and the description carries no positive triggers to distinguish invocation, leaving minor overlap risk — anchor 4.

4 / 5

Total

14

/

20

Passed

Validation

75%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 12 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

relative_links

Relative link issues: 4 deeper-than-1-level

Warning

referenced_paths_exist

Referenced path issues: 4 deeper-than-1-level

Warning

Total

12

/

16

Passed

Repository

android/skills

Path

build-system/agp/agp-9-upgrade/SKILL.md

Reviewed

Table of Contents

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.