event-store-design

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

Install with Tessl CLI

npx tessl i github:Dicklesworthstone/pi_agent_rust --skill event-store-design

What are skills?

1.15x

Quality

70%

Does it follow best practices?

Impact

99%

1.15x

Average score across 3 eval scenarios

Optimize this skill with Tessl

npx tessl skill review --optimize ./tests/ext_conformance/artifacts/agents-wshobson/backend-development/skills/event-store-design/SKILL.md

SKILL.md

Review

Evals

Evaluation results

100%

17%

Payment Processing Event Store: Database Schema

PostgreSQL event store schema

Criteria

Without context

With context

Events table exists

100%

UUID primary key with gen_random_uuid()

50%

100%

stream_type column

100%

event_data as JSONB

62%

100%

metadata as JSONB with default

100%

global_position as BIGSERIAL

87%

100%

Unique stream version constraint

100%

Stream query index

100%

Global position index

87%

100%

Snapshots table

70%

100%

Subscription checkpoints table

100%

Stream ID naming guidance

44%

100%

Without context: $0.4488 · 2m 19s · 16 turns · 16 in / 8,029 out tokens

With context: $0.3808 · 1m 29s · 16 turns · 293 in / 4,016 out tokens

99%

Logistics Fleet Tracker: Python Event Store Client

Python asyncpg event store client

Criteria

Without context

With context

Uses asyncpg

100%

Transaction wrapping

100%

Optimistic concurrency check

100%

Event ID for idempotency

100%

Correlation/causation IDs in metadata

12%

87%

Stream ID with aggregate type

87%

100%

Subscription checkpoint persistence

100%

Checkpoint upsert pattern

100%

Backpressure / poll interval

100%

read_stream ordered by version

100%

read_all ordered by global_position

100%

No update/delete of events

100%

Without context: $0.3680 · 1m 54s · 12 turns · 12 in / 7,178 out tokens

With context: $0.5971 · 2m 22s · 25 turns · 87 in / 7,629 out tokens

100%

10%

Streaming Content Platform: Event Store Implementation

EventStoreDB client and technology selection

Criteria

Without context

With context

Uses esdbclient package

100%

StreamState.ANY for unconditional append

100%

StreamState.NO_STREAM for new streams

100%

Category projection stream naming

100%

current_version parameter used

100%

NewEvent for constructing events

100%

Data encoded as bytes

100%

Technology selection rationale

100%

Subscription or read implementation

100%

No update or delete of events

100%

Stream ID includes aggregate type

100%

Without context: $0.4351 · 2m 32s · 15 turns · 16 in / 7,654 out tokens

With context: $0.4497 · 2m 3s · 16 turns · 310 in / 6,145 out tokens

Evaluated: 8 days ago
Agent: Claude Code
Model: Claude Sonnet 4.6

Table of Contents

Payment Processing Event Store: Database Schema Logistics Fleet Tracker: Python Event Store Client Streaming Content Platform: Event Store Implementation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.