event-sourcing-architect

Expert in event sourcing, CQRS, and event-driven architecture patterns. Masters event store design, projection building, saga orchestration, and eventual consistency patterns. Use PROACTIVELY for event-sourced systems, audit trail requirements, or complex domain modeling with temporal queries.

Quality

53%

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-sourcing-architect/SKILL.md

Quality

Content

36%Scale 1-5

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

This skill reads more like a high-level overview or checklist than actionable guidance for Claude. It lacks any concrete code examples, specific implementation patterns, or executable commands that would make it useful during actual development. The content is mostly a list of abstract principles that Claude likely already knows about event sourcing.

Suggestions

Add concrete, executable code examples showing event store implementation, command handlers, and projection building (e.g., a TypeScript or Python event store pattern with actual classes/functions)

Include specific event schema examples with versioning (e.g., JSON event envelope format, upcasting patterns)

Add validation checkpoints to the workflow, such as 'verify event schema compatibility before deploying' with specific commands or checks

Provide at least one complete worked example showing the flow from command → event → projection for a realistic domain scenario

Dimension	Reasoning	Score
Conciseness	The skill repeats the description in the header, has a 'Capabilities' section that largely restates what's in 'Use this skill when', and includes several sections that are somewhat redundant. However, it's not excessively verbose - just not tight enough.	3 / 5
Actionability	The instructions are entirely high-level and abstract ('Identify aggregate boundaries', 'Design events as immutable facts') with no concrete code examples, commands, schemas, or executable guidance. It describes what to do conceptually but never shows how.	2 / 5
Workflow Clarity	While there is a numbered sequence in the Instructions section, the steps are vaguely defined with no validation checkpoints, no concrete commands, and no feedback loops. For a skill involving complex multi-step architectural patterns, this lacks the specificity needed.	2 / 5
Progressive Disclosure	The content is organized into clear sections with headers, which provides some structure. However, there are no references to supporting files with detailed examples, code templates, or deeper documentation. For a complex topic like event sourcing, the lack of any referenced materials is a missed opportunity, though the skill is under 50 lines and reasonably organized for what it contains.	3 / 5
	Total	10 / 20 Passed

Description

70%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 covers a clear niche (event sourcing/CQRS) with good trigger terms and an explicit 'when' clause. Its main weakness is that capabilities are described as topic expertise ('Masters event store design') rather than concrete actions (e.g., 'designs event stores', 'implements projections', 'orchestrates sagas'). The use of 'Expert in' and 'Masters' is somewhat fluffy rather than action-oriented.

Suggestions

Replace 'Expert in' and 'Masters' with concrete action verbs describing what the skill does, e.g., 'Designs event stores, builds projections, orchestrates sagas, implements eventual consistency patterns'

Add more natural user trigger phrases to the 'when' clause, such as 'event replay', 'command query separation', 'event log', or 'domain events'

Dimension	Reasoning	Score
Specificity	Names the domain (event sourcing, CQRS, event-driven architecture) and lists several concepts (event store design, projection building, saga orchestration, eventual consistency patterns), but these read more as topic areas than concrete actions. It says 'Masters' rather than describing what it actually does with these patterns.	3 / 5
Completeness	Has a 'what' (event sourcing, CQRS, event store design, projection building, saga orchestration, eventual consistency) and a 'when' ('Use PROACTIVELY for event-sourced systems, audit trail requirements, or complex domain modeling with temporal queries'). The 'when' clause is explicit but could be more specific about user trigger phrases.	4 / 5
Trigger Term Quality	Includes relevant keywords like 'event sourcing', 'CQRS', 'event-driven architecture', 'event store', 'projection', 'saga', 'eventual consistency', 'audit trail', 'temporal queries', and 'domain modeling'. Missing some natural user phrases like 'event log', 'command query separation', or 'event replay'.	4 / 5
Distinctiveness Conflict Risk	The focus on event sourcing, CQRS, and saga orchestration is fairly distinctive and unlikely to overlap with general architecture or database skills. However, 'complex domain modeling' could overlap with DDD-focused skills, creating minor conflict risk.	4 / 5
	Total	15 / 20 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

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

	Total	10 / 11 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: skills/event-sourcing-architect/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.