cratis-chronicle-event-specifications SKILL.md skillA
cratis-chronicle-event-specifications from cratis/ai is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add cratis/ai/cratis-chronicle-event-specifications@git:20261014.64fcc06Pins git:20261014.64fcc06 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- cratis/ai
- Path
.cratis/ai/skills/cratis-chronicle-event-specifications/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261014.64fcc06, committed Oct 14, 2026
- First version recorded
- Sep 16, 2026
- Size
- 9,875 bytes
- Repository stars
- 4
- License
- MIT
Specify event-append behavior with EventScenario from Cratis.Chronicle.Testing — seeding prior events through Given, appending through When or the event log, and asserting on the append result including constraint violations. Use when the behavior under specification is what reaches the event store. Do not use for command handling or for read-model projection behavior.
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
# Chronicle event specifications `EventScenario` runs the append path in-process. No Chronicle server, no database, no network — an empty event log at sequence number zero, with the application's constraints discovered and active. ## Verified product sources | Package | Purpose | | --- | --- | | `Cratis.Chronicle.Testing` | `EventScenario`, its `Given`/`When` builders, the `IAppendResult` `Should*` assertions | | `Cratis.Chronicle` | `IEventSequence.Append`/`AppendMany`, `IAppendResult`, `ConstraintViolation` | Sources: `Source/Clients/Testing/EventSequences/`, `TestingEventStore.cs`, and `Source/Clients/DotNET/EventSequences/`. ```bash dotnet add package Cratis.Chronicle.Testing ``` Reverify against the Chronicle repository before claiming support for another version. Never translate an assertion name from memory. ## Route near misses - The behavior is a command running through validators, `Provide()` and `Handle()`: use `cratis-application-slice-specifications`. - The behavior is a projection or reducer building a read model: use `cratis-chronicle-read-model-specifications`. - You are deciding what the constraint should *be*: use …
Read the whole file at its exact version.
How to install
mdr add cratis/ai/cratis-chronicle-event-specifications@sha256:d3f8fc7f2721cb70The line at the top of this page pins the label git:20261014.64fcc06, 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_f7q3k45ez3lg52fr)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Sep 16, 2026 and Oct 14, 2026, about one every 7 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261014.64fcc06 latest | 2026-10-14 | 64fcc06 | 9,875 B | A | view · diff |
| git:20261013.9c1bacb | 2026-10-13 | 9c1bacb | 9,424 B | A | view · diff |
| git:20261012.a7621fb | 2026-10-12 | a7621fb | 9,492 B | A | view · diff |
| git:20261006.3b4e4b3 | 2026-10-06 | 3b4e4b3 | 8,984 B | A | view · diff |
| git:20260916.2dd9dbe | 2026-09-16 | 2dd9dbe | 8,783 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 (9875 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
cratis/ai · 4 stars · license MIT · pushed 2026-11-04 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_f7q3k45ez3lg52fr GET https://markdownregistry.com/api/v1/resolve?ref=cratis/ai/cratis-chronicle-event-specifications GET https://markdownregistry.com/api/v1/blob/d3f8fc7f2721cb706ef646eef59b797784137696a836bc0ec25df79935bb26e8
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.