CtrlK
BlogDocsLog inGet started
Tessl Logo

chatto-event-sourcing

Use when designing, implementing, reviewing, debugging, or documenting Chatto event-sourced domain behavior, including EVT subjects, aggregate boundaries, Services, projections, optimistic concurrency control, read-your-writes, live/reconnect delivery, replay compatibility, migration safety, and rollback/deployment implications.

74

Quality

92%

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

SKILL.md
Quality
Evals
Security

Quality

Content

85%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 a dense, well-structured set of event-sourcing guardrails with strong workflow sequencing, validation feedback loops, and clean progressive disclosure via signaled repo-doc references. Slight conciseness and code-block gaps keep it from a perfect score on two dimensions.

Suggestions

Tighten the longest rule sections (Latest-Value Runtime Indexes, Post-Commit Side Effects) by collapsing repeated 'document and test' phrasings into a single checklist item.

Add one small concrete code/pseudocode snippet for the OCC append+retry loop to push actionability from mostly-executable to copy-paste ready.

DimensionReasoningScore

Conciseness

High-signal, domain-specific guardrails with no basic-concept padding, but the ~310-line body has some repetition and lengthy rule lists that could be tightened; sits noticeably above the 'mostly efficient' anchor but short of fully lean.

4 / 5

Actionability

Concrete file anchors, named helpers (evtstream.Publisher, AppendAtFilter, LastSubjectPosition), and real commands (mise bench-projections) give mostly executable guidance; no full code blocks, but that is justified for an architecture/guardrail skill.

4 / 5

Workflow Clarity

Numbered pre-write checklist, OCC retry/re-read/re-check feedback loop, snapshot evolution checklist, and explicit 'wait for projection readiness then re-check' validation steps provide clear sequencing with error-recovery loops.

5 / 5

Progressive Disclosure

Single well-organized SKILL.md with clear headers and one-level-deep signaled pointers to repo docs (docs/architecture/INDEX.md, docs/adr/INDEX.md, docs/fdr/, AGENTS.md, ../loom-architecture/SKILL.md); no nested references and content appropriately split.

5 / 5

Total

18

/

20

Passed

Description

100%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 exemplary: third-person voice, concrete capability list, explicit 'Use when' triggers, and a distinctive niche that minimizes conflict risk. It satisfies every dimension at the top anchor.

DimensionReasoningScore

Specificity

Lists multiple concrete actions (designing, implementing, reviewing, debugging, documenting) alongside concrete domain objects (EVT subjects, aggregate boundaries, Services, projections, OCC, read-your-writes, replay/migration/rollback), giving comprehensive coverage.

5 / 5

Completeness

Explicitly answers both 'what' (Chatto event-sourced domain behavior with enumerated subtopics) and 'when' ('Use when designing, implementing, reviewing, debugging, or documenting...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Opens with explicit 'Use when' triggers and covers natural verb phrases plus domain synonyms (reviewing/debugging, live/reconnect, rollback/deployment) a developer would actually say.

5 / 5

Distinctiveness Conflict Risk

Targets a highly specific niche (Chatto event-sourcing, EVT subjects, aggregate lanes, projections, OCC) with distinct triggers and minimal overlap risk with other skills.

5 / 5

Total

20

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 suspicious

Warning

Total

15

/

16

Passed

Repository
chattocorp/chatto
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.