agentsclimarketplace

Android gradle build logic

Skill krutikJain/android-agent-skills/skills/android-gradle-build-logic

Android skills repository for Kotlin, Compose, XML, testing, CI, release work, and legacy upgrades

Install
npx -y skills add krutikJain/android-agent-skills --skill android-gradle-build-logic

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 14 stars14 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Shape Android build logic with Gradle, version catalogs, plugins, convention patterns, and toolchain compatibility.

SKILL.md

3.7 KB, as published. Nobody here has run it

Android Gradle Build Logic

When To Use

  • Use this skill when the request is about: android gradle plugin setup, fix build logic for android modules, version catalog for android repo.
  • Primary outcome: Shape Android build logic with Gradle, version catalogs, plugins, convention patterns, and toolchain compatibility.
  • Handoff skills when the scope expands:
  • android-modernization-upgrade
  • android-ci-cd-release-playstore

Workflow

  1. Map the request to the current Android stack, module boundaries, and minimum supported API level.
  2. Inspect the existing implementation for implicit assumptions, duplicate helpers, and outdated patterns.
  3. Apply the smallest change that improves correctness, readability, and long-term maintainability.
  4. Validate the result against the relevant showcase app path and repo benchmarks.
  5. Hand off adjacent work to the next specialized skill only after the core foundation is stable.

Guardrails

  • Prefer official Android and Kotlin guidance over custom local conventions when they conflict.
  • Keep public APIs boring and explicit; avoid clever abstractions that hide Android lifecycle costs.
  • Do not mix architectural cleanup with product behavior changes unless the request explicitly needs both.
  • Document any compatibility constraints that will affect old modules or generated code.

Anti-Patterns

  • Sprinkling helpers across modules without a clear ownership boundary.
  • Introducing framework-specific code into pure domain or data layers.
  • Refactoring every adjacent file when only one contract needed to change.
  • Leaving migration notes implied instead of writing them down.

Examples

Happy path

  • Scenario: Run the Compose showcase build from a clean checkout with version catalogs.
  • Command: cd examples/orbittasks-compose && ./gradlew :app:assembleDebug

Edge case

  • Scenario: Validate shared repositories and plugin management in the XML fixture.
  • Command: cd examples/orbittasks-xml && ./gradlew :app:assembleDebug

Failure recovery

  • Scenario: Benchmark build-logic trigger precision against modernization and CI skills.
  • Command: python3 scripts/eval_triggers.py --skill android-gradle-build-logic

Done Checklist

  • The implementation path is explicit, minimal, and tied to the right Android surface.
  • Relevant example commands and benchmark prompts have been exercised or updated.
  • Handoffs to adjacent skills are documented when the request crosses boundaries.
  • Official references cover the chosen pattern and the main migration or troubleshooting path.

Official References

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.