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

70%

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 ./skills/event-store-design/SKILL.md

Quality

Content

57%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.

The content is strong on actionability with comprehensive, executable code templates and a useful technology comparison, but it is padded with generic boilerplate and lacks a concrete multi-step workflow with validation checkpoints. Progressive disclosure is weak because everything is inlined into a single large file.

Suggestions

Remove the generic "Instructions" and "Do not use this skill when" boilerplate and replace them with a concrete build/validate sequence (e.g. create schema -> append -> read back to verify -> add subscription) with explicit validation checkpoints.

Move the large code templates (PostgreSQL schema, Python EventStore, EventStoreDB, DynamoDB) into separate files under references/ and keep only concise snippets plus navigation links in SKILL.md.

Fix the executable gaps in the templates: import asyncio in the subscribe loop and use a conditional PutItem (ConditionExpression) instead of batch_writer for the DynamoDB optimistic-concurrency append.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient (no "what is event sourcing" lecture) but includes generic boilerplate ("Clarify goals, constraints, and required inputs", "Do not use this skill when") and a "Use this skill when" list that duplicates the description, fitting the mostly-efficient-but-could-be-tightened anchor.	3 / 5
Actionability	Four substantial executable templates (PostgreSQL schema, Python EventStore, EventStoreDB, DynamoDB) are largely copy-paste ready, but minor gaps (missing asyncio import, DynamoDB batch_writer not actually enforcing conditional concurrency) keep it below 5.	4 / 5
Workflow Clarity	The only sequenced guidance is the generic Instructions list with no concrete checkpoints or validation feedback loops; since event-store appends are batch/database writes, the missing validation cap holds this at 3.	3 / 5
Progressive Disclosure	Section headers give reasonable structure, but with no bundle files the ~445-line body inlines large code templates (e.g. the 170-line Python implementation) that would be better split into reference files, matching the structure-present-but-inline-content anchor.	3 / 5
	Total	13 / 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.

The description is well-formed: it explicitly answers what and when, uses third person, and targets a distinct niche. The main weakness is that the "what" portion lists only two somewhat high-level actions rather than several granular capabilities.

Dimension	Reasoning	Score
Specificity	"Design and implement event stores" names the domain plus two concrete actions (design, implement), matching the 1-2-concrete-actions anchor; it does not list several granular actions, so it stays below 4.	3 / 5
Completeness	It states a clear "what" ("Design and implement event stores for event-sourced systems") and an explicit "Use when" clause with multiple concrete triggers, satisfying both halves explicitly.	5 / 5
Trigger Term Quality	Natural terms like "event sourcing infrastructure", "event store technologies", and "event persistence patterns" give good keyword coverage a user would say, but it lacks synonyms and specific technology names, stopping short of 5.	4 / 5
Distinctiveness Conflict Risk	"Event stores for event-sourced systems" carves a clear niche with distinct triggers (event sourcing, event store technologies) and minimal overlap with other 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: rmyndharis/antigravity-skills
Path: skills/event-store-design/SKILL.md
Commit: 3eff4af

Reviewed: 1 day 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.