Kafka Configuration
Amplicode/spring-skills
Configures Spring Boot's Kafka starter through application.properties / application.yml.
A skill your agent uses when implementing Kafka, RabbitMQ, Pulsar, or JMS producers and consumers in Spring Boot 4.
Install Event Driven Messaging
$ npx skills add rrezartprebreza/spring-boot-skills --skill event-driven-messaging -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install rrezartprebreza/spring-boot-skills event-driven-messaging --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/rrezartprebreza/spring-boot-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/spring-boot-4/event-driven-messaging .claude/skills/event-driven-messaging && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "event-driven-messaging" agent skill from https://github.com/rrezartprebreza/spring-boot-skills/tree/main/skills/spring-boot-4/event-driven-messaging into .claude/skills/event-driven-messaging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "event-driven-messaging", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/rrezartprebreza/spring-boot-skills/tree/main/skills/spring-boot-4/event-driven-messagingType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add rrezartprebreza/spring-boot-skills --skill event-driven-messaging -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install rrezartprebreza/spring-boot-skills event-driven-messaging --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rrezartprebreza/spring-boot-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/spring-boot-4/event-driven-messaging .agents/skills/event-driven-messaging && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "event-driven-messaging" agent skill from https://github.com/rrezartprebreza/spring-boot-skills/tree/main/skills/spring-boot-4/event-driven-messaging into .agents/skills/event-driven-messaging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "event-driven-messaging", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add rrezartprebreza/spring-boot-skills --skill event-driven-messaging -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install rrezartprebreza/spring-boot-skills event-driven-messaging --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rrezartprebreza/spring-boot-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/spring-boot-4/event-driven-messaging .cursor/skills/event-driven-messaging && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "event-driven-messaging" agent skill from https://github.com/rrezartprebreza/spring-boot-skills/tree/main/skills/spring-boot-4/event-driven-messaging into .cursor/skills/event-driven-messaging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "event-driven-messaging", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/rrezartprebreza/spring-boot-skills.git --path skills/spring-boot-4/event-driven-messaging--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add rrezartprebreza/spring-boot-skills --skill event-driven-messaging -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install rrezartprebreza/spring-boot-skills event-driven-messaging --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rrezartprebreza/spring-boot-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/spring-boot-4/event-driven-messaging .gemini/skills/event-driven-messaging && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "event-driven-messaging" agent skill from https://github.com/rrezartprebreza/spring-boot-skills/tree/main/skills/spring-boot-4/event-driven-messaging into .gemini/skills/event-driven-messaging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "event-driven-messaging", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install rrezartprebreza/spring-boot-skills event-driven-messagingInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add rrezartprebreza/spring-boot-skills --skill event-driven-messaging -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/rrezartprebreza/spring-boot-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/spring-boot-4/event-driven-messaging .github/skills/event-driven-messaging && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "event-driven-messaging" agent skill from https://github.com/rrezartprebreza/spring-boot-skills/tree/main/skills/spring-boot-4/event-driven-messaging into .github/skills/event-driven-messaging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "event-driven-messaging", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add rrezartprebreza/spring-boot-skills --skill event-driven-messaging -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install rrezartprebreza/spring-boot-skills event-driven-messaging --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rrezartprebreza/spring-boot-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/spring-boot-4/event-driven-messaging .opencode/skills/event-driven-messaging && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "event-driven-messaging" agent skill from https://github.com/rrezartprebreza/spring-boot-skills/tree/main/skills/spring-boot-4/event-driven-messaging into .opencode/skills/event-driven-messaging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "event-driven-messaging", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
event-driven-messaging- GitHub stars
- 301
- Token cost
- ~657 tokens
- SKILL.md length
- 277 words
- Files
- 5
- Skills in repo
- 51
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when implementing Kafka, RabbitMQ, Pulsar, or JMS producers and consumers in Spring Boot 4.
- Implementing Kafka
- SKILL.md covers Dependencies and contracts, Producer rules, Consumer rules and Testing, plus 3 more sections
- Runs Java scripts from its folder
- JMS producers and consumers in Spring Boot 4
What it does
Event Driven Messaging is an agent skill from rrezartprebreza/spring-boot-skills. Use when implementing Kafka, RabbitMQ, Pulsar, or JMS producers and consumers in Spring Boot 4. Covers modular starters, event contracts, idempotency, retries, dead letters, and outbox delivery.
Its SKILL.md is about 660 tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files (for example `agents/openai.yaml` and `examples/good-kafka.yml`).
It sits in Backend & APIs, covering Event-driven systems and Backend development. It works with Spring Boot and Apache Kafka. The repository describes itself as: Production-grade Claude Code and Codex skills for Spring Boot developers. The licence is MIT.
When your agent uses it
- Implementing Kafka
- JMS producers and consumers in Spring Boot 4
Example prompts
- “/event-driven-messaging”
What it can do on your machine
Read from SKILL.md and the folder at commit f0c06a0. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships script files (Java), which the agent can run.
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
docs.spring.iogithub.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Event Driven Messaging loads about 657 tokens when it runs. Until then it costs about 54 tokens; SKILL.md has 277 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from rrezartprebreza/spring-boot-skills at commit f0c06a0, republished under its MIT licence (© rrezartprebreza). 277 words, ~657 tokens.
Download SKILL.mdSave it as
.claude/skills/event-driven-messaging/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- event-driven-messaging
- description
- Use when implementing Kafka, RabbitMQ, Pulsar, or JMS producers and consumers in Spring Boot 4. Covers modular starters, event contracts, idempotency, retries, dead letters, and outbox delivery.
Event-Driven Messaging
Design for at-least-once delivery unless the complete system proves stronger semantics.
Dependencies and contracts
- Use the dedicated Boot 4 starter and matching technology test starter.
- Let Boot manage Spring Kafka, AMQP, Pulsar, and Integration versions.
- Publish immutable envelopes containing event ID, type, timestamp, schema version, and payload.
- Treat event schemas as public APIs and evolve them compatibly.
- Do not serialize JPA entities or internal Jackson configuration as contracts.
Producer rules
- Publish only after the originating state is durable.
- Use a transactional outbox when a database write and message must agree.
- Choose a stable aggregate key when per-aggregate ordering matters.
- Configure acknowledgements, delivery timeout, and serialization failure behavior explicitly.
Consumer rules
- Make every handler idempotent with a durable marker or naturally idempotent state transition.
- Commit the state change and idempotency marker in one transaction.
- Retry only transient failures with bounded exponential backoff.
- Route permanent or exhausted failures to a dead-letter destination with diagnostic headers.
- Build replay as an explicit operation with authorization and auditability.
Testing
- Use the Boot 4 technology test starter and Testcontainers for broker integration.
- Test duplicate, reordered, delayed, incompatible, and poison events.
- Verify schema compatibility independently from handler tests.
Examples
- See
examples/good-consumer.java,examples/good-kafka.yml, andexamples/bad-consumer.java.
Official sources
- Boot 4 messaging starters: https://github.com/spring-projects/spring-boot/wiki/Spring-Boot-4.0-Migration-Guide#starters
- Spring Kafka reference: https://docs.spring.io/spring-kafka/reference/
- Spring AMQP reference: https://docs.spring.io/spring-amqp/reference/
Gotchas
- Agent assumes broker transactions make external side effects exactly once - consumers still need idempotency.
- Agent retries every exception - classify permanent failures before retrying.
- Agent publishes directly after a repository call - use an outbox when atomicity matters.
- Agent uses old Boot 3 transitive dependencies - declare the Boot 4 messaging and test starters.
- Agent sends framework entities as events - publish a stable versioned contract.
© rrezartprebreza, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 4 other files in skills/spring-boot-4/event-driven-messaging of rrezartprebreza/spring-boot-skills.
- SKILL.md
- agents/openai.yaml
- examples/bad-consumer.java
- examples/good-consumer.java
- examples/good-kafka.yml
Open the folder on GitHubat commit f0c06a0
Compare with similar skills
Event Driven Messaging next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Event Driven Messaging this skillrrezartprebreza/spring-boot-skills | 301 | — | ~657 | Automated safety check: Pass | MIT | |
| Kafka ConfigurationAmplicode/spring-skills | 128 | — | ~4k | Automated safety check: Pass | None | |
| 314 Frameworks Spring Kafkajabrena/plinth | 447 | — | ~561 | Automated safety check: Pass | Apache-2.0 | |
| 323 Frameworks Spring Boot Testing Acceptance Testsjabrena/plinth | 447 | — | ~1.2k | Automated safety check: Pass | Apache-2.0 | |
| Spring Boot Event Driven Patternsgiuseppe-trisciuoglio/developer-kit | 357 | — | ~2.3k | Automated safety check: Notes | MIT | |
| Spring Boot Saga Patterngiuseppe-trisciuoglio/developer-kit | 357 | — | ~2.5k | Automated safety check: Notes | MIT |
Similar skills
314 Frameworks Spring Kafka
jabrena/plinth
A skill your agent uses when you need to design or implement Kafka messaging in Spring Boot — including topic design, producer/consumer implementation, JSON serialization with Boot factory…
323 Frameworks Spring Boot Testing Acceptance Tests
jabrena/plinth
A skill your agent uses when you need to implement acceptance tests from maintainer-authored or maintainer-sanitized Gherkin scenario facts for Spring Boot applications — including selecting…
Spring Boot Event Driven Patterns
giuseppe-trisciuoglio/developer-kit
Provides Event-Driven Architecture (EDA) patterns for Spring Boot — creates domain events, configures ApplicationEvent and @TransactionalEventListener, sets up Kafka producers and consumers, and…
Spring Boot Saga Pattern
giuseppe-trisciuoglio/developer-kit
Provides distributed transaction patterns using the Saga Pattern for Spring Boot microservices.
133 Java Testing Acceptance Tests
jabrena/plinth
A skill your agent uses when you need to implement acceptance tests from maintainer-sanitized Gherkin scenario facts for framework-agnostic Java (no Spring Boot, Quarkus, Micronaut) — confirming…
More from rrezartprebreza/spring-boot-skills
All 51 skills in this repoAI Observability
rrezartprebreza/spring-boot-skills
A skill your agent uses when adding Spring AI-specific model observations, token usage, latency, externally configured cost attribution, advisor telemetry, or protected prompt and completion logging.
API Versioning
rrezartprebreza/spring-boot-skills
A skill your agent uses when versioning Spring MVC or WebFlux APIs in Spring Boot 3 / Spring Framework 6.
API Versioning
rrezartprebreza/spring-boot-skills
A skill your agent uses when versioning Spring MVC or WebFlux APIs in Spring Boot 4 / Spring Framework 7.
Container Native Deployment
rrezartprebreza/spring-boot-skills
A skill your agent uses when packaging a Spring Boot 3 application as an OCI image or GraalVM native executable.
Container Native Deployment
rrezartprebreza/spring-boot-skills
A skill your agent uses when packaging Spring Boot 4 as an OCI image, JVM container, AOT application, or GraalVM native executable.
Domain Driven Design
rrezartprebreza/spring-boot-skills
A skill your agent uses when evolving aggregate invariants, value objects or domain events in an existing DDD-style Spring Boot 3 application, or when DDD is explicitly requested.
Related
Works with
Categories
Questions about Event Driven Messaging
What does Event Driven Messaging do?
A skill your agent uses when implementing Kafka, RabbitMQ, Pulsar, or JMS producers and consumers in Spring Boot 4. Event Driven Messaging is an agent skill from rrezartprebreza/spring-boot-skills. Use when implementing Kafka, RabbitMQ, Pulsar, or JMS producers and consumers in Spring Boot 4.
When should I use Event Driven Messaging?
Event Driven Messaging fits situations like: implementing Kafka; JMS producers and consumers in Spring Boot 4.
How do I install Event Driven Messaging in Claude Code?
Run `npx skills add rrezartprebreza/spring-boot-skills --skill event-driven-messaging -a claude-code`. Or copy the skill folder (skills/spring-boot-4/event-driven-messaging in rrezartprebreza/spring-boot-skills) into .claude/skills/event-driven-messaging in your project. Claude Code loads it when a task matches its description.
How do I install Event Driven Messaging in Codex?
Run `npx skills add rrezartprebreza/spring-boot-skills --skill event-driven-messaging -a codex`. Or copy the skill folder (skills/spring-boot-4/event-driven-messaging in rrezartprebreza/spring-boot-skills) into .agents/skills/event-driven-messaging in your project. Codex loads it when a task matches its description.
Can I use Event Driven Messaging in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add rrezartprebreza/spring-boot-skills --skill event-driven-messaging -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/event-driven-messaging, .gemini/skills/event-driven-messaging, .github/skills/event-driven-messaging and .opencode/skills/event-driven-messaging in your project.
What does Event Driven Messaging need to run?
Going by SKILL.md and its folder, Event Driven Messaging needs Java for the scripts in its folder.
Does Event Driven Messaging access the network?
SKILL.md names 2 domains. As links in the text: docs.spring.io and github.com. This is read from the text; nothing was executed.
Is Event Driven Messaging safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Event Driven Messaging use?
Event Driven Messaging is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Event Driven Messaging use?
About 657 tokens (SKILL.md is roughly 2.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Event Driven Messaging?
Skills that share tags, products or a category with Event Driven Messaging: Kafka Configuration (Amplicode/spring-skills, 128 stars), 314 Frameworks Spring Kafka (jabrena/plinth, 447 stars), 323 Frameworks Spring Boot Testing Acceptance Tests (jabrena/plinth, 447 stars) and Spring Boot Event Driven Patterns (giuseppe-trisciuoglio/developer-kit, 357 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Event Driven Messaging?
rrezartprebreza (a GitHub user) maintains it in rrezartprebreza/spring-boot-skills, which has 301 GitHub stars. The repository holds 51 skills in this directory. The repository was last updated on September 21, 2026.
Source: rrezartprebreza/spring-boot-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.