Token导航 LogoToken导航

Agent Skill · 研究检索

quarkus(quarkus 搜索)

quarkus 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

quarkus 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为需要联网;许可证信息还不明确,第三方扫描已通过,按安装量在研究检索类的 73,675 个 Skill 里排第 72,323。

总安装 188周安装 8GitHub Stars 8下载 66核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:quarkus(quarkus 搜索)
来源仓库:https://github.com/ar4mirez/samuel
仓库路径:skills/quarkus
安装命令:
npx skills add https://github.com/ar4mirez/samuel --skill quarkus
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/ar4mirez/samuel --skill quarkus

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

quarkus 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词快速定位候选结果时使用。适用于 Java 17+ 云原生微服务、Kubernetes 部署和 GraalVM 原生应用开发。

通过 npx skills add 命令从指定 GitHub 仓库安装,需结合原始 README 核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写操作。当前无详细 SKILL.md 内容,需参考仓库中的 Quarkus Guide 了解 Kubernetes 原生特性和扩展机制。

来源仓库内路径:skills/quarkus

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/ar4mirez/samuel --skill quarkus;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要需要联网,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

quarkus 怎么安装?

在终端执行 npx skills add https://github.com/ar4mirez/samuel --skill quarkus。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

quarkus 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

quarkus 需要什么权限?

权限级别是需要联网。该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

quarkus 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

quarkus 用的人多吗?

公开数据是累计安装 188 次,近一周安装 8 次,下载 66 次,GitHub 8 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

quarkus 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
quarkus

quarkus 搜索 · 本页

1888需要联网未明确通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

Quarkus Guide

Applies to: Quarkus 3.x, Java 17+, Cloud-Native Microservices, GraalVM Native, Kubernetes

Core Principles

  1. Kubernetes-Native: Designed for containers, fast startup, low memory footprint
  2. Developer Joy: Live reload via Dev Services, Dev UI, continuous testing
  3. Unified Reactive/Imperative: Choose per-endpoint, both coexist in one app
  4. Build-Time Optimization: Extensions process metadata at build time, not runtime
  5. GraalVM First-Class: Native compilation with millisecond startup and minimal RSS
  6. Standards-Based: MicroProfile, Jakarta EE, Vert.x, SmallRye under the hood

Guardrails

Project & Dependencies

  • Use Quarkus BOM for version management (never pin individual Quarkus artifact versions)
  • Add extensions via ./mvnw quarkus:add-extension rather than editing pom.xml manually
  • Run ./mvnw quarkus:dev for live reload; never restart manually during development
  • Use Dev Services (auto-provisioned containers) for databases, Kafka, Redis in dev/test
  • Keep application.properties profile-aware: %dev., %test., %prod. prefixes

CDI (Contexts and Dependency Injection)

  • Use @ApplicationScoped for stateless services (one instance per app)
  • Use @RequestScoped only when you need per-request state
  • Prefer constructor injection or @Inject fields (constructor preferred for testability)
  • Avoid @Dependent scope unless you need a new instance per injection point
  • Use @Startup for beans that must initialize eagerly at boot
  • Register beans for native with @RegisterForReflection only when reflection is required
  • Produce CDI beans via @Produces methods for third-party objects

RESTEasy Reactive Resources

  • Use RESTEasy Reactive (quarkus-resteasy-reactive), not classic RESTEasy
  • Return Uni<T> or Multi<T> for non-blocking I/O; plain types for blocking is acceptable
  • Keep resource classes thin: validate input, delegate to service, map response
  • Use @Valid on request parameters for Bean Validation
  • Annotate with @Produces(APPLICATION_JSON) and @Consumes(APPLICATION_JSON)
  • Use @Path versioning: /api/v1/resource
  • Add OpenAPI annotations (@Operation, @APIResponse) on every endpoint
  • Secure endpoints with @RolesAllowed, @Authenticated, or @PermitAll

Panache ORM

  • Active Record (extends PanacheEntity): good for simple CRUD entities
  • Repository (implements PanacheRepository<T>): good for complex queries, better testability
  • Use Uni<T> return types with hibernate-reactive-panache for non-blocking DB access
  • Add custom finder methods on entity or repository (e.g., findByEmail)
  • Use @WithTransaction on service methods that write, not on resources
  • Set quarkus.hibernate-orm.database.generation=validate and manage schema via Flyway
  • Always provide @PrePersist / @PreUpdate for audit timestamps

Configuration

  • Use application.properties with profile prefixes: %dev., %test., %prod.
  • Inject config values with @ConfigProperty(name = "key", defaultValue = "fallback")
  • Group related config with @ConfigMapping interfaces
  • Never hardcode secrets; use ${ENV_VAR:default} placeholder syntax
  • Enable Dev Services for local containers: quarkus.devservices.enabled=true

Error Handling

  • Create domain exceptions: ResourceNotFoundException, DuplicateResourceException
  • Register JAX-RS @Provider classes implementing ExceptionMapper<T>
  • Return structured error bodies: {title, status, detail, timestamp}
  • Map ConstraintViolationException to 400 with per-field error details
  • Log at WARN for client errors, ERROR for unexpected failures

Native Build Compatibility

  • Avoid runtime reflection (use @RegisterForReflection when unavoidable)
  • Avoid dynamic proxies and runtime bytecode generation
  • Test native build regularly: ./mvnw verify -Pnative
  • Use @BuildStep extensions for build-time processing
  • Prefer compile-time DI and annotation processors (MapStruct, Panache)
  • Use quarkus.native.container-build=true to build without local GraalVM

Project Structure

myproject/
├── src/main/java/com/example/
│   ├── resource/              # JAX-RS endpoints (thin controllers)
│   │   ├── UserResource.java
│   │   └── AuthResource.java
│   ├── service/               # Business logic
│   │   └── UserService.java
│   ├── repository/            # Panache repositories (optional if using active record)
│   │   └── UserRepository.java
│   ├── entity/                # JPA entities with Panache
│   │   └── User.java
│   ├── dto/                   # Request/response records
│   │   ├── UserRequest.java
│   │   └── UserResponse.java
│   ├── mapper/                # MapStruct mappers (compile-time, CDI-scoped)
│   │   └── UserMapper.java
│   ├── exception/             # Domain exceptions + ExceptionMappers
│   │   ├── ResourceNotFoundException.java
│   │   ├── DuplicateResourceException.java
│   │   └── ExceptionMappers.java
│   └── health/                # MicroProfile Health checks
│       └── DatabaseHealthCheck.java
├── src/main/resources/
│   ├── application.properties # Config with profile prefixes
│   └── db/migration/          # Flyway SQL migrations
│       └── V1__create_users.sql
├── src/main/docker/
│   ├── Dockerfile.jvm
│   └── Dockerfile.native
├── src/test/java/com/example/
│   ├── resource/              # @QuarkusTest integration tests
│   │   └── UserResourceTest.java
│   └── service/               # Unit tests with @InjectMock
│       └── UserServiceTest.java
└── pom.xml
  • resource/ -- Thin REST endpoints; input validation and response mapping only
  • service/ -- All business logic; transactional boundaries live here
  • repository/ -- Data access (skip if active record pattern suffices)
  • entity/ -- JPA entities; keep domain logic minimal, push to service
  • dto/ -- Java records for request/response; use Bean Validation annotations
  • mapper/ -- MapStruct interfaces with componentModel = "cdi"
  • exception/ -- Domain exceptions and JAX-RS ExceptionMapper providers
  • health/ -- MicroProfile HealthCheck implementations

CDI Pattern

@ApplicationScoped
public class UserService {

    @Inject
    UserRepository userRepository;

    @Inject
    UserMapper userMapper;

    @WithTransaction
    public Uni<UserResponse> createUser(UserRequest request) {
        return userRepository.existsByEmail(request.email())
            .flatMap(exists -> {
                if (exists) {
                    return Uni.createFrom().failure(
                        new DuplicateResourceException("User", "email", request.email()));
                }
                User user = userMapper.toEntity(request);
                return userRepository.persist(user).map(userMapper::toResponse);
            });
    }

    public Uni<UserResponse> getUserById(Long id) {
        return userRepository.findById(id)
            .onItem().ifNull().failWith(
                () -> new ResourceNotFoundException("User", "id", id))
            .map(userMapper::toResponse);
    }
}

RESTEasy Resource Pattern

@Path("/api/v1/users")
@Produces(MediaType.APPLICATION_JSON)
@Consumes(MediaType.APPLICATION_JSON)
@Tag(name = "Users", description = "User management APIs")
public class UserResource {

    @Inject
    UserService userService;

    @POST
    @Operation(summary = "Create a new user")
    @APIResponse(responseCode = "201", description = "User created")
    public Uni<Response> createUser(@Valid UserRequest request) {
        return userService.createUser(request)
            .map(user -> Response
                .created(URI.create("/api/v1/users/" + user.id()))
                .entity(user).build());
    }

    @GET
    @Path("/{id}")
    @RolesAllowed({"USER", "ADMIN"})
    @SecurityRequirement(name = "jwt")
    @Operation(summary = "Get user by ID")
    public Uni<UserResponse> getUserById(@PathParam("id") Long id) {
        return userService.getUserById(id);
    }
}

Panache Entity Pattern

@Entity
@Table(name = "users")
public class User extends PanacheEntity {

    @Column(nullable = false, unique = true)
    public String email;

    @Column(nullable = false)
    public String name;

    @Column(name = "created_at", updatable = false)
    public LocalDateTime createdAt;

    @PrePersist
    void onCreate() {
        createdAt = LocalDateTime.now();
    }

    // Panache active record queries
    public static Uni<User> findByEmail(String email) {
        return find("email", email).firstResult();
    }

    public static Uni<List<User>> findActive() {
        return list("active", true);
    }
}

DTO Records with Validation

public record UserRequest(
    @NotBlank(message = "Email is required")
    @Email(message = "Invalid email format")
    String email,

    @NotBlank(message = "Password is required")
    @Size(min = 8, max = 100, message = "Password must be 8-100 characters")
    String password,

    @NotBlank(message = "Name is required")
    @Size(min = 2, max = 100)
    String name
) {}

public record UserResponse(
    Long id, String email, String name,
    String role, boolean active, LocalDateTime createdAt
) {}

Exception Mapper Pattern

@Provider
public class ResourceNotFoundMapper
        implements ExceptionMapper<ResourceNotFoundException> {

    @Override
    public Response toResponse(ResourceNotFoundException e) {
        return Response.status(Response.Status.NOT_FOUND)
            .entity(Map.of(
                "title", "Resource Not Found",
                "status", 404,
                "detail", e.getMessage(),
                "timestamp", Instant.now().toString()))
            .build();
    }
}

Configuration

# Application
quarkus.application.name=myproject
quarkus.http.port=8080

# Reactive datasource
quarkus.datasource.db-kind=postgresql
quarkus.datasource.username=${DB_USERNAME:postgres}
quarkus.datasource.password=${DB_PASSWORD:postgres}
quarkus.datasource.reactive.url=vertx-reactive:postgresql://localhost:5432/mydb

# JDBC (for Flyway migrations)
quarkus.datasource.jdbc.url=jdbc:postgresql://localhost:5432/mydb

# Hibernate
quarkus.hibernate-orm.database.generation=validate
quarkus.hibernate-orm.log.sql=true

# Flyway
quarkus.flyway.migrate-at-start=true
quarkus.flyway.locations=db/migration

# Dev Services
%dev.quarkus.datasource.devservices.enabled=true
%dev.quarkus.datasource.devservices.image-name=postgres:15-alpine

# Logging
quarkus.log.level=INFO
quarkus.log.category."com.example".level=DEBUG
%prod.quarkus.log.console.json=true

# JWT
mp.jwt.verify.publickey.location=publicKey.pem
mp.jwt.verify.issuer=https://example.com

# OpenAPI / Swagger
quarkus.smallrye-openapi.path=/api-docs
quarkus.swagger-ui.always-include=true

# Health
quarkus.smallrye-health.root-path=/health

Testing Overview

Standards

  • Use @QuarkusTest for integration tests (full CDI + HTTP stack)
  • Use @InjectMock to mock CDI beans in integration tests
  • Use @TestSecurity(user = "test", roles = "ADMIN") to bypass auth in tests
  • Use REST-assured for HTTP endpoint assertions
  • Use @QuarkusTestResource with Testcontainers for DB integration tests
  • Test native with ./mvnw verify -Pnative (runs @NativeImageTest classes)
  • Use @DisplayName for readable test names describing behavior

Integration Test

@QuarkusTest
@DisplayName("UserResource")
class UserResourceTest {

    @Test
    @DisplayName("POST /api/v1/users - should create user")
    void shouldCreateUser() {
        given()
            .contentType(ContentType.JSON)
            .body(new UserRequest("test@example.com", "Password1!", "Test"))
        .when()
            .post("/api/v1/users")
        .then()
            .statusCode(201)
            .body("id", notNullValue())
            .body("email", equalTo("test@example.com"));
    }

    @Test
    @TestSecurity(user = "admin", roles = "ADMIN")
    @DisplayName("GET /api/v1/users - admin can list users")
    void adminCanListUsers() {
        given()
        .when()
            .get("/api/v1/users")
        .then()
            .statusCode(200);
    }
}

Commands

# Create project
mvn io.quarkus.platform:quarkus-maven-plugin:3.6.0:create \
    -DprojectGroupId=com.example \
    -DprojectArtifactId=myproject \
    -Dextensions="resteasy-reactive-jackson,hibernate-reactive-panache,reactive-pg-client"

# Dev mode (live reload + Dev Services)
./mvnw quarkus:dev

# Run tests
./mvnw test

# Build JVM jar
./mvnw package

# Build native binary
./mvnw package -Pnative

# Build native in container (no local GraalVM)
./mvnw package -Pnative -Dquarkus.native.container-build=true

# Verify native (integration tests against native binary)
./mvnw verify -Pnative

# List available extensions
./mvnw quarkus:list-extensions

# Add extension
./mvnw quarkus:add-extension -Dextensions="openapi"

# Build container image
./mvnw package -Dquarkus.container-image.build=true

# Deploy to Kubernetes
./mvnw package -Dquarkus.kubernetes.deploy=true

# Lint / format
./mvnw compile           # Runs annotation processors
mvn checkstyle:check     # If checkstyle configured

Best Practices Summary

Do

  • Use Dev Services for automatic local containers
  • Use Panache for simpler data access patterns
  • Use reactive types (Uni, Multi) for I/O-bound operations
  • Use @WithTransaction on service methods (not resources)
  • Configure for native compilation early; test regularly
  • Use health checks (@Liveness, @Readiness, @Wellness)
  • Use profile-based configuration (%dev., %test., %prod.)
  • Use MapStruct (compile-time) over reflection-based mappers

Do Not

  • Mix blocking calls in reactive pipelines (use @Blocking annotation if needed)
  • Use runtime reflection without @RegisterForReflection
  • Hardcode configuration values (use @ConfigProperty or @ConfigMapping)
  • Use synchronous JDBC APIs with reactive datasources
  • Ignore native build compatibility until deployment time
  • Put business logic in resource classes

Advanced Topics

For detailed patterns and examples, see:

  • references/patterns.md -- Reactive pipelines, Hibernate Reactive, testing strategies, GraalVM native, messaging, security, observability

External References

平台分布

Codex

37.21%
按下载量换算25

Claude

32.31%
按下载量换算21

Cursor

18.56%
按下载量换算12

Gemini CLI

9.37%
按下载量换算6

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills