Quarkus Native and Container

Before you start: read this whole install prompt, tell me in a few lines what this skill does and what installing it involves, and wait for my go-ahead before you do anything else. Prerequisites: An existing Quarkus project and local Java tools, plus a container runtime or a JDK for native work: Docker or Podman for container builds (which pull a Mandrel builder image from quay.io), or a local Mandrel or GraalVM install for local native builds. No account, no API key and no paid service is needed to install or use the skill itself. At use time, pushing a container image sends that image to the registry you name, with your own registry credentials, and deploying sends the generated manifests to your own Kubernetes or OpenShift cluster with kubectl or oc and your own cluster credentials: both happen only when you run those commands. Cloud clusters or registries you choose may cost money on your own accounts. The skill itself sends nothing during installation. Install "Quarkus Native and Container" for me. Native executables, container images and Kubernetes or OpenShift manifests for a Quarkus project. The skill covers both native build routes (container build with Docker or Podman and no local GraalVM, or a local Mandrel or GraalVM install), the version gates between Quarkus lines, a table of common native failures and their fixes (reflection registration, missing resources, build time initialization, memory), testing the native binary with QuarkusIntegrationTest, building images with Jib or Docker extensions, and generating and customizing Kubernetes and OpenShift manifests, with a reminder to review generated YAML and keep secrets out of it. Native builds are slow and memory hungry (several GB) and are best done in CI or on demand. A single SKILL.md file. Repository: https://github.com/github/awesome-copilot (the skill is the whole skills/quarkus-native-and-container/ folder at the pinned commit: SKILL.md) Pinned version: install the code at commit cb64ad12e32737ae764becd6885462e9b4c7cb00 exactly. Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Clone https://github.com/github/awesome-copilot into a temporary folder, check out commit cb64ad12e32737ae764becd6885462e9b4c7cb00, and copy the skills/quarkus-native-and-container/ folder from that checkout. Then compare every file in the folder with the fingerprints recorded for this listing on 2026-10-18: [FINGERPRINTS] - SKILL.md: SHA-256 93c9cd356b4c28b0c393a59e73381ed61939c516585135e9ee0801d4c570d95c If a file does not match, it changed since the listing was prepared: do not install it yet, tell me what you found and let me decide. 2. Read SKILL.md in full (and every other file in the folder) and tell me in plain words: what the skill does when used, which services it connects to, whether it reads or sends any personal information or keys, and anything that seems unusual. Stop on any red flag and tell me before going further. Confirm these points from the files: - The skill folder holds one file only: SKILL.md. There is no executable code and no companion file. - Nothing is sent anywhere during installation itself; the only download is the skill file from GitHub at the pinned commit. - At use time the downloads are the Mandrel builder image from quay.io for container builds and your Maven or Gradle artifacts. A registry push or a cluster deployment happens only through the commands shown, to the registry or cluster you name, with your own credentials. - The skill tells you to review generated Kubernetes YAML before applying it and to keep secrets out of it, referencing secrets by name (env.secrets) instead of values. 3. When I say "yes, install", install it as a skill: copy the whole folder into the agent's skills directory, in a folder named "quarkus-native-and-container", keeping every file (SKILL.md). 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (for example: sign in or create an account, provide any API key, or install any local tool named in the prerequisites; using the skill is a separate step that only starts when I ask for it, and every paid or authenticated use disclosed above happens only then). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.