Individual skill
event-driven-architect
Designs event-driven systems with CloudEvents schemas, message brokers, idempotency keys, and dead-letter queues.
skills/architecture/event-driven-architect/SKILL.md
Source commit d0a9928d24afb7df0fad2f2f35f65d3938a6926a
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Not checked yet
- Last checked
- Nov 5, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 27
- Repository last updated
- Aug 20, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- claude-code Repository topic
- ai Repository topic
- ai-agents Repository topic
- ai-coding Repository topic
- ai-skill Repository topic
- ai-skill-enhancement Repository topic
- ai-skills Repository topic
- ai-skills-analysis Repository topic
- ai-skills-fest Repository topic
- ai-skills-manager Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
README.mddoc · 585 bytesSKILL.mdcore · 1,785 bytesexamples/example.mddoc · 1,012 bytes
Read excerpt
## Purpose
Architect resilient, decoupled event-driven architectures (EDA) using Kafka, RabbitMQ, SQS/SNS, or NATS, incorporating standardized schema registries, transactional outbox patterns, idempotent consumers, and dead-letter queue (DLQ) retry policies.
## When to Use
- Moving from synchronous request-response chains to asynchronous background processing.
- Ensuring guaranteed event delivery without dual-write inconsistency (Transactional Outbox).
- Designing event topics, partition keys for ordering, and consumer group scaling.
## What to Analyze
1. **Event Schema Design**: Standard envelopes (CloudEvents spec), event types, versioning, and payloads.
2. **Publishing Reliability**: Transactional Outbox pattern with Debezium or polling to prevent lost events if broker is down.