Quarkus Application Development

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 (Java, Maven or Gradle, the Quarkus CLI is optional). No account, no API key and no paid service is needed to install or use the skill itself. At use time, adding extensions downloads artifacts from your configured Maven or Gradle repositories. Following the skill can lead you to add infrastructure dependencies (Kafka, OIDC or Keycloak): the skill says to ask you first, and those services run as Dev Services containers (Docker or Podman) in dev and test, or as your own deployed services in production, at your own cost if you host them somewhere paid. The skill itself sends nothing: no project code or data is uploaded by the skill. Install "Quarkus Application Development" for me. Application development inside an existing Quarkus project. The skill starts by detecting the project version, Java release and extensions already present, adds extensions only through the Quarkus CLI or Maven commands (never guessed artifact ids), and follows explicit agent rules: ask before adding Kafka, OIDC or Keycloak or any new infrastructure dependency, never use the Spring compatibility extensions unless the project already does, use jakarta imports and records for DTOs, and never hard code secrets. It routes each need to a reference file: REST and validation, typed configuration and CDI, Hibernate ORM with Panache, Mutiny and virtual threads, Reactive Messaging with Kafka, OIDC security, observability, resilience, REST client, scheduler and cache. Six reference files ship with SKILL.md. Repository: https://github.com/github/awesome-copilot (the skill is the whole skills/quarkus-application-development/ folder at the pinned commit: SKILL.md, references/config-cdi.md, references/observability-resilience.md, references/persistence.md, references/reactive-messaging.md, references/rest.md, references/security-oidc.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-application-development/ 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 16aa261f5e2d44a3d98e6fbd33f20d867c615a786424209598f50b9ecc11aa54 - references/config-cdi.md: SHA-256 54a4860807e0e154e3ddf462262f1eded6d62fcb90e347e74b2150d6c7d64849 - references/observability-resilience.md: SHA-256 60d701b476141627e297fe4d947668c30959368863423e0580755d3076f26e39 - references/persistence.md: SHA-256 e6350a1bcc97664a6566ed6452a78200b5b21f1454512b5a9dde57ef15206b5e - references/reactive-messaging.md: SHA-256 4b67115a7431e20577d6881efc5f1fbc4524cbf3ccfb8b6971de737865339724 - references/rest.md: SHA-256 5ee5572694fc475edc6c6cf3668cac564a75eae42b80fb5b12acf4bbe2e64d0e - references/security-oidc.md: SHA-256 1a5c5623bd77ce17fc9078b9710989d44a00e142dd74833c79f3b7870602bce8 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 7 files: SKILL.md plus six reference files in references/ (REST, config and CDI, persistence, reactive messaging, security OIDC, observability and resilience). There is no executable code of its own. - Nothing is sent anywhere during installation itself; the only download is the skill folder from GitHub at the pinned commit. At use time, extension downloads come from your configured Maven or Gradle repositories only. - The agent rules in SKILL.md require asking you before adding Kafka, OIDC or Keycloak or any new infrastructure dependency, and forbid hard coding secrets or credentials in application.properties. - Project creation, Dev Services testing and native or container builds are out of scope here: they belong to the companion Quarkus skills in the same repository. 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-application-development", keeping every file (SKILL.md, references/config-cdi.md, references/observability-resilience.md, references/persistence.md, references/reactive-messaging.md, references/rest.md, references/security-oidc.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.