Skills event-store-design
📦

event-store-design

Content revision r2 Medium Risk ⚙️ External commands🌐 Network access

Design Reliable Event Stores

Event-sourced systems fail when ordering, concurrency, and replay behavior are designed incompletely. This skill provides architecture guidance, technology comparisons, schemas, and implementation patterns.

Supports: Claude Codex Code(CC)
📊 69 Adequate

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/sickn33-event-store-design.md and its manifest at https://skillstore.io/api/skills/sickn33-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/sickn33-event-store-design.md Signed manifest GET /api/skills/sickn33-event-store-design/manifest Signed lockfile GET /api/skills/sickn33-event-store-design/lockfile

Test it

Using "event-store-design". Choose storage for an order service using PostgreSQL with moderate traffic.

Expected outcome:

  • Recommendation: use PostgreSQL with one ordered stream per order and a global sequence for subscriptions.
  • Enforce a unique stream and version constraint, then handle conflicts as optimistic concurrency failures.
  • Store correlation identifiers in metadata and checkpoint each projection independently.

Using "event-store-design". Review a projection consumer that may receive duplicate events.

Expected outcome:

  • Primary risk: repeated delivery can apply the same state change more than once.
  • Record processed event identifiers or make every projection update naturally idempotent.
  • Advance the checkpoint only after the projection transaction succeeds.

Using "event-store-design". Plan snapshots for long-lived account streams.

Expected outcome:

Create snapshots after a measured event threshold, retain their source version, and verify state by replaying events after that version.

Security Audit

Medium Risk
v5 • 7/24/2026 Open versioned report

All 31 static findings are false positives caused by Markdown formatting, database method names, schema identifiers, and documentation links. Two implementation examples contain real security-relevant weaknesses: disabled transport security and a DynamoDB write path that does not enforce its claimed concurrency condition.

2
Files scanned
484
Lines analyzed
0
Review items
0
False positives ignored

Confirmed security concerns (2)

Medium
SKILL.md:311
Transport Security Disabled in EventStoreDB Example
The example connection URI explicitly disables TLS. Reusing this configuration beyond isolated local development could expose event data and credentials in transit.
The URI explicitly contains tls=false, so transport encryption is disabled. The localhost host reduces immediate exposure but does not make the template safe for deployment.
Medium
SKILL.md:385-403
DynamoDB Example Does Not Enforce Optimistic Concurrency
The append method claims conditional concurrency but uses batch put operations without conditions. Duplicate keys can replace historical events and violate append-only integrity.
The method derives versions locally and calls batch.put_item without a condition or transaction. DynamoDB put operations replace items with matching keys.

Risk Factors

⚙️ External commands (11)
SKILL.md:23 SKILL.md:38-54 SKILL.md:54-80 SKILL.md:80-123 SKILL.md:123-127 SKILL.md:127-302 SKILL.md:302-306 SKILL.md:306-369 SKILL.md:369-373 SKILL.md:373-429 SKILL.md:429-435
🌐 Network access (5)
SKILL.md:212 SKILL.md:232 SKILL.md:450 SKILL.md:451 SKILL.md:452
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
Security Assessment

Copy report link

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

Markdown badge

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

HTML badge

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

Embed card

<iframe src="https://skillstore.io/embed/skills/sickn33-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

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

BibTeX citation

@techreport{sickn33-sickn33-event-store-design-2026, author = {sickn33}, title = {event-store-design security audit report (audit version 5)}, institution = {Skillstore}, year = {2026}, number = {5}, url = {https://skillstore.io/skills/sickn33-event-store-design/audits/5}, 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 5)" version: "unspecified" type: report authors: - name: "sickn33" date-released: "2026-07-24" url: "https://skillstore.io/skills/sickn33-event-store-design/audits/5" identifiers: - type: other value: "skillstore:sickn33-event-store-design:audit:5" 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
wshobson Recommended

wshobson-event-store-design

Skillstore Score 78
Evidence Confidence High
Skillstore usage 12
Updated

2026-09-09

sickn33 Current

sickn33-event-store-design

Skillstore Score 69
Evidence Confidence High
Skillstore usage 10
Updated

2026-09-09

Skillstore Score

Why this score Evidence Confidence: High
55
Architecture
85
Maintainability
87
Content
69
Community
83
Spec Compliance

What You Can Build

Plan a New Event Store

Compare storage technologies and define ordering, concurrency, subscription, and retention requirements before implementation.

Implement PostgreSQL Persistence

Create an event schema and service design for teams that already operate PostgreSQL.

Review Replay and Scaling Safety

Assess checkpoints, idempotency, snapshots, projections, and indexes before increasing event volume.

Try These Prompts

Define Basic Requirements 
Design an event store for [application]. Ask about event volume, ordering, consistency, retention, replay, and operational constraints before recommending an approach.
Compare Storage Technologies 
Compare PostgreSQL, EventStoreDB, Kafka, and DynamoDB for [workload]. Evaluate stream reads, global ordering, subscriptions, operations, cost, and scaling.
Design a Production Schema 
Design a production event-store schema for [domain] using [database]. Include concurrency, idempotency, metadata, indexes, checkpoints, snapshots, retention, and migration strategy.
Audit an Existing Event Store 
Review this event-store design: [design]. Identify integrity, concurrency, replay, projection, security, recovery, and scaling risks. Prioritize fixes and define verification tests.

Best Practices

  • State ordering, consistency, replay, retention, and throughput requirements before selecting technology.
  • Protect event integrity with immutable records, atomic version checks, idempotent writes, and tested recovery procedures.
  • Validate every example against current libraries, production security controls, and realistic load tests.

Avoid

  • Do not modify or delete historical events to correct domain state.
  • Do not advance consumer checkpoints before handlers and projection writes succeed.
  • Do not treat sample connection settings or storage code as production-ready configuration.

Frequently Asked Questions

Does this skill choose a database automatically?
No. It compares common options and uses your workload, operations, consistency, and query requirements to guide selection.
Can it design a PostgreSQL event store?
Yes. It covers event tables, stream versions, global positions, snapshots, indexes, and subscription checkpoints.
Does it support EventStoreDB and DynamoDB?
Yes. It includes conceptual guidance and Python examples, but those examples require security and production hardening.
How does it address concurrent writes?
It recommends expected stream versions and optimistic concurrency. Your implementation must enforce version checks atomically in the chosen database.
Does it cover event schema evolution?
It recommends event versioning and explicit upcasting or downcasting policies. It does not provide a complete migration framework.
Is the generated design ready for production?
No. Validate authentication, encryption, authorization, observability, recovery, performance, and vendor-specific behavior before deployment.

Developer Details

Author

sickn33

License

MIT

Skillstore revision

r2

Version notice

The author did not declare a version.

Repository

https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/event-store-design

Ref

88a8e9a07f4c54ab105c1c41b6267c287146b07b

Maintenance freshness

7/26/2026

Usage

7 downloads · 138 views

File structure

📁 resources/

📄 implementation-playbook.md

📄 SKILL.md

More from sickn33

View all

Related Skills

View all