414 frameworks quarkus kafka
Plinth is an AI-native engineering toolkit for modern Java enterprise SDLC, built around reusable Commands, Agents, Skills, and MCP Servers.
npx -y skills add jabrena/plinth --skill 414-frameworks-quarkus-kafkaAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
What its author says it does
Copied from the file, not written here
Use when you need Kafka messaging in Quarkus with SmallRye Reactive Messaging — including channel/topic design, build-time Jackson serialization, typed @Channel/@Incoming, ack/failure strategies, retries/DLQ, idempotency, Dev Services, and Testcontainers integration tests. This should trigger for requests such as Add Kafka in Quarkus; Review Reactive Messaging consumers; Improve failure handling for Quarkus Kafka; Configure Quarkus Reactive Messaging Kafka channels; Add Quarkus Kafka failure strategy or DLQ handling. Part of Plinth Toolkit
The file declares its own license as Apache-2.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
2.2 KB, as published. Nobody here has run it
Quarkus — Kafka messaging
Apply Quarkus Kafka guidance with concrete examples for design, implementation, and error handling.
Constraints
Compile before messaging refactors; verify after changes.
- MANDATORY: Run
./mvnw compileormvn compilebefore applying any change - SAFETY: If compilation fails, stop immediately
- VERIFY: Run
./mvnw clean verifyormvn clean verifyafter applying improvements - BEFORE APPLYING: Read the reference for detailed rules and examples
When to use this skill
- Add Kafka in Quarkus
- Review Quarkus Reactive Messaging consumers/producers
- Improve retries, dead-letter handling, or idempotency in Quarkus Kafka
- Configure Quarkus Reactive Messaging Kafka channels
- Add Quarkus Kafka failure strategy or DLQ handling
Workflow
- Read reference and assess project context
Read references/414-frameworks-quarkus-kafka.md and inspect current messaging setup before proposing changes.
- Gather scope and decide target improvements
Identify delivery semantics and resilience goals to define safe improvements.
- Apply framework-aligned changes
Implement/refactor channels, serializers, and failure strategies in Reactive Messaging.
- Run verification and report results
Execute build/tests and summarize what changed, what was verified, and follow-up actions.
Reference
For detailed guidance, examples, and constraints, see references/414-frameworks-quarkus-kafka.md.