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.
Overall
score
73%
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillEvaluation — 100%
↑ 1.14xAgent success when using this skill
Validation for skill structure
Discovery
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 structure that explicitly addresses both what the skill does and when to use it. The main weaknesses are moderate specificity in concrete actions and trigger terms that could benefit from additional natural variations users might employ when seeking help with event sourcing.
Suggestions
Add more specific concrete actions such as 'store and replay events', 'implement snapshots', 'query event streams', or 'handle event versioning'.
Expand trigger terms to include related concepts users might mention: 'CQRS', 'event stream', 'aggregate root', 'EventStoreDB', 'event log', or 'domain events'.
| 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 stream', 'aggregate events', 'EventStoreDB', or 'event log'. | 2 / 3 |
Distinctiveness Conflict Risk | Has a clear niche focused specifically on event sourcing and event stores, which is distinct enough to avoid conflicts with general database skills or other architecture patterns. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
65%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 developers. However, it's verbose with explanatory content Claude doesn't need, lacks clear implementation workflows with validation steps, and would benefit from splitting detailed templates into separate reference files.
Suggestions
Remove the 'When to Use This Skill' section and requirements table - Claude understands event sourcing concepts
Add an explicit implementation workflow with validation checkpoints (e.g., 'After creating schema, verify with: SELECT * FROM events LIMIT 1')
Move detailed implementation templates (PostgreSQL, DynamoDB, EventStoreDB) to separate reference files and keep only a quick-start example in the main skill
Add error handling guidance and recovery steps for common failures like concurrency conflicts
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary explanatory content (e.g., the 'When to Use This Skill' section, the ASCII diagram, and the requirements table explaining basic concepts). The code templates are valuable but the surrounding context could be tightened. | 2 / 3 |
Actionability | Provides fully executable code templates for PostgreSQL, Python, EventStoreDB, and DynamoDB implementations. The SQL schema is copy-paste ready, and the Python classes are complete with proper error handling and async patterns. | 3 / 3 |
Workflow Clarity | While individual code templates are clear, there's no explicit workflow for implementing an event store from scratch. Missing validation checkpoints for schema deployment, no guidance on testing the implementation, and no error recovery steps for common failure scenarios. | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with templates and best practices sections, but the skill is monolithic at ~300 lines. The technology comparison and multiple implementation templates could be split into separate reference files with the main skill providing a quick-start overview. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 13 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 13 / 16 Passed | |
- 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.