CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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 for event-sourced systems, audit trails, or temporal queries.

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/event-sourcing-architect/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

50%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 body is short, well-organized, and honest about scope, but it reads as a topic checklist rather than executable guidance — no code, schemas, or conventions anywhere — and its workflow lacks the validation checkpoints the rubric requires for database/batch operations. Redundancy between the intro, Capabilities, and Best Practices wastes tokens.

Suggestions

Add concrete, executable guidance to the Instructions: e.g., an event store table schema (aggregate_id, sequence_number, event_type, payload, committed_at), a sample command handler applying events, and a specific event versioning convention (e.g., upcasters or weak-schema JSON) — the current directives are too abstract for an instruction-only skill.

Insert validation checkpoints into the workflow for the risky operations the Safety section itself flags: e.g., 'rebuild projections in staging and verify read models match expected output before promoting to production' as an explicit step, plus a verify step after event schema changes.

Remove duplication to tighten the body: drop the opening paragraph (it repeats the frontmatter description verbatim), merge Capabilities with Instructions, and consolidate the duplicate 'never delete or modify events' guidance between Safety and Best Practices.

DimensionReasoningScore

Conciseness

Mostly terse and free of teaching basics Claude already knows, but there is real redundancy: the opening paragraph repeats the description nearly verbatim, "Capabilities" re-lists the same items ("Event store design", "Projection building", "Saga and process manager orchestration", "Eventual consistency handling"), and "Events are facts - never delete or modify them" duplicates the Safety bullet. This fits anchor 3 (could be tightened) better than anchor 4 (only minor trimming needed).

3 / 5

Actionability

The Instructions are high-level design directives — "Identify aggregate boundaries and event streams", "Design events as immutable facts", "Implement command handlers and event application" — with no concrete artifacts: no event store schema, no command-handler or projection code, no naming/versioning conventions, no tool or library specifics. This matches anchor 2 (high-level hints missing the specific steps to execute) rather than anchor 3, which requires at least some concrete, executable detail.

2 / 5

Workflow Clarity

The 7-step Instructions form a coherent design sequence (boundaries → events → command handlers → projections → sagas → snapshotting → versioning), but there are no validation checkpoints anywhere in the sequence. Since event stores are database operations and projection rebuilds are batch/destructive-risk operations the Safety section itself flags, the rubric's cap applies: steps listed with validation gaps, i.e. anchor 3, despite the otherwise logical ordering.

3 / 5

Progressive Disclosure

The body is ~50 lines with no bundle files and no external references, organized into clear, well-labeled sections (Capabilities, Use/Do-not-use, Instructions, Safety, Best Practices). Per the rubric's simple-skill exception, a short skill with no need for external references scores 5 on well-organized sections alone; it is not a monolithic wall of text nor does it bury any references.

5 / 5

Total

13

/

20

Passed

Description

83%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 description in third-person voice that clearly states capabilities and includes an explicit "Use for" trigger clause with concrete terms. It is specific and complete, with only minor gaps: a few missing natural trigger variations and slightly broad terms like "audit trails" that create small overlap risk.

DimensionReasoningScore

Specificity

Lists several concrete capability areas — "event store design, projection building, saga orchestration, and eventual consistency patterns" — comparable to the anchor-4 example of several specific actions with minor gaps (e.g., event versioning and snapshotting are absent from the description). It falls short of anchor 5's comprehensive coverage, and "Masters" is mild over-claim language, keeping it below a 5.

4 / 5

Completeness

Clearly answers both: the "what" via "Masters event store design, projection building, saga orchestration, and eventual consistency patterns" and the "when" via the explicit trigger clause "Use for event-sourced systems, audit trails, or temporal queries" with concrete trigger phrases. This matches the anchor-5 example pattern (what + explicit 'Use when' with concrete triggers) and is clearly above anchor 4, whose 'when' is generic.

5 / 5

Trigger Term Quality

Good keyword coverage with natural terms users would say: "event sourcing", "CQRS", "event-driven architecture", "audit trails", "temporal queries". A few natural variations are missing (e.g., "event store", "undo/redo", "time travel", "microservices"), which matches anchor 4 rather than anchor 5's comprehensive synonym/extension coverage.

4 / 5

Distinctiveness Conflict Risk

Event sourcing/CQRS is a clear niche with distinct triggers ("event-sourced systems", "temporal queries") unlikely to fire the wrong skill. Minor overlap risk remains: "audit trails" and "event-driven architecture" are broad enough to overlap with logging/security or general architecture skills, so it fits anchor 4 rather than anchor 5's minimal-conflict bar.

4 / 5

Total

17

/

20

Passed

Validation

100%

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

Reviewed

Table of Contents

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.