Gradle Skills plugin
Official Gradle skills: a build audit against Gradle best practices and a safe wrapper upgrade that rolls back on failure
- 76 ★ on the repository
- Last commit
- Apache-2.0
Extended access
Why this level
- The wrapper upgrade skill changes `gradlew`, `gradlew.bat` and the wrapper jar in the working tree
- The audit reads build scripts and plugin code and applies fixes on request
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add plugins/gradle-skillsDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The wrapper upgrade skill changes `gradlew`, `gradlew.bat` and the wrapper jar in the working tree
- The audit reads build scripts and plugin code and applies fixes on request
This is third-party code. Review the repository files before installing.
What it does
The plugin holds two skills in the Agent Skills format. `gradle-best-practices` compares a build with the official Gradle recommendations and reports findings ordered by impact, each linked to its practice. It reads build scripts, settings files, `gradle.properties`, the wrapper config, the version catalog and plugin code under `buildSrc/` and `build-logic/`. On request it applies the fixes. `gradle-wrapper-upgrade` upgrades the wrapper to the latest release or a named one. It pins the distribution checksum, regenerates `gradlew`, `gradlew.bat` and the wrapper jar, then checks that the build still configures. If it does not, the upgrade is rolled back and a smaller step is suggested with the release notes. Asked how to upgrade, the skill answers with commands and leaves the working tree alone. The skill upgrades an existing wrapper only: it will not add one to a build that has none and will not edit build scripts. The `evals/` folder holds benchmark results across several models and agents.
Who it is for. Java and Kotlin developers on Gradle who want to audit a build and upgrade the wrapper without manual checksum work.
Good fit when
- The build got slow and you want a review against official Gradle practices ordered by impact
- The wrapper is outdated and must be raised to a given version with a checksum
- Before a major Gradle migration you want a smaller step if the upgrade breaks the build
- A team needs the shared plugin with these skills in the project `.claude/settings.json`
Not a fit when
- You need to add Gradle to a project that has none: the skill does not create a wrapper from scratch
- You need to rewrite build scripts for a new Gradle version: the skill does not edit them during a wrapper upgrade
- The project uses Maven or Bazel: the set targets Gradle only
Example request
Audit this Gradle project against the official practices and show findings ordered by impactLimitations
There are two skills, covering the practices audit and the wrapper upgrade; other Gradle tasks are outside the set. The audit follows the official practices page as of the time the skill was written, and new Gradle rules arrive with a plugin update. After a wrapper upgrade the build is checked only for configuration, and a full test run is left to you. In Claude Code each team member needs one install command even if the marketplace is already listed in `.claude/settings.json`. The skill applies fixes only on request.
How to disable. In Claude Code run `/plugin uninstall gradle-skills@gradle-skills`; for other agents delete the skill folders from the project `.agents/skills/` or reinstall without them.
FAQ
How do I install Gradle Skills in Claude Code?
With `/plugin marketplace add gradle/gradle-skills` and `/plugin install gradle-skills@gradle-skills`. The skills load as `gradle-skills:gradle-best-practices` and `gradle-skills:gradle-wrapper-upgrade`.
What happens if the build breaks after the upgrade?
The skill rolls the wrapper upgrade back and suggests a version closer to the current one with the release notes. It tries versions step by step, checking build configuration after each.
Does the skill change my files when I ask how to upgrade?
No. For a how-to question it answers with commands and the working tree stays as it was. Changes happen only after you ask for the upgrade itself.
Does the set work in Codex and Cursor?
Yes, they read the Agent Skills format too. `npx skills add gradle/gradle-skills` places the skills into the project `.agents/skills/`, and `-g` installs them for every project.
Where can I see the quality of the skills?
The `evals/` folder holds benchmark records for audit versions 1.0.0 and 1.0.1 and wrapper upgrade versions 1.0.0 and 1.1.0 across several models and agents.
Discussion
No questions or reviews yet.
Related
PluginsA skill set from the Kotlin team for agents: Java to Kotlin conversion, build migrations and correct use of backend frameworks
A skills library for Claude Code, Cursor and Codex: team code review, TDD, stacked PRs and repository readiness scoring
Seven Go skills from the creator of Cobra and Hugo: idiomatic style, CLI design, releases, Wails, file operations and afero tests
37signals skills in the dev, security, ai and recap plugins: review replies, GitHub Actions hardening, AGENTS.md files, digests.
Brooklyn skills: 25 portable agent skills for pull requests, triage, cleanup, UI checks and research
Guard skills for coding agents: a second pass over the diff that catches typical AI mistakes in code, tests and docs
README in short
The README first describes the two skills with versions, links to benchmark records and sample prompts. Installation in Claude Code through the marketplace follows, then team setup in `.claude/settings.json` and installation for other agents with `npx skills`.