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

82%

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

Quality

Content

65%Weight 40%Scale 1-3

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

The content is highly actionable with four complete executable templates, but it is verbose and explains concepts Claude already knows, lacks concrete validation checkpoints in its workflow guidance, and keeps all material inline rather than progressively disclosing it across reference files. The strongest dimension is actionability; the weakest are workflow clarity and progressive disclosure.

Suggestions

Replace the generic 'Instructions' section with a concrete, sequenced design workflow that includes explicit validation checkpoints (e.g., verify schema migration, test optimistic concurrency with a duplicate write, confirm subscription checkpointing) and a validate→fix→retry feedback loop.

Move the four full code templates into separate reference files (e.g., references/postgres_template.md, references/dynamodb_template.md) and keep SKILL.md as a concise overview that links to them, improving progressive disclosure and token efficiency.

Trim the 'Core Concepts' section — the ASCII diagram and the append-only/ordered/versioned definitions restate event-sourcing basics Claude already knows; keep only what is non-obvious or skill-specific.

Dimension	Reasoning	Score
Conciseness	The body is mostly actionable templates, but the 'Core Concepts' section explains event-sourcing basics Claude already knows (append-only, ordered, versioned) and the ASCII architecture diagram is decorative padding; the ~440 lines could be tightened. Not 3 because of this redundant explanation; not 1 because the bulk is concrete, useful content.	2 / 3
Actionability	Provides four complete, executable templates — a PostgreSQL schema, an asyncpg Python implementation, an EventStoreDB client, and a DynamoDB store — all copy-paste ready. Matches the score-3 anchor; not 2 since the code is real and executable rather than pseudocode.	3 / 3
Workflow Clarity	The 'Instructions' section is generic ('Apply relevant best practices and validate outcomes') with no concrete validation checkpoints, and for database/concurrency operations the rubric caps this at 2 when feedback loops are missing. Not 3 because no explicit validate→fix→retry checkpoints exist; not 1 because the code templates do convey an append/read/subscribe sequence.	2 / 3
Progressive Disclosure	Sections are well organized, but all ~440 lines — including four full code implementations — are inline in SKILL.md with no bundle files split out, so content that should be separate remains inline. Not 3 because it far exceeds 50 lines and nothing is offloaded to references; not 1 because it is clearly sectioned rather than a monolithic wall.	2 / 3
	Total	9 / 12 Passed

Description

100%Weight 40%Scale 1-3

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 concise, specific, and complete — it clearly states both what the skill does and when to use it with natural trigger terms and a distinct niche. It uses appropriate third-person voice with no over-claims or fluff.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Design and implement event stores', 'building event sourcing infrastructure', 'choosing event store technologies', 'implementing event persistence patterns' — matching the score-3 anchor for multiple specific concrete actions.	3 / 3
Completeness	Explicitly answers both 'what' ('Design and implement event stores for event-sourced systems') and 'when' ('Use when building...'), with an explicit 'Use when' trigger clause matching the score-3 anchor exactly.	3 / 3
Trigger Term Quality	Includes natural domain terms users would actually say — 'event stores', 'event-sourced systems', 'event sourcing', 'event persistence' — giving good coverage, matching the score-3 anchor.	3 / 3
Distinctiveness Conflict Risk	Targets a clear niche (event sourcing infrastructure) with distinct triggers, making it unlikely to fire for unrelated skills; matches the score-3 anchor.	3 / 3
	Total	12 / 12 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: e63f7dd

Reviewed: 13 days 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.