CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

71%

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-store-design/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

51%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 concrete, executable material — a real schema, working code for three technologies, and a useful comparison table — but it reads as a reference dump rather than a guided skill. Generic boilerplate sections pad the token budget, no sequenced design/implementation workflow with validation checkpoints is provided, and the large templates should live in reference files rather than inline.

Suggestions

Replace the generic 'Instructions' and 'Do not use this skill when' boilerplate with a sequenced domain workflow, e.g.: 1) choose technology via the comparison table, 2) create the schema, 3) implement append/read, 4) verify concurrency handling (test duplicate/optimistic-concurrent appends), 5) confirm subscriptions resume from their checkpoint.

Move the four large code templates into reference files (e.g., templates/postgres.md, templates/dynamodb.md) and keep a concise quick-start example plus navigation links in SKILL.md.

Fix the executable gaps: import asyncio in Template 2, and implement real conditional writes in the DynamoDB template (TransactWriteItems or a ConditionExpression on the expected version) instead of batch_writer.

DimensionReasoningScore

Conciseness

The bulk of the body is dense, useful material (tables, executable SQL/Python), but it is padded by two boilerplate sections — "The task is unrelated to event store design" / "You need a different domain or tool outside this scope" and the generic "Clarify goals, constraints, and required inputs... Apply relevant best practices" instructions — that add no domain value, and four full code templates (~350 lines) inflate the token load. This sits between 'noticeably verbose' and 'efficient', matching the mostly-efficient-but-could-be-tightened anchor.

3 / 5

Actionability

The four templates are concrete, mostly executable code: a complete PostgreSQL DDL schema, an asyncpg EventStore class, esdbclient usage, and a DynamoDB implementation. It falls short of fully copy-paste ready because of minor gaps — Template 2 calls asyncio.sleep without importing asyncio, and Template 4 claims 'conditional write for concurrency' but uses batch_writer with no condition expression, so the concurrency check is not actually implemented.

4 / 5

Workflow Clarity

No sequenced workflow is presented: the 'Instructions' section is generic directives ('Clarify goals... Apply relevant best practices and validate outcomes') rather than steps, and there are no validation checkpoints for the database operations the skill covers (schema creation, concurrent appends, subscription resume). The section ordering (concepts → tech comparison → templates → practices) gives only a rough implicit sequence with poorly defined steps and absent validation, matching the anchor below 'steps listed'.

2 / 5

Progressive Disclosure

The body has clear section headers and decent organization, but no bundle files exist (no references/, scripts/, or assets/) and roughly 350 lines of code templates are inlined in SKILL.md — content that clearly belongs in separate reference files per the rubric. This matches 'some structure but content that should be separate is inline'; it is above the minimal-structure anchor because headers make it navigable, and above-the-50-line simple-skill exception does not apply.

3 / 5

Total

12

/

20

Passed

Description

78%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 well-formed description with a clear what-clause and an explicit, well-structured 'Use when' trigger clause containing concrete phrases. Its main weakness is that the capability statement is generic ('design and implement') rather than enumerating the specific actions the skill actually supports.

Suggestions

List concrete capabilities in the what-clause (e.g., 'create event store schemas, implement append-only persistence with optimistic concurrency, set up subscriptions and snapshots') instead of the generic 'design and implement'.

Add natural trigger synonyms users might say, such as 'event storage', 'append-only log', 'CQRS', or specific technology names (Postgres, Kafka, EventStoreDB) that the skill covers.

DimensionReasoningScore

Specificity

The what-clause names the domain and only two fairly generic actions — "Design and implement event stores" — without listing specific capabilities like schema creation, optimistic concurrency, or subscription management. This matches the 'names domain and 1-2 concrete actions' anchor; it is not score 4 because several specific actions are absent, and not score 2 because the domain and actions are explicitly named.

3 / 5

Completeness

It explicitly answers both questions: "Design and implement event stores for event-sourced systems" (what) followed by an explicit "Use when building event sourcing infrastructure, choosing event store technologies, or implementing event persistence patterns" (when) with three concrete trigger phrases. This mirrors the top-anchor example structure; the 'Use when' clause is present so no cap applies.

5 / 5

Trigger Term Quality

Natural phrases users would say are present — "event sourcing", "event store", "event-sourced", "event persistence", "building event sourcing infrastructure", "choosing event store technologies" — giving good keyword coverage. It falls short of the comprehensive anchor because common variations like 'event storage', 'append-only store', or technology names (Postgres, Kafka) are missing.

4 / 5

Distinctiveness Conflict Risk

Event store design is a clear niche with distinct triggers, so it is mostly distinguishable from unrelated skills. It stays below the top anchor because "implementing event persistence patterns" is broad enough to overlap with closely related skills (general event-sourcing patterns, database persistence, or streaming skills).

4 / 5

Total

16

/

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-store-design/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.