android-gradle-logic

Expert guidance on setting up scalable Gradle build logic using Convention Plugins and Version Catalogs.

Quality

65%

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

Fix and improve this skill with Tessl

tessl review fix ./.github/skills/build_and_tooling/android-gradle-logic/SKILL.md

Quality

Content

68%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 guide with concrete code throughout, but it lacks explicit validation/verification checkpoints in its workflow, capping workflow clarity at 3.

Suggestions

Add a verification step after applying the plugin, e.g. 'Run ./gradlew :app:tasks or sync the project to confirm the convention plugin resolves and applies.'

Fill the elided placeholders ('# ...', '// Configure common options here') or note explicitly that they are intentional stubs for the user to extend.

Consider moving extended convention plugin variants (e.g. library, Hilt, Compose) into a references file with a one-line pointer to keep the overview lean.

Dimension	Reasoning	Score
Conciseness	The body is efficient and assumes Gradle competence, with lean code blocks and no padding about what Gradle/Kotlin are; only minor phrases like 'This drastically cleans up module-level build files' could be trimmed.	4 / 5
Actionability	It provides concrete, copy-paste-ready Kotlin/TOML code for settings, the version catalog, the convention plugin, its registration, and usage, with only minor gaps such as elided '[libraries] # ...' and '// Configure common options here' placeholders.	4 / 5
Workflow Clarity	Steps are clearly sequenced (Step 1, 2, 3, Usage) but there are no validation checkpoints (e.g. 'run ./gradlew tasks' or 'sync the project to verify the plugin resolves'), leaving the sequence without explicit feedback.	3 / 5
Progressive Disclosure	The body is well organized into clearly labeled sections (Goal, Project Structure, Steps, Usage) and is appropriately self-contained; at ~120 lines it slightly exceeds the under-50-line simple-skill threshold that would merit a 5.	4 / 5
	Total	15 / 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 is specific and well-targeted to its niche, but it omits an explicit 'Use when...' trigger clause and lists only a single concrete action, limiting completeness and specificity.

Suggestions

Add an explicit trigger clause, e.g. 'Use when setting up or refactoring an Android Gradle build with convention plugins, version catalogs, or multi-module build logic.'

List 2-3 concrete actions (e.g. 'centralize build logic, define version catalogs, apply convention plugins') to raise specificity.

Include common synonyms/file artifacts users might mention (e.g. 'libs.versions.toml', 'build-logic', 'composite build') for stronger trigger terms.

Dimension	Reasoning	Score
Specificity	The description names the domain ('Gradle build logic') and concrete mechanisms ('Convention Plugins and Version Catalogs') but lists only one action ('setting up'), lacking a comprehensive set of concrete actions.	3 / 5
Completeness	It clearly states the 'what' (expert guidance on setting up scalable Gradle build logic) but provides no 'Use when...' clause or equivalent explicit trigger guidance, capping completeness at 3 per the rubric.	3 / 5
Trigger Term Quality	Phrases like 'Gradle build logic', 'Convention Plugins', and 'Version Catalogs' are natural terms a developer would say when needing this skill, giving good keyword coverage, though a few common variations are absent.	4 / 5
Distinctiveness Conflict Risk	The niche is fairly distinct (scalable Android Gradle build logic via Convention Plugins and Version Catalogs) with minor overlap risk against general Gradle or build-automation skills.	4 / 5
	Total	14 / 20 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: new-silvermoon/awesome-android-agent-skills
Path: .github/skills/build_and_tooling/android-gradle-logic/SKILL.md
Commit: 82900ea

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.