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.

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/backend-development/skills/event-store-design/SKILL.md

Quality

Content

61%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A clean, well-structured overview that appropriately delegates detailed templates to a single reference file. Its weakness is actionability and workflow clarity: the body lacks inline executable guidance and any explicit sequenced workflow with validation checkpoints for stateful event-store operations.

Suggestions

Add a short inline quick-start snippet (e.g. the PostgreSQL events table DDL or a minimal append example) so the body is actionable on its own without forcing a jump to references/details.md.

Include a sequenced implementation workflow with explicit validation checkpoints (e.g. 1. apply schema 2. append with expected_version 3. verify on concurrency conflict -> retry) for stateful event-store operations.

Replace abstract best-practice bullets like "Index appropriately - For your query patterns" with concrete examples tied to the query patterns listed.

Dimension	Reasoning	Score
Conciseness	The body is lean and uses tables, bullet lists, and a diagram with no padding or explanation of basic concepts; the ASCII architecture diagram is somewhat large but earns its place.	4 / 5
Actionability	Concrete artifacts like the stream-ID format (`Order-{uuid}`) and the tech comparison are present, but the executable code/schema live only in references/details.md and several bullets (e.g. "Index appropriately - For your query patterns") are abstract.	3 / 5
Workflow Clarity	No sequenced multi-step workflow with validation checkpoints is given in the body; event-store setup is a stateful/batch operation but there is no validate->fix->retry loop, capping this dimension.	3 / 5
Progressive Disclosure	The body is an overview with clear sections and a single well-signaled one-level-deep reference to references/details.md (a real bundle file), though the main body itself could be even more of a pure overview.	4 / 5
	Total	14 / 20 Passed

Description

82%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A well-structured description that clearly answers both what and when with a third-person voice and concrete trigger phrases. Minor room to expand the list of specific actions and add a few more natural synonyms.

Dimension	Reasoning	Score
Specificity	"Design and implement event stores" names the domain and two concrete actions (design, implement) plus technology choice, but is not comprehensive in listing concrete actions.	3 / 5
Completeness	It clearly states what the skill does ("Design and implement event stores for event-sourced systems") and gives an explicit "Use when..." trigger clause with concrete phrases.	5 / 5
Trigger Term Quality	"building event sourcing infrastructure, choosing event store technologies, or implementing event persistence patterns" covers several natural phrasings a user would say, though it is somewhat jargon-heavy and misses common synonyms.	4 / 5
Distinctiveness Conflict Risk	The event-store / event-sourcing niche is specific with distinct triggers, making it unlikely to fire for unrelated skills.	5 / 5
	Total	17 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: wshobson/agents
Path: plugins/backend-development/skills/event-store-design/SKILL.md
Commit: d6837ae

Reviewed: about 12 hours ago

Table of Contents

Discovery Implementation Validation

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.