Backend Event Driven
Use when the user asks about event-driven architecture, domain vs integration events, publishing events between services, Kafka or RabbitMQ consumers, event schema versioning, DLQs or sagas. Produces event catalog, topology and consumer code. Not for event stores (use backend-event-sourcing) or broker operations (use backend-message-queue).
Install
npx skills add j4flmao/agent-skills --skill backend-event-drivengit clone --depth 1 https://github.com/j4flmao/agent-skills.git /tmp/agent-skills
mkdir -p ~/.claude/skills
cp -r /tmp/agent-skills/skills/backend/universal/event-driven ~/.claude/skills/backend-event-drivenPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Backend Event-Driven
## Purpose
Design event-driven systems with clear event boundaries, reliable delivery, observable flows, and error recovery. Every event is a fact. Every consumer is idempotent. Every failure has a recovery path.
## Agent Protocol
### Trigger
Exact user phrases: "event-driven", "message queue", "Kafka", "RabbitMQ", "pub/sub", "domain event", "event sourcing", "CQRS", "async messaging", "event bus", "saga", "distributed transaction".
### Input Context
Before activating, verify:
- The message broker is known (Kafka, RabbitMQ, NATS, Redis, SQS/SNS) or ask.
- The service boundaries are known (which services produce events, which consume them).
- Whether events are in-process (single service) or cross-service.
### Output Artifact
No file output unless requested. Produces event design as text.
### Response Format
```
Event: {EventName}
Version: {n}
Producer: {service name}
Consumers: [{service list}]
Schema: {key fields}
Idempotency key: {eventId or business key}
```
For sagas:
```
Saga: {name}
Type: {choreography/orchestration}
Steps:
1. {service}: {action}
2. {service}: {action}
Compensation:
1. {service}: {rollback action}
2. {service}: {rollback action}
```
### Completion Criteria
- [ ] Domain vs integration event distinction is documented.
- [ ] Every event has a clear name, version, producer, and schema.
- [ ] Consumer idempotency strategy is specified for every consumer.
- [ ] Dead letter queue strategy is specified.Details
- Skill name
backend-event-driven- Repository
- j4flmao/agent-skills
- Path
skills/backend/universal/event-driven/SKILL.md- License
- MIT
- Repo updated
- 17 November 2026
FAQ
What does the Backend Event Driven skill do?
Use when the user asks about event-driven architecture, domain vs integration events, publishing events between services, Kafka or RabbitMQ consumers, event schema versioning, DLQs or sagas. Produces event catalog, topology and consumer code. Not for event stores (use backend-event-sourcing) or broker operations (use backend-message-queue).
How do I install the Backend Event Driven skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add j4flmao/agent-skills --skill backend-event-driven. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Backend Event Driven popular?
It lives in j4flmao/agent-skills, which has 45 GitHub stars and 6 forks.
Related skills
Agent Observability
45j4flmao/agent-skills
Use when the user asks about agent observability, tracing agent reasoning, debugging an agent loop, OpenTelemetry GenAI spans for LLM calls, LLM cost tracking per agent, agent audit logs or hallucination/eval monitoring in production. Produces instrumentation config, trace schema, dashboards, alerts and cost attribution. Not for generic service tracing without LLMs (use devops-opentelemetry).
AI Agent Architectures
45j4flmao/agent-skills
Use when the user asks to build an AI agent, design an agent that calls tools and keeps memory, write an agent system prompt or pick an agent framework (Claude Agent SDK, OpenAI Agents SDK, LangGraph). Produces an architecture brief covering loop, tools, memory, guardrails and evals, routing depth to child skills. Not for workflow patterns (use ai-agentic-workflows).
AI Agent Core Loop
45j4flmao/agent-skills
Use when the user asks about the agent loop, ReAct vs plan-and-solve, re-planning, Reflexion, an agent stuck in a loop, max iterations or termination conditions. Produces a loop spec or patch with state, success predicate, caps and no-progress detection. Not for overall agent design (use ai-agent-architectures) or tool schemas (use tool-calling-principles).
Backend Event Sourcing
45j4flmao/agent-skills
Use when the user asks about event sourcing, storing every change as an append-only event log, event store, rehydrating aggregates, snapshots, upcasting or projection rebuilds. Produces an event-sourced aggregate and store design. Not for CQRS without event sourcing (use backend-cqrs-patterns).
Backend Elixir
45j4flmao/agent-skills
Use when the user asks about Phoenix, Phoenix LiveView, Ecto schemas and changesets, GenServer state, OTP supervision trees, Oban jobs or Phoenix PubSub. Produces Phoenix/Elixir backend code organized by contexts. Not for Elixir language basics (use lang-elixir).
Backend Feature Flags
45j4flmao/agent-skills
Use when the user asks about server-side feature flags, kill switches, percentage rollouts, OpenFeature, LaunchDarkly, Unleash, Flagsmith or flag cleanup. Produces a flag design with ownership, defaults and evaluation code. Not for client UI flags (use frontend-feature-flags) or deploy strategies (use progressive-delivery).
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.