Agent skill

Writing Build Steps

by quarkusio in quarkusio/quarkus

Patterns for creating and modifying Quarkus @BuildStep methods, build items, and recorders in extension deployment modules.

Apache-2.0Auto-check passedDevOps & Cloud

Install Writing Build Steps

skills CLI
$ npx skills add quarkusio/quarkus --skill writing-build-steps -a claude-code

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

GitHub CLI
$ gh skill install quarkusio/quarkus writing-build-steps --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/quarkusio/quarkus.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/writing-build-steps .claude/skills/writing-build-steps && 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
writing-build-steps
GitHub stars
16k
Token cost
~880 tokens
SKILL.md length
422 words
Files
1
Skills in repo
12
Repo updated
First seen
Licence
Apache-2.0

At a glance

Patterns for creating and modifying Quarkus @BuildStep methods, build items, and recorders in extension deployment modules.

  • DevOps & Cloud work in your project
  • SKILL.md covers Build Steps, Build Items, Key Rules and Config Mappings in Build Steps, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Writing Build Steps is an agent skill from quarkusio/quarkus. Patterns for creating and modifying Quarkus @BuildStep methods, build items, and recorders in extension deployment modules.

Its SKILL.md is about 880 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in DevOps & Cloud. It works with Java. The repository describes itself as: Quarkus: Supersonic Subatomic Java. The licence is Apache-2.0.

When your agent uses it

  • DevOps & Cloud work in your project

Example prompts

  • “Use the writing-build-steps skill to pattern for creating and modifying Quarkus @BuildStep methods, build items, and recorders in extension…”
  • “/writing-build-steps”

What it can do on your machine

Read from SKILL.md and the folder at commit d58d0eb. 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 java).

    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.

Context cost

Writing Build Steps loads about 880 tokens when it runs. Until then it costs about 36 tokens; SKILL.md has 422 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~36
When it runs · the whole SKILL.md, loaded when a task matches
~880

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 quarkusio/quarkus at commit d58d0eb, republished under its Apache-2.0 licence (© quarkusio). 422 words, ~880 tokens.

Download SKILL.mdSave it as .claude/skills/writing-build-steps/SKILL.md (or your agent's skills folder).
name
writing-build-steps
description
Patterns for creating and modifying Quarkus @BuildStep methods, build items, and recorders in extension deployment modules.

Writing Build Steps

Quarkus extensions perform work at build time through build steps that produce and consume build items. This is the core extension mechanism.

Build Steps

A build step is a method annotated with @BuildStep in a processor class (by convention <Feature>Processor.java in the deployment module).

java
@BuildStep
SomeBuildItem produce(AnotherBuildItem input) {
    // Build-time logic
    return new SomeBuildItem(...);
}

Build Items

Build items extend BuildItem (or a subclass) and are the data objects passed between build steps.

  • SimpleBuildItem — Exactly one instance. Use for single values.
  • MultiBuildItem — Multiple instances. Use when collecting contributions from multiple extensions (e.g., registering beans, routes).
  • Build items should be final classes.

Key Rules

  • Build steps are ordered by input/output dependencies, NOT declaration order
  • If a step consumes a BuildItem, it runs after all producers of that item
  • Prefer producing a single build item per step. A step that produces multiple different item types is a sign it should be split. Use BuildProducer<T> when you need to produce multiple instances of the same item type or produce items conditionally
  • Use Optional<T> for optional consumption of build items
  • Use List<T> to consume all instances of a MultiBuildItem
  • Build steps run during augmentation (build time), NOT at runtime
  • Avoid unnecessary I/O or computation — leverage existing build items rather than duplicating work

Config Mappings in Build Steps

@ConfigMapping/@ConfigRoot interfaces are only registered as CDI beans when they appear as a parameter in at least one @BuildStep. If a runtime bean injects a config mapping, you must reference that config mapping in a build step — otherwise the injection will fail with UnsatisfiedResolutionException. See the working-with-config skill for details.

Show full SKILL.md (167 more words)Show less

Recorders

To execute code at runtime from a build step, use a @Recorder. The recorder class lives in the runtime module. Its methods are called from deployment build steps, but the actual execution happens at application startup — the recorder generates bytecode that replays those method calls at runtime.

java
@BuildStep
@Record(ExecutionTime.RUNTIME_INIT)
void setupAtRuntime(MyRecorder recorder, SomeBuildItem item) {
    recorder.initialize(item.getValue());
}
Execution Times
  • STATIC_INIT — Runs during static initialization (before main()). Safe for native image. Prefer this when possible as it allows more work to be done at build time in native mode.
  • RUNTIME_INIT — Runs at application startup (during main()). Use when the code needs runtime-only resources (e.g., network, threads).
Recorder Constraints
  • Recorder methods must only use types available in the runtime module
  • Do not pass deployment-only types to recorder methods
  • Do not use build-time-only libraries inside recorder implementations
  • Recorder method parameters must be recordable (the bytecode recorder writes code that reconstructs the object, similar to how ObjectMapper would serialize it — but to bytecode, not JSON). Use simple value types, collections, or types with appropriate constructors/setters. This is NOT Java serialization

© quarkusio, 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

Just SKILL.md in .agents/skills/writing-build-steps of quarkusio/quarkus.

Open the folder on GitHubat commit d58d0eb

Compare with similar skills

Writing Build Steps 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.

Writing Build Steps compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Writing Build Steps this skillquarkusio/quarkus16k—~880Automated safety check: PassApache-2.0
Docker Jfr Benchmark Loopeclipse-rdf4j/rdf4j420—~945Automated safety check: PassBSD-3-Clause
Apm IntegrationsDataDog/dd-trace-java736—~3.7kAutomated safety check: NotesApache-2.0
Opik Local Dev Environmentcomet-ml/opik22k—~734Automated safety check: PassApache-2.0
Pi K8s Deployrodrigorodrigues/microservices-design-patterns187—~1.6kAutomated safety check: PassNone
Coastline Rendering Testosmandapp/OsmAnd-tools116—~2.5kAutomated safety check: PassCustom licence

Similar skills

  • Docker Jfr Benchmark Loop

    eclipse-rdf4j/rdf4j

    Run a repeatable RDF4J performance loop against one JMH benchmark in Docker with Linux Java 26 and JFR CPU-time profiling.

    420 GitHub stars~945 tokensUpdated today
    DevOps & CloudAuto-check passed
  • Apm Integrations

    DataDog/dd-trace-java

    Official

    Write a new library instrumentation end-to-end. An agent skill from DataDog/dd-trace-java.

    736 GitHub stars~3.7k tokensUpdated today
    DevOps & CloudAuto-check: notes
  • Starts, rebuilds, and troubleshoots the Opik local dev stack, including an optional Comet Platform integration mode for the Opik team.

    22k GitHub stars~734 tokensUpdated today
    DevOps & CloudAuto-check passed
  • Pi K8s Deploy

    rodrigorodrigues/microservices-design-patterns

    Check Docker Hub for a new :latest image on a managed service and roll it out to the home Pi k8s cluster, the same way authentication-service was deployed on 2026-08-29 (SSH + kubectl rollout…

    187 GitHub stars~1.6k tokensUpdated 21 days ago
    DevOps & CloudAuto-check passed
  • Coastline Rendering Test

    osmandapp/OsmAnd-tools

    Run or debug the coastline rendering test (CoastlineRenderingTester / utilities.sh test-coastline-rendering) that compares locally rendered tiles against tile.osmand.net and reports water mask…

    116 GitHub stars~2.5k tokensUpdated today
    DevOps & CloudAuto-check passed
  • Release A2a

    a2aproject/a2a-java

    Guide maintainers through the multi-step release process — version bump, CI verification, tagging, Maven Central deployment, SNAPSHOT bump, and versioned documentation.

    504 GitHub stars~2.3k tokensUpdated 4 days ago
    DevOps & CloudAuto-check passed

More from quarkusio/quarkus

All 12 skills in this repo
  • Manage Deprecations

    quarkusio/quarkus

    Maintain @Deprecated code in the Quarkus codebase: remove code that has been deprecated for more than 12 months, add the @Deprecated annotations that were missed when a related element was…

    16k GitHub stars~2.8k tokensUpdated today
    Auto-check passed
  • Building And Testing

    quarkusio/quarkus

    How to build and test Quarkus: Maven commands, build flags, incremental builds, justfile aliases, and important build rules.

    16k GitHub stars~615 tokensUpdated today
    Auto-check passed
  • Building Docs

    quarkusio/quarkus

    How to build, preview, and verify Quarkus documentation locally: root Maven build, docs rebuild, Roq dev server preview.

    16k GitHub stars~1.8k tokensUpdated today
    Auto-check passed
  • Quarkus split classloading model, runtime-dev module wiring, conditional dependencies, and common classloading mistakes.

    16k GitHub stars~635 tokensUpdated today
    Auto-check passed
  • Step-by-step guide for converting Quarkus extensions from the legacy @Record/@Recorder pattern to the ServiceRegistrar service system.

    16k GitHub stars~4.6k tokensUpdated today
    Auto-check passed
  • Creating Extensions

    quarkusio/quarkus

    How to create a new Quarkus extension: full module layout, package naming, artifact naming, dependency rules, and Dev UI setup.

    16k GitHub stars~929 tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Writing Build Steps

What does Writing Build Steps do?

Patterns for creating and modifying Quarkus @BuildStep methods, build items, and recorders in extension deployment modules. Writing Build Steps is an agent skill from quarkusio/quarkus. Patterns for creating and modifying Quarkus @BuildStep methods, build items, and recorders in extension deployment modules.

When should I use Writing Build Steps?

Writing Build Steps fits situations like: devOps & Cloud work in your project.

How do I install Writing Build Steps in Claude Code?

Run `npx skills add quarkusio/quarkus --skill writing-build-steps -a claude-code`. Or copy the skill folder (.agents/skills/writing-build-steps in quarkusio/quarkus) into .claude/skills/writing-build-steps in your project. Claude Code loads it when a task matches its description.

How do I install Writing Build Steps in Codex?

Run `npx skills add quarkusio/quarkus --skill writing-build-steps -a codex`. Or copy the skill folder (.agents/skills/writing-build-steps in quarkusio/quarkus) into .agents/skills/writing-build-steps in your project. Codex loads it when a task matches its description.

Can I use Writing Build Steps 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 quarkusio/quarkus --skill writing-build-steps -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/writing-build-steps, .gemini/skills/writing-build-steps, .github/skills/writing-build-steps and .opencode/skills/writing-build-steps in your project.

What does Writing Build Steps need to run?

SKILL.md names no scripts, command-line tools or credentials: Writing Build Steps is instructions for the agent only.

Does Writing Build Steps 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 Writing Build Steps 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 Writing Build Steps use?

Writing Build Steps is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Writing Build Steps use?

About 880 tokens (SKILL.md is roughly 3.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Writing Build Steps?

Skills that share tags, products or a category with Writing Build Steps: Docker Jfr Benchmark Loop (eclipse-rdf4j/rdf4j, 420 stars), Apm Integrations (DataDog/dd-trace-java, 736 stars), Opik Local Dev Environment (comet-ml/opik, 22k stars) and Pi K8s Deploy (rodrigorodrigues/microservices-design-patterns, 187 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Writing Build Steps?

quarkusio (a GitHub organization) maintains it in quarkusio/quarkus, which has 15,939 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on October 9, 2026.

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