Agent skill

Event Store Design

Designs event stores for event-sourced systems: requirements, a comparison of EventStoreDB, PostgreSQL, Kafka, DynamoDB and Marten, and stream and versioning practices.

MITAuto-check passedBackend & APIs

Install Event Store Design

skills CLI

$ npx skills add wshobson/agents --skill event-store-design -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install wshobson/agents event-store-design --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/wshobson/agents.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/backend-development/skills/event-store-design .claude/skills/event-store-design && rm -rf skills-src

Use ~/.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/

Paste into Claude Code

Install the "event-store-design" agent skill from https://github.com/wshobson/agents/tree/main/plugins/backend-development/skills/event-store-design into .claude/skills/event-store-design/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "event-store-design", 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

$skill-installer install https://github.com/wshobson/agents/tree/main/plugins/backend-development/skills/event-store-design

Type 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.

skills CLI

$ npx skills add wshobson/agents --skill event-store-design -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install wshobson/agents event-store-design --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/wshobson/agents.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/backend-development/skills/event-store-design .agents/skills/event-store-design && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "event-store-design" agent skill from https://github.com/wshobson/agents/tree/main/plugins/backend-development/skills/event-store-design into .agents/skills/event-store-design/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "event-store-design", 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.

skills CLI

$ npx skills add wshobson/agents --skill event-store-design -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install wshobson/agents event-store-design --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/wshobson/agents.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/backend-development/skills/event-store-design .cursor/skills/event-store-design && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "event-store-design" agent skill from https://github.com/wshobson/agents/tree/main/plugins/backend-development/skills/event-store-design into .cursor/skills/event-store-design/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "event-store-design", 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

$ gemini skills install https://github.com/wshobson/agents.git --path plugins/backend-development/skills/event-store-design

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add wshobson/agents --skill event-store-design -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install wshobson/agents event-store-design --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/wshobson/agents.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/backend-development/skills/event-store-design .gemini/skills/event-store-design && rm -rf skills-src

Use ~/.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/

Paste into Gemini CLI

Install the "event-store-design" agent skill from https://github.com/wshobson/agents/tree/main/plugins/backend-development/skills/event-store-design into .gemini/skills/event-store-design/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "event-store-design", 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.

GitHub CLI

$ gh skill install wshobson/agents event-store-design

Installs 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).

skills CLI

$ npx skills add wshobson/agents --skill event-store-design -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/wshobson/agents.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/backend-development/skills/event-store-design .github/skills/event-store-design && rm -rf skills-src

Use ~/.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/

Paste into GitHub Copilot

Install the "event-store-design" agent skill from https://github.com/wshobson/agents/tree/main/plugins/backend-development/skills/event-store-design into .github/skills/event-store-design/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "event-store-design", 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.

skills CLI

$ npx skills add wshobson/agents --skill event-store-design -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install wshobson/agents event-store-design --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/wshobson/agents.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/backend-development/skills/event-store-design .opencode/skills/event-store-design && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "event-store-design" agent skill from https://github.com/wshobson/agents/tree/main/plugins/backend-development/skills/event-store-design into .opencode/skills/event-store-design/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "event-store-design", 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-store-design
GitHub stars: 40k
Used in: 9 other repos
Token cost: ~828 tokens
SKILL.md length: 207 words
Files: 2 (incl. references)
Skills in repo: 142
Repo updated: Oct 5, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Designs event stores for event-sourced systems: requirements, a comparison of EventStoreDB, PostgreSQL, Kafka, DynamoDB and Marten, and stream and versioning practices.

Works in 2 steps: Event Store Architecture → Event Store Requirements
Designing event sourcing infrastructure for a new service
SKILL.md covers When to Use This Skill, Core Concepts, Technology Comparison and Templates and detailed worked…, plus 1 more section
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

The skill sets out what an event store must do: append-only writes, per-stream and global ordering, versioning for optimistic concurrency, real-time subscriptions and idempotent handling of duplicate writes. A technology table compares EventStoreDB, PostgreSQL, Kafka, DynamoDB and Marten, noting what each suits and where it falls short.

Practical advice includes stream IDs that carry the aggregate type, correlation and causation IDs for tracing, event versioning from the start, deduplication by event ID and indexes matched to query patterns. It warns against updating or deleting events, storing large payloads, skipping optimistic concurrency and ignoring backpressure from slow consumers. Schemas and worked examples are in `references/details.md`.

When your agent uses it

Designing event sourcing infrastructure for a new service
Choosing between EventStoreDB, PostgreSQL, Kafka and DynamoDB for events
Implementing a custom event store schema
Planning how an event store will scale

Example prompts

“Design a PostgreSQL event store schema with stream IDs, versions and optimistic concurrency.”
“Which event store technology fits a serverless, AWS-native system, and what are its limits?”
“Add correlation and causation IDs to our event envelope for tracing.”

Workflow steps

2 steps, taken from the step headings in SKILL.md.

Event Store Architecture
Event Store Requirements

What it can do on your machine

Read from SKILL.md and the folder at commit 46891e7. 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
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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 Store Design loads about 828 tokens when it runs, and up to ~3.7k if it reads all its reference files. Until then it costs about 52 tokens; SKILL.md has 207 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~52
When it runs · the whole SKILL.md, loaded when a task matches: ~828
With references · SKILL.md plus every file in references/, read only if the agent opens them: ~3.7k

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 wshobson/agents at commit 46891e7, republished under its MIT licence (© wshobson). 207 words, ~828 tokens.

Download SKILL.mdSave it as .claude/skills/event-store-design/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.

name: event-store-design
description: Design and implement event stores for event-sourced systems. Use when building event sourcing infrastructure, choosing event store technologies, or implementing event persistence patterns.

Event Store Design

Comprehensive guide to designing event stores for event-sourced applications.

When to Use This Skill

Designing event sourcing infrastructure
Choosing between event store technologies
Implementing custom event stores
Optimizing event storage and retrieval
Setting up event store schemas
Planning for event store scaling

Core Concepts

1. Event Store Architecture

┌─────────────────────────────────────────────────────┐
│                    Event Store                       │
├─────────────────────────────────────────────────────┤
│  ┌─────────────┐  ┌─────────────┐  ┌─────────────┐ │
│  │   Stream 1   │  │   Stream 2   │  │   Stream 3   │ │
│  │ (Aggregate)  │  │ (Aggregate)  │  │ (Aggregate)  │ │
│  ├─────────────┤  ├─────────────┤  ├─────────────┤ │
│  │ Event 1     │  │ Event 1     │  │ Event 1     │ │
│  │ Event 2     │  │ Event 2     │  │ Event 2     │ │
│  │ Event 3     │  │ ...         │  │ Event 3     │ │
│  │ ...         │  │             │  │ Event 4     │ │
│  └─────────────┘  └─────────────┘  └─────────────┘ │
├─────────────────────────────────────────────────────┤
│  Global Position: 1 → 2 → 3 → 4 → 5 → 6 → ...     │
└─────────────────────────────────────────────────────┘

2. Event Store Requirements

Requirement	Description
Append-only	Events are immutable, only appends
Ordered	Per-stream and global ordering
Versioned	Optimistic concurrency control
Subscriptions	Real-time event notifications
Idempotent	Handle duplicate writes safely

Technology Comparison

Technology	Best For	Limitations
EventStoreDB	Pure event sourcing	Single-purpose
PostgreSQL	Existing Postgres stack	Manual implementation
Kafka	High-throughput streaming	Not ideal for per-stream queries
DynamoDB	Serverless, AWS-native	Query limitations
Marten	.NET ecosystems	.NET specific

Templates and detailed worked examples

Full template library and detailed worked examples live in references/details.md. Read that file when you need the concrete templates.

Best Practices

Do's

Use stream IDs that include aggregate type - Order-{uuid}
Include correlation/causation IDs - For tracing
Version events from day one - Plan for schema evolution
Implement idempotency - Use event IDs for deduplication
Index appropriately - For your query patterns

Don'ts

Don't update or delete events - They're immutable facts
Don't store large payloads - Keep events small
Don't skip optimistic concurrency - Prevents data corruption
Don't ignore backpressure - Handle slow consumers

Files

SKILL.md and 1 other file (references) in plugins/backend-development/skills/event-store-design of wshobson/agents.

SKILL.md
references/details.md

Open the folder on GitHubat commit 46891e7

Used in 9 other repositories

We found 23 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 9 other GitHub owners. This page covers the copy in wshobson/agents, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Event Store Design 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.

Event Store Design compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Event Store Design this skillwshobson/agents	40k	9 repos	~828	Automated safety check: Pass	MIT	5 days ago
New Event Sourceaws/aws-lambda-dotnet	1.7k	—	~3k	Automated safety check: Pass	Apache-2.0	today
Create Environmentgodatadriven/whirl	205	—	~1.9k	Automated safety check: Pass	Apache-2.0	8 days ago
Windmill Trigger Type Checklistwindmill-labs/windmill	18k	—	~4.7k	Automated safety check: Pass	Custom licence	today
FoundatioFoundatioFx/Foundatio	2.1k	—	~3.9k	Automated safety check: Pass	Apache-2.0	yesterday
Monstermq Broker Configvogler75/monster-mq	143	—	~2.2k	Automated safety check: Pass	GPL-3.0	today

Similar skills

New Event Source
aws/aws-lambda-dotnet
Official
Add a new AWS event source attribute (e.g., Kinesis, Kafka, MQ) to the Lambda .NET Annotations framework, including the attribute class, source generator integration, CloudFormation writer, unit…
1.7k GitHub stars~3k tokensUpdated today
Testing & QAAuto-check passed
Create Environment
godatadriven/whirl
Create a new Whirl environment in the envs/ directory. An agent skill from godatadriven/whirl.
205 GitHub stars~1.9k tokensUpdated 8 days ago
Backend & APIsAuto-check passed
Windmill Trigger Type Checklist
windmill-labs/windmill
Checklist of every backend, frontend, CLI and capture change needed to add a new TriggerCrud-based trigger type, such as Azure, GCP or Kafka, to Windmill.
18k GitHub stars~4.7k tokensUpdated today
Backend & APIsAuto-check passed
Foundatio
FoundatioFx/Foundatio
A skill your agent uses when working with Foundatio infrastructure abstractions for .NET -- caching, queuing, messaging, file storage, distributed locking, or background jobs.
2.1k GitHub stars~3.9k tokensUpdated yesterday
Backend & APIsAuto-check passed
Monstermq Broker Config
vogler75/monster-mq
Guide for configuring, deploying, and operating the MonsterMQ broker.
143 GitHub stars~2.2k tokensUpdated today
DevOps & CloudAuto-check passed
Flox Environments
affaan-m/ECC
Create reproducible, cross-platform (macOS/Linux) development environments with Flox, a declarative Nix-based environment manager.
276k GitHub starsUsed in 1 repo~3.5k tokens
DatabasesAuto-check: notes

Questions about Event Store Design

What does Event Store Design do?

Designs event stores for event-sourced systems: requirements, a comparison of EventStoreDB, PostgreSQL, Kafka, DynamoDB and Marten, and stream and versioning practices. The skill sets out what an event store must do: append-only writes, per-stream and global ordering, versioning for optimistic concurrency, real-time subscriptions and idempotent handling of duplicate writes. A technology table compares EventStoreDB, PostgreSQL, Kafka, DynamoDB and Marten, noting what each suits and where it falls short.

When should I use Event Store Design?

Event Store Design fits situations like: designing event sourcing infrastructure for a new service; choosing between EventStoreDB, PostgreSQL, Kafka and DynamoDB for events; implementing a custom event store schema; planning how an event store will scale.

How do I install Event Store Design in Claude Code?

Run `npx skills add wshobson/agents --skill event-store-design -a claude-code`. Or copy the skill folder (plugins/backend-development/skills/event-store-design in wshobson/agents) into .claude/skills/event-store-design in your project. Claude Code loads it when a task matches its description.

How do I install Event Store Design in Codex?

Run `npx skills add wshobson/agents --skill event-store-design -a codex`. Or copy the skill folder (plugins/backend-development/skills/event-store-design in wshobson/agents) into .agents/skills/event-store-design in your project. Codex loads it when a task matches its description.

Can I use Event Store Design 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 wshobson/agents --skill event-store-design -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-store-design, .gemini/skills/event-store-design, .github/skills/event-store-design and .opencode/skills/event-store-design in your project.

What does Event Store Design need to run?

SKILL.md names no scripts, command-line tools or credentials: Event Store Design is instructions for the agent only.

Does Event Store Design access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Event Store Design 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 Store Design use?

Event Store Design 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 Store Design use?

About 828 tokens (SKILL.md is roughly 3.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.9k tokens, read only when the agent opens those files.

What are the alternatives to Event Store Design?

Skills that share tags, products or a category with Event Store Design: New Event Source (aws/aws-lambda-dotnet, 1.7k stars), Create Environment (godatadriven/whirl, 205 stars), Windmill Trigger Type Checklist (windmill-labs/windmill, 18k stars) and Foundatio (FoundatioFx/Foundatio, 2.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Event Store Design?

wshobson (a GitHub user) maintains it in wshobson/agents, which has 40,314 GitHub stars. The repository holds 142 skills in this directory. The repository was last updated on October 5, 2026.

Source: wshobson/agents on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Event Store Design

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Event Store Design

When to Use This Skill

Core Concepts

1. Event Store Architecture

2. Event Store Requirements

Technology Comparison

Templates and detailed worked examples

Best Practices

Do's

Don'ts

Files

Used in 9 other repositories

Compare with similar skills

Similar skills

More from wshobson/agents

Related

Questions about Event Store Design