Create Quarkus Project
Scaffold a new Quarkus project with Maven or Gradle, pick the right extensions, and run it in dev mode.
- What
- Scaffold a new Quarkus project with Maven or Gradle, pick the right extensions, and run it in dev mode.
- Cost
- Free
- Needs
- 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.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — Scaffold a new Quarkus application or REST API. The skill first detects the environment (Java version, Quarkus CLI, Maven or Gradle) and refuses to scaffold over an existing Quarkus project. For a new project it uses the stream marked recommended on code.quarkus.io (an LTS stream), scaffolds with the Quarkus CLI, the Maven plugin or the code.quarkus.io API, helps choose extensions from a table (REST with Jackson, Hibernate ORM with Panache, validation, health and metrics, OIDC or JWT auth, OpenAPI, REST client, container images), and runs the result in dev mode with live reload, the Dev UI and Dev Services. It ships five reference files on configuration, databases, security basics, container images and local runtime insights. By @github, listed here with credit to its creator. MIT-licensed. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Copy the install package below, then paste it into Muse📌 Pinned version: commit cb64ad1The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
- It can contact outside services over the network.
- It can create or modify files.
What the scan found — excerpts from the install prompt
- makes network calls — Prerequisites: Local Java tools only: Java 17, 21 or 25, and Maven or Gradle (the Quarkus CLI is optional). No · Prérequis : Outils Java locaux seulement : Java 17, 21 ou 25, et Maven ou Gradle (la CLI Quarkus est optionnel
- writes files — 3. When I say "yes, install", install it as a skill: copy the whole folder into the agent's skills directory, · 3. Quand je dis « yes, install », installe-le comme skill : copie tout le dossier dans le répertoire des skill
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: Local Java tools only: Java 17, 21 or 25, and 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, scaffolding contacts code.quarkus.io (the skill reads https://code.quarkus.io/api/streams to pick the recommended stream, and one scaffold route generates the project through the code.quarkus.io API) and Maven or Gradle downloads the Quarkus platform and extensions from the configured repositories (Maven Central by default). Dev Services and container work at use time also need Docker or Podman and pull container images. Nothing else is sent: the project name, group id and extension list go to code.quarkus.io only if you use that generation route. Install "Create Quarkus Project" for me. Scaffold a new Quarkus application or REST API. The skill first detects the environment (Java version, Quarkus CLI, Maven or Gradle) and refuses to scaffold over an existing Quarkus project. For a new project it uses the stream marked recommended on code.quarkus.io (an LTS stream), scaffolds with the Quarkus CLI, the Maven plugin or the code.quarkus.io API, helps choose extensions from a table (REST with Jackson, Hibernate ORM with Panache, validation, health and metrics, OIDC or JWT auth, OpenAPI, REST client, container images), and runs the result in dev mode with live reload, the Dev UI and Dev Services. It ships five reference files on configuration, databases, security basics, container images and local runtime insights. Repository: https://github.com/github/awesome-copilot (the skill is the whole skills/create-quarkus-project/ folder at the pinned commit: SKILL.md, references/configuration.md, references/container-image.md, references/database.md, references/local-runtime-insights.md, references/security.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/create-quarkus-project/ 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 91be9b0c947bf8c7a0a38f77e1d078e4851dfbd183a38bd1259ee41580e45bb0 - references/configuration.md: SHA-256 2989d1e1e2f01628a90bf28fecb0761feb7f5ef266c785a94e95cd8ade0cfa6f - references/container-image.md: SHA-256 436b301526af25f69b6d25ca7afcd7d29d311d6a644cbfb3a734ca992fc76da4 - references/database.md: SHA-256 dd31085022c09bb9a978357181a9c1e2fa74f22a76be771e517c6ee842cb2205 - references/local-runtime-insights.md: SHA-256 0d3b83c223fd7d6ce0cb12dc947f3e37a4be7ebc72a77bce04ebd351cec7bedd - references/security.md: SHA-256 76028946cf8ba9a2f1e15e25da30d1a5c0f1082a2069fc2da04629c8d3cec5c0 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 6 files: SKILL.md plus five reference files in references/ (configuration, database, security, container image and local runtime insights). There is no executable code of its own: the commands it proposes are the standard java, quarkus, mvn and gradle commands shown in SKILL.md. - Nothing is sent anywhere during installation itself; the only download is the skill folder from GitHub at the pinned commit. - At use time the network contacts are the ones disclosed in the prerequisites: code.quarkus.io for the stream check and the optional generation route, and your configured Maven or Gradle repositories for the platform and extensions. Dev Services pull container images with Docker or Podman. - The references warn never to commit secrets: project configuration should use environment variables, Kubernetes secrets or vault expressions such as ${DB_PASSWORD}, never plain credentials in files. 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 "create-quarkus-project", keeping every file (SKILL.md, references/configuration.md, references/container-image.md, references/database.md, references/local-runtime-insights.md, references/security.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.
Saved to your recent installs. Find it anytime on /connect.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.