Install any skill in seconds. Free to start, no credit card required.
Get Started Free →dokhacgiakhoa/event-store-design
Design and implement event stores for event-sourced systems.
Passed 17 of 25 test cases with the skill, and 16 of 25 without it.
1 fixed16 passed either way8 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
A test case the skill fixed. Same model, same prompt, with and without the skill.
Our system takes a snapshot of aggregate state after every single event append to ensure hydration is fast. However, database write IOPS and storage costs are skyrocketing. Evaluate this snapshotting strategy and provide a balanced configuration strategy.
| Checked | Without skill | With skill |
|---|---|---|
| Explaining that taking snapshots after every single event creates excessive storage bloat and IOPS overhead. | Passed | Passed |
| Recommending a configurable event count threshold between aggregate snapshots. | Passed | Passed |
| Demonstrating code logic to trigger snapshot persistence when stream version reaches threshold multiples. | Missed | Passed |
The instructions your model reads when the skill loads.
Comprehensive guide to designing event stores for event-sourced applications.
resources/implementation-playbook.md.test cases passed, vs 16 / 25 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.