New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Gradle

by micronaut-projects in micronaut-projects/micronaut-openapi

Execute Gradle maintainer operations for Micronaut repositories using micronaut-build internals and modern Gradle best practices.

Apache-2.0Auto-check passedBackend & APIs

Install Gradle

skills CLI
$ npx skills add micronaut-projects/micronaut-openapi --skill gradle -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install micronaut-projects/micronaut-openapi gradle --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/micronaut-projects/micronaut-openapi.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/gradle .claude/skills/gradle && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
gradle
GitHub stars
114
Token cost
~1.6k tokens
SKILL.md length
609 words
Files
3 (incl. references)
Skills in repo
7
Repo updated
First seen
Licence
Apache-2.0

At a glance

Execute Gradle maintainer operations for Micronaut repositories using micronaut-build internals and modern Gradle best practices.

  • Works in 4 steps: Establish build shape first → Use source-of-truth plugin contracts → Execute maintainer workflows → …
  • Users ask to diagnose build failures
  • SKILL.md covers Goal, Procedure, Guardrails and Best Practices, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Gradle is an agent skill from micronaut-projects/micronaut-openapi. Execute Gradle maintainer operations for Micronaut repositories using micronaut-build internals and modern Gradle best practices. Use when users ask to diagnose build failures, maintain BOM/version catalogs, manage publishing/signing, enforce binary compatibility, or debug micronaut-build plugin behavior.

Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `references/gradle-best-practices.md` and `references/micronaut-build-plugins.md`). Compatibility notes: Micronaut framework repositories in micronaut-projects using micronaut-build plugins

It sits in Backend & APIs, covering OpenAPI specifications. It works with Gradle and OpenAPI. The repository describes itself as: Generates OpenAPI / Swagger Documentation for Micronaut projects. The licence is Apache-2.0.

When your agent uses it

  • Users ask to diagnose build failures
  • Maintain BOM/version catalogs
  • Manage publishing/signing
  • Enforce binary compatibility

Example prompts

  • “/gradle”

Requirements

  • Docker
  • Compatibility (from SKILL.md): Micronaut framework repositories in micronaut-projects using micronaut-build plugins

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Establish build shape first
  2. Use source-of-truth plugin contracts
  3. Execute maintainer workflows
  4. Verify before completion

What it can do on your machine

Read from SKILL.md and the folder at commit 4877fd7. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are kotlin).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    Micronaut framework repositories in micronaut-projects using micronaut-build plugins

    From compatibility in the SKILL.md frontmatter.

Context cost

Gradle loads about 1.6k tokens when it runs, and up to ~5.1k if it reads all its reference files. Until then it costs about 78 tokens; SKILL.md has 609 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~78
When it runs · the whole SKILL.md, loaded when a task matches
~1.6k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~5.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from micronaut-projects/micronaut-openapi at commit 4877fd7, republished under its Apache-2.0 licence (© micronaut-projects). 609 words, ~1,557 tokens.

Download SKILL.mdSave it as .claude/skills/gradle/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
gradle
description
Execute Gradle maintainer operations for Micronaut repositories using micronaut-build internals and modern Gradle best practices. Use when users ask to diagnose build failures, maintain BOM/version catalogs, manage publishing/signing, enforce binary compatibility, or debug micronaut-build plugin behavior.
compatibility
Micronaut framework repositories in micronaut-projects using micronaut-build plugins
license
Apache-2.0
metadata.author
Álvaro Sánchez-Mariscal
metadata.version
1.0.0
metadata.gradle-major-version
9.x

Gradle (Micronaut Committer)

Use this skill for Micronaut framework maintainer work. Do not default to end-user app guidance.

Goal

Apply correct, source-backed Gradle changes in Micronaut repositories, using the micronaut-build plugin contracts and current Gradle best practices.

Current coverage target: repositories on Gradle major line 9.x.

For dependency-intelligence tasks (version freshness, stability, release cadence, CVE/license checks), use the embedded maven-tools MCP via skill_mcp.

Procedure

  1. Identify build shape and active plugins.
  2. Map requested work to exact micronaut-build plugin behavior.
  3. Execute minimal maintainer-safe change.
  4. Verify with targeted and aggregate Gradle tasks.
1) Establish build shape first
  • Inspect settings.gradle or settings.gradle.kts for settings plugins and dependency management.
  • Confirm io.micronaut.build.shared.settings is present unless the repository intentionally diverged.
  • Validate settings-scoped plugins (especially Develocity wiring) in settings.gradle(.kts), not in project build.gradle(.kts).
  • Confirm root build applies io.micronaut.build.internal.parent for standard aggregation behavior.
  • Inspect root and impacted module build files for applied plugin IDs and micronautBuild extension usage.
  • Inspect buildSrc/convention plugins before modifying module build scripts.
  • Inspect gradle.properties and gradle/*.versions.toml for version source and overrides.
  • Treat module directory names and Gradle project paths separately; if standardized names are enabled, use :micronaut-* paths for task targeting.
  • If module paths are unclear, run ./gradlew projects.
  • If dependency resolution is involved, capture dependencyInsight before changing files.
2) Use source-of-truth plugin contracts
  • Use references/micronaut-build-plugins.md as the authoritative plugin behavior map.
  • Treat micronaut-build source as primary truth. Its README may be outdated.
  • Remember default plugin IDs are internal: io.micronaut.build.internal.<name>.
  • Important exception: io.micronaut.build.shared.settings.
3) Execute maintainer workflows
  • Build failures: reproduce with minimal task path, then expand to module check, then root validation.
  • Catalog/version updates: use plugin-provided workflows (updateVersionCatalogs, useLatestVersions) where available.
  • Catalog imports: prefer micronautBuild { importMicronautCatalog() } and alias-specific imports over ad hoc BOM wiring when repository conventions use settings extension catalog import.
  • Dependency intelligence: use the maven-tools MCP for latest stable versions, upgrade comparisons, and dependency health signals before changing catalogs or BOM constraints.
  • Dependency scope hygiene: choose api only for public API surface; use implementation for internals; use compileOnly/runtimeOnly intentionally.
  • BOM/publishing: verify BOM generation, inlining behavior, publication metadata, and signing gates.
  • Binary compatibility: keep baseline discovery and accepted API changes explicit; never silently suppress regressions.
  • Docs/quality: treat root-only aggregator plugins and docs pipelines as first-class checks.
  • Layering: prefer convention plugin changes (buildSrc) over duplicating logic in many module build files.
Show full SKILL.md (229 more words)Show less
4) Verify before completion
  • Run at least one targeted task and one aggregate task:
    • ./gradlew :<module>:check
    • ./gradlew check
  • For maintainer pipelines, include docs and style gates where applicable:
    • ./gradlew check docs
    • ./gradlew spotlessApply spotlessCheck
  • For API-affecting changes, run compatibility checks:
    • ./gradlew japiCmp
  • For newly added published modules, define when binary compatibility checks start in module build logic (example):
kotlin
micronautBuild {
    binaryCompatibility.enabledAfter("2.0.0")
}
  • Use the repository's intended first compatible release version instead of blindly reusing 2.0.0.
  • Add focused diagnostics when needed:
    • ./gradlew dependencyInsight --configuration <conf> --dependency <module>
    • ./gradlew --scan <task>
  • Report exact commands and outcomes.

Guardrails

  • Do not use enforcedPlatform when plugin logic explicitly forbids it.
  • Do not bypass Micronaut version mismatch checks except intentional development-version flows.
  • Do not apply root-only plugins to subprojects.
  • Do not replace framework maintainer workflows with generic app-centric shortcuts.

Best Practices

Use references/gradle-best-practices.md for operational standards on:

  • configuration and build cache behavior,
  • provider/lazy configuration patterns,
  • toolchains and reproducibility,
  • secure publishing and dependency verification,
  • CI reliability.

Examples

  • "Diagnose why micronaut-core version mismatch fails on compileClasspath."
  • "Update version catalogs safely and apply latest allowed minor versions."
  • "Fix Sonatype release pipeline behavior for a non-snapshot release."
  • "Investigate binary compatibility failure and validate accepted changes file usage."

Validation Checklist

  • Active plugins identified from build files.
  • Decisions mapped to micronaut-build source behavior.
  • Changes align with maintainer workflows.
  • Verification tasks run and outcomes captured.
  • No end-user-only Gradle guidance substituted for framework operations.

References

  • references/micronaut-build-plugins.md
  • references/gradle-best-practices.md

© micronaut-projects, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files (references) in .agents/skills/gradle of micronaut-projects/micronaut-openapi.

  • SKILL.md
  • references/gradle-best-practices.md
  • references/micronaut-build-plugins.md

Open the folder on GitHubat commit 4877fd7

Used in 2 other repositories

We found 2 copies of this SKILL.md (exact, near-identical or edited) in other folders. This page covers the copy in micronaut-projects/micronaut-openapi, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Gradle next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Gradle compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Gradle this skillmicronaut-projects/micronaut-openapi114—~1.6kAutomated safety check: PassApache-2.0
ToolJet Marketplace Plugin BuilderToolJet/ToolJet41k—~2.1kAutomated safety check: PassAGPL-3.0
Step Partsearthtojake/text-to-cad19k1 repos~1.5kAutomated safety check: PassMIT
OpenAPI to MCP Servermcp-use/mcp-use11k—~5.2kAutomated safety check: PassApache-2.0
Use Yaakmountain-loop/yaak19k—~1.9kAutomated safety check: PassMIT
API DesignerJeffallan/claude-skills12k1 repos~2kAutomated safety check: PassMIT

Similar skills

  • ToolJet Marketplace Plugin Builder

    ToolJet/ToolJet

    Turns an API description, such as an OpenAPI file or a Postman collection, into a connector plugin for ToolJet's marketplace and checks it with the repo's validator.

    41k GitHub stars~2.1k tokensUpdated today
    Backend & APIsAuto-check passed

  • Step Parts

    earthtojake/text-to-cad

    Find, evaluate, and download common purchasable CAD parts from step.parts, including named off-the-shelf actuators, servos, motors, electronics boards, connectors, screws, bolts, nuts, washers…

    19k GitHub starsUsed in 1 repo~1.5k tokens
    Backend & APIsAuto-check passed

  • OpenAPI to MCP Server

    mcp-use/mcp-use

    Turns an OpenAPI or Swagger spec into an MCP server with the mcp-use TypeScript SDK, mapping each operation to a tool, wiring auth, testing and deploying.

    11k GitHub stars~5.2k tokensUpdated today
    Backend & APIsAuto-check passed

  • Use Yaak

    mountain-loop/yaak

    A skill your agent uses when the user mentions Yaak, a Yaak workspace, or the yaak command, or asks to call, hit, or smoke test HTTP/REST endpoints, save or organize API requests for reuse or manual…

    19k GitHub stars~1.9k tokensUpdated 2 days ago
    Backend & APIsAuto-check passed

  • API Designer

    Jeffallan/claude-skills

    Designs REST and GraphQL APIs from resource modeling to an OpenAPI 3.1 contract, with versioning, pagination and RFC 7807 error handling.

    12k GitHub starsUsed in 1 repo~2k tokens
    Backend & APIsAuto-check passed

  • CLI Creator

    huangruiteng/CS-Notes

    Build a composable CLI for Codex from API docs, an OpenAPI spec, existing curl examples, an SDK, a web app, an admin tool, or a local script.

    4k GitHub starsUsed in 2 repos~2.7k tokens
    Backend & APIsAuto-check passed

More from micronaut-projects/micronaut-openapi

  • Agent Md Refactor

    micronaut-projects/micronaut-openapi

    Refactor oversized agent instruction files into a progressive-disclosure structure.

    114 GitHub stars~766 tokensUpdated yesterday
    Auto-check passed

  • Docs

    micronaut-projects/micronaut-openapi

    Write and maintain Micronaut Framework module guides for micronaut-projects repositories.

    114 GitHub stars~1.4k tokensUpdated yesterday
    Auto-check passed

  • Guides

    micronaut-projects/micronaut-openapi

    Create or update standalone Micronaut Guides in micronaut-projects/micronaut-guides, including topic discovery, guide authoring, validation, PDF export, and pull request handoff.

    114 GitHub stars~1.9k tokensUpdated yesterday
    Auto-check: notes

  • Skill Creator

    micronaut-projects/micronaut-openapi

    Create new Agent Skills or improve existing ones in an agent-agnostic way.

    114 GitHub stars~1.2k tokensUpdated yesterday
    Auto-check passed

  • Coding

    micronaut-projects/micronaut-openapi

    Implement and review Java code changes for Micronaut framework repositories using maintainer standards, including JSpecify null-safety conventions.

    114 GitHub stars~2.6k tokensUpdated yesterday
    Auto-check passed

  • Micronaut Sourcegen

    micronaut-projects/micronaut-openapi

    Add, integrate, or review Micronaut Sourcegen usage in modules that generate Java source, Kotlin source, Groovy-compatible source, or bytecode from ObjectDef, TypeDef, MethodDef, ExpressionDef…

    114 GitHub stars~3.3k tokensUpdated yesterday
    Auto-check passed

Works with

Categories

Questions about Gradle

What does Gradle do?

Execute Gradle maintainer operations for Micronaut repositories using micronaut-build internals and modern Gradle best practices. Gradle is an agent skill from micronaut-projects/micronaut-openapi. Execute Gradle maintainer operations for Micronaut repositories using micronaut-build internals and modern Gradle best practices.

When should I use Gradle?

Gradle fits situations like: users ask to diagnose build failures; maintain BOM/version catalogs; manage publishing/signing; enforce binary compatibility.

How do I install Gradle in Claude Code?

Run `npx skills add micronaut-projects/micronaut-openapi --skill gradle -a claude-code`. Or copy the skill folder (.agents/skills/gradle in micronaut-projects/micronaut-openapi) into .claude/skills/gradle in your project. Claude Code loads it when a task matches its description.

How do I install Gradle in Codex?

Run `npx skills add micronaut-projects/micronaut-openapi --skill gradle -a codex`. Or copy the skill folder (.agents/skills/gradle in micronaut-projects/micronaut-openapi) into .agents/skills/gradle in your project. Codex loads it when a task matches its description.

Can I use Gradle in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add micronaut-projects/micronaut-openapi --skill gradle -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/gradle, .gemini/skills/gradle, .github/skills/gradle and .opencode/skills/gradle in your project.

What does Gradle need to run?

SKILL.md names no scripts, command-line tools or credentials: Gradle is instructions for the agent only. Our summary lists: Docker. Compatibility (from SKILL.md): Micronaut framework repositories in micronaut-projects using micronaut-build plugins.

Does Gradle access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Gradle safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Gradle use?

Gradle is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Gradle use?

About 1.6k tokens (SKILL.md is roughly 6.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 3.6k tokens, read only when the agent opens those files.

What are the alternatives to Gradle?

Skills that share tags, products or a category with Gradle: ToolJet Marketplace Plugin Builder (ToolJet/ToolJet, 41k stars), Step Parts (earthtojake/text-to-cad, 19k stars), OpenAPI to MCP Server (mcp-use/mcp-use, 11k stars) and Use Yaak (mountain-loop/yaak, 19k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Gradle?

micronaut-projects (a GitHub organization) maintains it in micronaut-projects/micronaut-openapi, which has 114 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on October 8, 2026.

Source: micronaut-projects/micronaut-openapi on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.