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-design80
Quality
70%
Does it follow best practices?
Impact
99%
1.15xAverage 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.mdDiscovery
75%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 description with good completeness and distinctiveness. It clearly identifies when to use the skill and targets a specific architectural domain. However, it could benefit from more concrete action verbs and additional trigger terms that users commonly associate with event sourcing patterns.
Suggestions
Add more specific concrete actions like 'store domain events', 'replay event streams', 'implement snapshots', 'query event history'
Include additional trigger terms users might naturally say: 'CQRS', 'event stream', 'EventStoreDB', 'append-only', 'aggregate events', 'event replay'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (event stores, event-sourced systems) and mentions some actions (design, implement, choosing technologies), but lacks specific concrete actions like 'store events', 'replay event streams', 'snapshot aggregates', or 'query event history'. | 2 / 3 |
Completeness | Clearly answers both what ('Design and implement event stores for event-sourced systems') and when ('Use when building event sourcing infrastructure, choosing event store technologies, or implementing event persistence patterns') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes relevant terms like 'event sourcing', 'event store', 'event persistence' but misses common variations users might say such as 'CQRS', 'event log', 'event stream', 'EventStoreDB', 'append-only log', or 'aggregate events'. | 2 / 3 |
Distinctiveness Conflict Risk | Event sourcing is a specific architectural pattern with distinct terminology. The description clearly targets this niche and is unlikely to conflict with general database, messaging, or other persistence skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides excellent actionable code templates for multiple event store implementations, making it highly practical for implementation. However, it's verbose with explanatory content Claude doesn't need, lacks explicit setup/validation workflows, and could benefit from better progressive disclosure by splitting templates into separate reference files.
Suggestions
Remove the 'When to Use This Skill' and 'Core Concepts' sections - Claude understands event sourcing fundamentals
Add an explicit workflow section showing the sequence: create schema → validate → test append → verify read → set up subscriptions
Split the four technology templates into separate files (e.g., POSTGRES.md, EVENTSTOREDB.md, DYNAMODB.md) with SKILL.md as a concise overview
Add validation commands or checks after schema creation (e.g., 'Verify table exists: SELECT * FROM events LIMIT 1;')
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary explanatory content (e.g., 'When to Use This Skill' section, 'Core Concepts' architecture diagram) that Claude already understands. The templates are valuable but could be more condensed. | 2 / 3 |
Actionability | Provides fully executable code templates for PostgreSQL, Python, EventStoreDB, and DynamoDB implementations. The SQL schemas and Python classes are copy-paste ready with complete implementations. | 3 / 3 |
Workflow Clarity | While the code templates show individual operations clearly, there's no explicit workflow for setting up an event store end-to-end. Missing validation steps for schema deployment and no error recovery guidance for failed appends beyond the ConcurrencyError. | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but it's a monolithic document with ~300 lines that could benefit from splitting templates into separate files. External resources are listed but internal cross-references are absent. | 2 / 3 |
Total | 9 / 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.
- 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.