event-sourcing SKILL.md skillA
event-sourcing from robsonkades/agent-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add robsonkades/agent-skills/event-sourcing@git:20261016.c769bd8Pins git:20261016.c769bd8 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- robsonkades/agent-skills
- Path
skills/event-sourcing/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261016.c769bd8, committed Oct 16, 2026
- First version recorded
- Sep 6, 2026
- Size
- 13,927 bytes
- Repository stars
- 3
- License
- Apache-2.0
Event streams as authoritative state: adoption criteria, stream boundaries, expected-version appends, command idempotency, snapshots, projection correctness/rebuild, temporal replay, schema evolution and erasure. Use when event sourcing is proposed, projections drift, old payloads must evolve, or write/read visibility surprises users. Integration messaging, delivery, sagas, mutable-row locking and replica consistency remain separate skills.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Event Sourcing ## Purpose Decide, and then correctly operate, a system whose durable truth is an append-only sequence of facts rather than a mutable row. State is a fold over that sequence; the row you used to update becomes a derived view you can throw away and rebuild. This can preserve a sequenced decision history, reconstruct state under a specified model and build new views from retained facts. It does **not** automatically make history complete, tamper-evident, legally immutable or semantically reproducible: missing external inputs, changed projection code and retention/redaction policies still matter. The durable obligation is to keep event meaning, replay tooling and governance compatible for the declared horizon. Compare audit/history storage before adopting event sourcing solely for auditability; measure actual operating cost rather than assuming a fixed ratio. Design schema evolution, projection rebuilds and retention/erasure before committing long-lived history. Inspect the target JDK, event-store/server and client versions, append/subscription contracts, retention and transaction manager. Java examples use Java 21 standard pattern switches …
Read the whole file at its exact version.
How to install
mdr add robsonkades/agent-skills/event-sourcing@sha256:4f79b2f16eee44d6The line at the top of this page pins the label git:20261016.c769bd8, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_ktt4bcm3chpttcqh)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Sep 6, 2026 and Oct 16, 2026, about one every 10 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261016.c769bd8 latest | 2026-10-16 | c769bd8 | 13,927 B | A | view · diff |
| git:20260927.9ecadfd | 2026-09-27 | 9ecadfd | 13,727 B | A | view · diff |
| git:20260923.832673e | 2026-09-23 | 832673e | 13,323 B | A | view · diff |
| git:20260911.37b054b | 2026-09-11 | 37b054b | 13,022 B | A | view · diff |
| git:20260906.e6ad4bd | 2026-09-06 | e6ad4bd | 12,490 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (13927 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
robsonkades/agent-skills · 3 stars · license Apache-2.0 · pushed 2026-10-28 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ktt4bcm3chpttcqh GET https://markdownregistry.com/api/v1/resolve?ref=robsonkades/agent-skills/event-sourcing GET https://markdownregistry.com/api/v1/blob/4f79b2f16eee44d6944b05fce0c9fa4dd6434849432d3ad39386d0d3d83ac37c
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.