Name: event-store-design
Rating: 63.2 (1 reviews)
Author: administrakt0r

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

75%

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/AI-Agents-Safe-Coding-Skills-claude/skills/event-store-design/SKILL.md

The canonical home for this skill is event-store-design in administrakt0r/AI-Agents-Safe-Coding-Skills

Quality

Content

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

Highly actionable with complete, executable code templates, but undermined by a vague non-workflow in the Instructions section and poor progressive disclosure (monolithic inlining plus a broken reference).

Suggestions

Replace the generic 'Instructions' list with a concrete sequenced workflow (e.g., 1. pick technology, 2. apply schema template, 3. validate concurrency/idempotency, 4. test subscription) with explicit validation checkpoints.

Split the per-technology templates (PostgreSQL, EventStoreDB, DynamoDB) into separate files under a real 'resources/' or 'references/' directory and keep SKILL.md an overview with one-level-deep links.

Create the missing 'resources/implementation-playbook.md' referenced in the Instructions, or remove the broken reference.

Dimension	Reasoning	Score
Conciseness	Efficient, table- and code-dense content with no padding or explanation of concepts Claude already knows; minor tightening possible given the large volume of inlined templates.	4 / 5
Actionability	Fully executable, copy-paste-ready SQL schema and Python implementations for PostgreSQL, EventStoreDB, and DynamoDB covering the common cases.	5 / 5
Workflow Clarity	The 'Instructions' section is generic ('Clarify goals, constraints', 'Apply relevant best practices and validate outcomes') with no concrete sequenced steps or validation checkpoints.	2 / 5
Progressive Disclosure	Most template content that belongs in separate files is inlined into a ~450-line monolith, and the single reference to 'resources/implementation-playbook.md' points to a file that does not exist.	2 / 5
	Total	13 / 20 Passed

Description

87%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 strong, specific description that clearly states both the capability and concrete usage triggers, occupying a well-defined niche. Minor additions of synonyms could push trigger_term_quality to fully comprehensive.

Dimension	Reasoning	Score
Specificity	Names the domain and lists several concrete actions ('design and implement event stores', 'building event sourcing infrastructure', 'choosing event store technologies', 'implementing event persistence patterns'), with only minor coverage gaps.	4 / 5
Completeness	Clearly answers both 'what' (Design and implement event stores for event-sourced systems) and 'when' (explicit 'Use when building... choosing... or implementing...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Good keyword coverage of natural phrases ('event sourcing infrastructure', 'event store technologies', 'event persistence patterns'), though a few synonyms like bare 'event sourcing' or specific tech names are missing.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (event stores / event sourcing) with distinct, specific triggers and minimal overlap risk with other skills.	5 / 5
	Total	18 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills-claude/skills/event-store-design/SKILL.md
Commit: 57c135b

Reviewed: 3 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.