CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

80

1.15x
Quality

70%

Does it follow best practices?

Impact

99%

1.15x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./tests/ext_conformance/artifacts/agents-wshobson/backend-development/skills/event-store-design/SKILL.md

The canonical home for this skill is event-store-design in wshobson/agents

SKILL.md
Quality
Evals
Security

Quality

Content

57%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 actionable and well-sectioned with concrete executable templates, but it is token-heavy from inlining four full implementations and lacks an explicit sequenced workflow with validation checkpoints. Splitting templates into reference files and adding a validation-gated design sequence would raise the weaker dimensions.

Suggestions

Move the per-technology implementations (EventStoreDB, DynamoDB) into separate reference files and keep only the PostgreSQL quick-start inline, reducing token load and improving progressive disclosure.

Add an explicit numbered design workflow with validation checkpoints (e.g., define schema -> implement append with optimistic concurrency -> verify idempotency -> load-test) so multi-step processes are clearly sequenced.

Fix the DynamoDB template so the code actually performs a conditional write (ConditionExpression on expected version) to match its docstring claim, closing the actionability and workflow-clarity gap.

DimensionReasoningScore

Conciseness

The prose is lean and assumes Claude's knowledge, but four full inline implementations (~430 lines total) is heavy; the volume could be tightened by moving some templates to reference files.

3 / 5

Actionability

Provides mostly executable, copy-paste-ready SQL and Python templates across PostgreSQL, EventStoreDB, and DynamoDB; a minor gap is the DynamoDB 'conditional write for concurrency' comment that does not match the batch_writer code, which lacks a ConditionExpression.

4 / 5

Workflow Clarity

There is no explicit multi-step design/implementation sequence with checkpoints; the PostgreSQL template includes optimistic-concurrency validation but the DynamoDB one does not, and the batch/destructive-operation cap at 3 applies.

3 / 5

Progressive Disclosure

Section headers are well-organized, but at ~430 lines all content is inlined with no bundle files and templates that clearly belong in separate reference files; the under-50-line simple-skill exception does not apply.

3 / 5

Total

13

/

20

Passed

Description

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

The description is well-structured with explicit what and when guidance and a clear, distinctive niche. Its only weakness is specificity, as it offers just two verbs ('Design and implement') rather than a fuller enumeration of concrete capabilities.

DimensionReasoningScore

Specificity

Names the domain ('event stores for event-sourced systems') with two concrete actions ('Design and implement'), matching the anchor for 1-2 actions that are not comprehensive; it does not list the several specific actions needed for a 4.

3 / 5

Completeness

It explicitly answers what ('Design and implement event stores for event-sourced systems') and when ('Use when building event sourcing infrastructure, choosing event store technologies, or implementing event persistence patterns') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural trigger phrases like 'building event sourcing infrastructure', 'choosing event store technologies', and 'implementing event persistence patterns' give good keyword coverage, though a few common synonyms are absent.

4 / 5

Distinctiveness Conflict Risk

'Event stores for event-sourced systems' is a clear niche with distinct triggers and minimal overlap risk with other skills.

5 / 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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
Dicklesworthstone/pi_agent_rust
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.