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.
82
59%
Does it follow best practices?
Impact
97%
1.15xAverage score across 6 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/backend-development/skills/event-store-design/SKILL.mdQuality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a solid skill description that clearly identifies its niche in event sourcing infrastructure, includes an explicit 'Use when' clause with relevant triggers, and is distinctive enough to avoid conflicts with other skills. The main weakness is that the capability actions could be more granular—listing specific operations like stream management, snapshots, projections, or concurrency handling would strengthen specificity.
Suggestions
Add more concrete actions such as 'append events to streams, read event streams, implement snapshots, build projections, handle concurrency' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (event sourcing) and some actions ('design and implement event stores', 'choosing event store technologies', 'implementing event persistence patterns'), but the actions are somewhat high-level and not as concrete as listing specific operations like 'append events, read streams, handle snapshots, implement projections'. | 2 / 3 |
Completeness | Clearly answers both 'what' (design and implement event stores for event-sourced systems) and 'when' (explicit 'Use when' clause covering building event sourcing infrastructure, choosing technologies, or implementing persistence patterns). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'event store', 'event-sourced', 'event sourcing', 'event persistence', 'event store technologies'. These are the terms a developer working in this domain would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Event sourcing and event stores are a very specific architectural niche. The description is clearly distinguishable from general database skills, messaging skills, or CQRS skills, with distinct trigger terms unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
29%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides high-quality, executable code templates across multiple event store technologies, which is its primary strength. However, it is excessively verbose, lacks any workflow sequencing or validation steps for what is a complex infrastructure task, and dumps all content into a single monolithic file rather than using progressive disclosure. The content reads more like a reference manual than an actionable skill guide.
Suggestions
Add a clear step-by-step workflow for designing and implementing an event store (e.g., 1. Choose technology, 2. Create schema, 3. Validate schema, 4. Implement store class, 5. Test with sample events) with explicit validation checkpoints.
Move technology-specific templates into separate referenced files (e.g., POSTGRES_EVENT_STORE.md, DYNAMODB_EVENT_STORE.md) and keep only one primary template inline with links to alternatives.
Remove the 'Core Concepts' section (ASCII diagram, requirements table) and technology comparison table - Claude already understands event sourcing fundamentals. Replace with a brief decision guide.
Add validation/verification steps such as testing the schema creation, verifying event append/read round-trips, and checking concurrency handling works correctly.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~350+ lines. It includes extensive ASCII diagrams, requirement tables, and technology comparison tables that explain concepts Claude already knows. The 'When to Use This Skill' and 'Core Concepts' sections add little actionable value. Four full implementation templates across different technologies bloat the content significantly. | 1 / 3 |
Actionability | The code templates are fully executable and copy-paste ready. The PostgreSQL schema, Python EventStore class, EventStoreDB client usage, and DynamoDB implementation all contain concrete, working code with proper imports, error handling, and realistic patterns. | 3 / 3 |
Workflow Clarity | There is no clear workflow or sequenced process for designing/implementing an event store. The content presents templates and best practices but lacks any step-by-step guidance, validation checkpoints, or feedback loops. For a skill involving database schema creation and infrastructure setup, missing validation steps is a significant gap. | 1 / 3 |
Progressive Disclosure | The content is a monolithic wall of text with no references to external files. Four complete implementation templates for different technologies are all inlined, when they should be split into separate reference files. There's no overview-to-detail navigation structure. | 1 / 3 |
Total | 6 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- wshobson/agents
- Commit
70444e5
- Reviewed
Table of Contents
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.