Event driven architecture
Skill kimtth/agent-skill-100-lines-or-less/skills/event-driven-architecture
Use when: design systems around events and messages with reliable, decoupled processing.From its SKILL.md
npx -y skills add kimtth/agent-skill-100-lines-or-less --skill event-driven-architectureAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.1 KB, 211 tokens by cl100k_base, as published. Nobody here has run it
Goal: decoupled components that react to events reliably.
Use for:
- decoupling producers from consumers
- async workflows, integrations, and fan-out
- designing topics, queues, and event schemas
Workflow:
- Define events as facts about what happened, named in past tense.
- Version event schemas; keep them backward compatible.
- Choose delivery semantics: at-least-once is the common default.
- Make consumers idempotent to tolerate redelivery.
- Handle failures with retries and a dead-letter queue.
- Verify ordering and replay behavior under load.
Patterns:
- publish/subscribe for fan-out
- outbox pattern for atomic write-and-publish
- idempotency keys to dedupe processing
- dead-letter queues for poison messages
Rules:
- assume at-least-once delivery; design idempotent consumers
- events are immutable facts, not commands
- evolve schemas additively; never break consumers
- never lose a failed message silently; dead-letter it
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.