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.
Patterns for creating and modifying Quarkus @BuildStep methods, build items, and recorders in extension deployment modules.
$ npx skills add quarkusio/quarkus --skill writing-build-steps -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install quarkusio/quarkus writing-build-steps --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ 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-srcUse ~/.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/
Install the "writing-build-steps" agent skill from https://github.com/quarkusio/quarkus/tree/main/.agents/skills/writing-build-steps into .claude/skills/writing-build-steps/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-build-steps", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/quarkusio/quarkus/tree/main/.agents/skills/writing-build-stepsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add quarkusio/quarkus --skill writing-build-steps -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install quarkusio/quarkus writing-build-steps --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/quarkusio/quarkus.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/writing-build-steps .agents/skills/writing-build-steps && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "writing-build-steps" agent skill from https://github.com/quarkusio/quarkus/tree/main/.agents/skills/writing-build-steps into .agents/skills/writing-build-steps/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-build-steps", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add quarkusio/quarkus --skill writing-build-steps -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install quarkusio/quarkus writing-build-steps --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/quarkusio/quarkus.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/writing-build-steps .cursor/skills/writing-build-steps && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "writing-build-steps" agent skill from https://github.com/quarkusio/quarkus/tree/main/.agents/skills/writing-build-steps into .cursor/skills/writing-build-steps/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-build-steps", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/quarkusio/quarkus.git --path .agents/skills/writing-build-steps--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add quarkusio/quarkus --skill writing-build-steps -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install quarkusio/quarkus writing-build-steps --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/quarkusio/quarkus.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/writing-build-steps .gemini/skills/writing-build-steps && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "writing-build-steps" agent skill from https://github.com/quarkusio/quarkus/tree/main/.agents/skills/writing-build-steps into .gemini/skills/writing-build-steps/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-build-steps", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install quarkusio/quarkus writing-build-stepsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add quarkusio/quarkus --skill writing-build-steps -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/quarkusio/quarkus.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/writing-build-steps .github/skills/writing-build-steps && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "writing-build-steps" agent skill from https://github.com/quarkusio/quarkus/tree/main/.agents/skills/writing-build-steps into .github/skills/writing-build-steps/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-build-steps", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add quarkusio/quarkus --skill writing-build-steps -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install quarkusio/quarkus writing-build-steps --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/quarkusio/quarkus.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/writing-build-steps .opencode/skills/writing-build-steps && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "writing-build-steps" agent skill from https://github.com/quarkusio/quarkus/tree/main/.agents/skills/writing-build-steps into .opencode/skills/writing-build-steps/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-build-steps", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
writing-build-stepsPatterns 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.
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.
Read from SKILL.md and the folder at commit d58d0eb. It shows what the files ask for, not the result of running them.
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.
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.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
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.
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.
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.
The full file from quarkusio/quarkus at commit d58d0eb, republished under its Apache-2.0 licence (© quarkusio). 422 words, ~880 tokens.
.claude/skills/writing-build-steps/SKILL.md (or your agent's skills folder).Quarkus extensions perform work at build time through build steps that produce and consume build items. This is the core extension mechanism.
A build step is a method annotated with @BuildStep in a processor class
(by convention <Feature>Processor.java in the deployment module).
@BuildStep
SomeBuildItem produce(AnotherBuildItem input) {
// Build-time logic
return new SomeBuildItem(...);
}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).final classes.BuildItem, it runs after all producers of that itemBuildProducer<T> when you need to produce multiple instances of the
same item type or produce items conditionallyOptional<T> for optional consumption of build itemsList<T> to consume all instances of a MultiBuildItem@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.
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.
@BuildStep
@Record(ExecutionTime.RUNTIME_INIT)
void setupAtRuntime(MyRecorder recorder, SomeBuildItem item) {
recorder.initialize(item.getValue());
}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).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
Just SKILL.md in .agents/skills/writing-build-steps of quarkusio/quarkus.
Open the folder on GitHubat commit d58d0eb
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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Writing Build Steps this skillquarkusio/quarkus | 16k | — | ~880 | Automated safety check: Pass | Apache-2.0 | |
| Docker Jfr Benchmark Loopeclipse-rdf4j/rdf4j | 420 | — | ~945 | Automated safety check: Pass | BSD-3-Clause | |
| Apm IntegrationsDataDog/dd-trace-java | 736 | — | ~3.7k | Automated safety check: Notes | Apache-2.0 | |
| Opik Local Dev Environmentcomet-ml/opik | 22k | — | ~734 | Automated safety check: Pass | Apache-2.0 | |
| Pi K8s Deployrodrigorodrigues/microservices-design-patterns | 187 | — | ~1.6k | Automated safety check: Pass | None | |
| Coastline Rendering Testosmandapp/OsmAnd-tools | 116 | — | ~2.5k | Automated safety check: Pass | Custom licence |
eclipse-rdf4j/rdf4j
Run a repeatable RDF4J performance loop against one JMH benchmark in Docker with Linux Java 26 and JFR CPU-time profiling.
DataDog/dd-trace-java
Write a new library instrumentation end-to-end. An agent skill from DataDog/dd-trace-java.
comet-ml/opik
Starts, rebuilds, and troubleshoots the Opik local dev stack, including an optional Comet Platform integration mode for the Opik team.
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…
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…
a2aproject/a2a-java
Guide maintainers through the multi-step release process — version bump, CI verification, tagging, Maven Central deployment, SNAPSHOT bump, and versioned documentation.
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…
quarkusio/quarkus
How to build and test Quarkus: Maven commands, build flags, incremental builds, justfile aliases, and important build rules.
quarkusio/quarkus
How to build, preview, and verify Quarkus documentation locally: root Maven build, docs rebuild, Roq dev server preview.
quarkusio/quarkus
Quarkus split classloading model, runtime-dev module wiring, conditional dependencies, and common classloading mistakes.
quarkusio/quarkus
Step-by-step guide for converting Quarkus extensions from the legacy @Record/@Recorder pattern to the ServiceRegistrar service system.
quarkusio/quarkus
How to create a new Quarkus extension: full module layout, package naming, artifact naming, dependency rules, and Dev UI setup.
Works with
Categories
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.
Writing Build Steps fits situations like: devOps & Cloud work in your project.
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.
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.
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.
SKILL.md names no scripts, command-line tools or credentials: Writing Build Steps is instructions for the agent only.
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.
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.
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.
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.
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.
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.