Skills event-store-design

📦

event-store-design

Name: event-store-design
Author: wshobson

Content revision r1 Safe ⚙️ External commands🌐 Network access

Design Event Stores for Event-Sourced Systems

Event-sourced systems need durable ordering, concurrency checks, subscriptions, and clear storage choices. This skill guides schema design, implementation patterns, and technology selection for event stores.

Supports: Claude Codex Code(CC)

🥉 78 Bronze

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request

Review the Skillstore skill "event-store-design" from https://skillstore.io/skills/wshobson-event-store-design.md and its manifest at https://skillstore.io/api/skills/wshobson-event-store-design/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/wshobson-event-store-design.md Signed manifest GET /api/skills/wshobson-event-store-design/manifest Signed lockfile GET /api/skills/wshobson-event-store-design/lockfile

Test it

Using "event-store-design". I need an event store for an order service that already uses PostgreSQL.

Expected outcome:

A recommended design with an append-only events table, stream version constraint, metadata fields, indexes, snapshots, and subscription checkpoints.

Using "event-store-design". Compare EventStoreDB and DynamoDB for serverless event sourcing.

Expected outcome:

A tradeoff summary covering native event sourcing features, operational complexity, per-stream reads, global ordering, throughput, and cloud fit.

Using "event-store-design". Review this event store for concurrency and subscription risks.

Expected outcome:

A focused review identifying expected-version checks, idempotency gaps, checkpoint behavior, polling limits, and backpressure handling.

Security Audit

Safe

v7 • 7/7/2026 Open versioned report

All static findings appear to be false positives from Markdown fences, database query examples, resource links, and event-store schema terms. No prompt injection, exfiltration intent, or malicious behavior was found in SKILL.md.

Files scanned

436

Lines analyzed

Review items

False positives ignored

Risk Factors

⚙️ External commands (10)

SKILL.md:23-39 SKILL.md:39-65 SKILL.md:65-108 SKILL.md:108-112 SKILL.md:112-287 SKILL.md:287-291 SKILL.md:291-354 SKILL.md:354-358 SKILL.md:358-414 SKILL.md:414-419

🌐 Network access (5)

SKILL.md:197 SKILL.md:217 SKILL.md:433 SKILL.md:434 SKILL.md:435

No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.

Audited by: codex View Audit History →

Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report

Copy report link

https://skillstore.io/skills/wshobson-event-store-design/audits/7?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/wshobson-event-store-design/security.svg)](https://skillstore.io/skills/wshobson-event-store-design?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/wshobson-event-store-design?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/wshobson-event-store-design/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/wshobson-event-store-design.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

Academic citations (APA · BibTeX · CFF)

APA citation

wshobson. (2026). event-store-design security audit report (audit version 7) [Author version unspecified]. Skillstore. https://skillstore.io/skills/wshobson-event-store-design/audits/7

BibTeX citation

@techreport{wshobson-wshobson-event-store-design-2026,
  author = {wshobson},
  title = {event-store-design security audit report (audit version 7)},
  institution = {Skillstore},
  year = {2026},
  number = {7},
  url = {https://skillstore.io/skills/wshobson-event-store-design/audits/7},
  note = {Author version unspecified}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "event-store-design security audit report (audit version 7)"
version: "unspecified"
type: report
authors:
  - name: "wshobson"
date-released: "2026-07-07"
url: "https://skillstore.io/skills/wshobson-event-store-design/audits/7"
identifiers:
  - type: other
    value: "skillstore:wshobson-event-store-design:audit:7"
    description: "Skillstore immutable audit report identifier"

Compare variants

2 installable variants

Each author remains a separate installable skill. The recommended variant is ranked by Skillstore evidence.

Why this variant is first

Highest Skillstore Score

Author / source Skillstore Score Evidence Confidence Skillstore usage Updated

wshobson Recommended Current

wshobson-event-store-design

Skillstore Score 78

Evidence Confidence High

Skillstore usage 12

Updated

2026-08-21

sickn33

sickn33-event-store-design

Skillstore Score 69

Evidence Confidence High

Skillstore usage 9

Updated

2026-08-21

Skillstore Score

Why this score Evidence Confidence: High

Architecture

Maintainability

Content

Community

Spec Compliance

What You Can Build

Plan a New Event Store

Select a storage technology and define core event store requirements before implementation starts.

Build PostgreSQL Persistence

Create an append-only event schema with stream ordering, indexes, snapshots, and subscription checkpoints.

Review Event Sourcing Tradeoffs

Compare operational limits, query patterns, and scaling concerns across common event store technologies.

Try These Prompts

Choose a Store

Help me choose an event store for a new event-sourced system. Compare PostgreSQL, EventStoreDB, Kafka, and DynamoDB for my expected throughput and query needs.

Draft a Schema

Design a PostgreSQL event store schema for aggregates, snapshots, and subscriptions. Include indexes, concurrency constraints, and expected read patterns.

Implement Persistence

Create an event store implementation plan for Python with async PostgreSQL access. Cover append, read stream, read all, subscriptions, checkpoints, and error handling.

Assess Production Readiness

Review my event store design for production readiness. Focus on idempotency, optimistic concurrency, schema evolution, subscriptions, snapshots, indexes, and backpressure.

Best Practices

Use immutable append-only events with unique stream version constraints.
Include correlation IDs, causation IDs, event versions, and metadata for tracing and evolution.
Design indexes and subscriptions around real read patterns before production rollout.

Avoid

Updating or deleting stored events instead of appending corrective events.
Skipping optimistic concurrency checks on aggregate streams.
Storing large payloads or unrelated read model data inside event records.

Frequently Asked Questions

Can this skill help choose between event store technologies?

Yes. It compares EventStoreDB, PostgreSQL, Kafka, DynamoDB, and Marten using practical event sourcing tradeoffs.

Does it include implementation examples?

Yes. It includes examples for PostgreSQL, EventStoreDB, and DynamoDB event store patterns.

Is the PostgreSQL schema production ready?

It is a starting template. Review indexes, retention, backups, migrations, and operational limits for your workload.

Can it design subscription processing?

Yes. It covers global reads, polling subscriptions, and checkpoint tables for tracking processed positions.

Does it cover event schema evolution?

It highlights event versioning and metadata, but detailed upcaster design still requires application-specific planning.

Can I use it with Claude, Codex, and Claude Code?

Yes. The skill is listed as compatible with Claude, Codex, and Claude Code.

Developer Details

Author

wshobson

License

MIT

Skillstore revision

Version notice

The author did not declare a version.

Repository

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

Ref

36e07d5e13068e5be64447e8f20b427cf2cbd21a

Maintenance freshness

7/18/2026

Usage

8 downloads · 235 views

File structure

📄 SKILL.md