Event Driven Systems
Use for event-driven or message-driven architecture, commands and events, queues, pub/sub, Kafka, choreography, orchestration, sagas, outbox, idempotency, retries, ordering, backpressure, consumer lag, and messaging operations.
Install
/plugin marketplace add eralmansouri/skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add eralmansouri/skills --skill event-driven-systemsgit clone --depth 1 https://github.com/eralmansouri/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/skills/event-driven-systems ~/.claude/skills/event-driven-systemsPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Event-Driven Systems Use messaging to solve explicit workflow, temporal-decoupling, buffering, or integration needs. It changes coupling rather than removing it and introduces delivery, consistency, failure, and operational responsibilities. ## Design Workflow 1. Establish capability boundaries and ownership before choosing messages or transport. 2. Map business intent, facts, handoffs, decisions, deadlines, and failure outcomes. 3. Use synchronous request-response for an immediate answer, a command for directed intent, and an event for an independently consumable fact. 4. Decide whether temporal decoupling is valuable enough to change completed into accepted for later processing. 5. Use choreography while the workflow remains understandable; use orchestration or a stateful policy when progress and compensation must be explicit. 6. Define delivery, duplicate, ordering, timeout, retry, dead-letter, and reconciliation behavior. 7. Choose queue, pub/sub, or retained log by semantics rather than product preference. 8. Design external messages as stable APIs and keep internal events private by default. 9. Design tracing, lag monitoring, outbox operations, dead-letter replay, and capacity before rollout. 10. Choose deployment topology last; messaging does not require microservices. ## Message Semantics - Command: imperative intent directed to one logical owning consumer. - Event: past-tense fact, one logical publisher, zero or more consumers.
Details
- Skill name
event-driven-systems- Repository
- eralmansouri/skills
- Path
skills/event-driven-systems/SKILL.md- Repo updated
- 15 October 2026
FAQ
What does the Event Driven Systems skill do?
Use for event-driven or message-driven architecture, commands and events, queues, pub/sub, Kafka, choreography, orchestration, sagas, outbox, idempotency, retries, ordering, backpressure, consumer lag, and messaging operations.
How do I install the Event Driven Systems skill?
Claude Code plugin: /plugin marketplace add eralmansouri/skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Event Driven Systems popular?
It lives in eralmansouri/skills, which has 9 GitHub stars and 2 forks.
Related skills
Codebase Design
9eralmansouri/skills
Use for code-level module design, deep modules, interfaces, seams, adapters, testability, refactoring shallow modules, and finding architecture improvements in an existing codebase.
Design Review
9eralmansouri/skills
Design review of a codebase area, branch, or PR. Maps its bounded contexts, vertical slices, and modules, then judges where rules live and whether flexibility sits where change actually happens. Use when the user asks for a design or architecture review, or when a review should judge structure rather than bugs or style.
Domain Driven Design
9eralmansouri/skills
Use for domain-driven design, domain modeling, ubiquitous language, bounded contexts, aggregates, invariants, entities, value objects, domain services, domain events, and deciding whether a rich domain model is warranted.
Khaow Friend Roleplay
513D4C/kewmajiroon8888
Roleplay as a friend named "khaow" — a quirky programmer who solves problems in weird, roundabout ways but is extremely confident in his own ideas. Use this skill whenever the user mentions their friend khaow, asks to roleplay as khaow, wants to talk to khaow, or asks "how would khaow do this?" / "what would khaow build?" — even if the word "roleplay" isn't used directly.
Duvo CLI
9duvoai/skills
Drive the Duvo public API from the terminal via the `duvo` CLI (`@duvoai/cli`). Use when the user wants to script Duvo — managing automations, Policy, agents, runs, cases, queues, files, skills, connections, Clarity processes, Pulse dashboards, or hitting an arbitrary endpoint via `duvo api` — instead of clicking through the Duvo web UI or hand-crafting `curl` calls.
Run Debugger
9duvoai/skills
Investigate why a Duvo Run failed or produced the wrong outcome. Use when the user shares a failed Run, asks "why did this Run fail", or wants to fix a recurring failure on an Agent. Reads the Run's transcript and the Build that was active for it via the Duvo public API, names the root cause from a fixed failure-mode taxonomy, and proposes one concrete fix — handing off to aop-writer for any AOP rewrite.
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.