pragmatic-use-events SKILL.md skillA
pragmatic-use-events from pragmatic-design/pragmatic.design is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add pragmatic-design/pragmatic.design/pragmatic-use-events@git:20261031.7fecbf3Pins git:20261031.7fecbf3 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- pragmatic-design/pragmatic.design
- Path
marketplace/plugins/pragmatic-design/skills/pragmatic-use-events/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261031.7fecbf3, committed Oct 31, 2026
- First version recorded
- Oct 3, 2026
- Size
- 15,190 bytes
- Repository stars
- 15
- License
- a license file GitHub does not identify
Use when an entity raises a domain event and a handler in the same process reacts after commit (Pragmatic.Events, [EventHandler], ordering, lifecycle [Raises<T>], event outbox). Cross-boundary work is pragmatic-use-messaging.
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
# Pragmatic Use Events **Covers:** In-process domain events with Pragmatic.Events: RaiseEvent, [EventHandler]/IDomainEventHandler<T>, handler ordering, dispatch after commit, lifecycle [Raises<T>], the transactional event outbox. `Pragmatic.Events` handles **in-process domain events**: an entity raises an event during business logic, and one or more handlers react after the change is persisted, in the same process, with no message bus. The source generator discovers handlers and builds an AOT-safe typed dispatch table. ## When to use - An entity change should trigger a side effect in the **same boundary/process** (e.g. confirming a reservation sends a notification). - You want the reaction to run **after a successful save**, not inside the request handler. For **cross-boundary** or **durable/async** reactions (another service, a queue, retries across restarts) use `pragmatic-use-messaging`: publish to `IMessageBus` and handle with `[MessageHandler] IMessageHandler<T>`. Rule of thumb: same boundary, in-process → `IDomainEventHandler<T>` (this skill); cross-boundary/durable → the bus. ## Packages ```xml <PackageReference Include="Pragmatic.Events" Version="1.0.0-alpha.3" /> …
Read the whole file at its exact version.
How to install
mdr add pragmatic-design/pragmatic.design/pragmatic-use-events@sha256:bd2f82e1b88ea569The line at the top of this page pins the label git:20261031.7fecbf3, 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_tbluo6tvnyxcwawp)
0 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Oct 3, 2026 and Oct 31, 2026, about one every 7 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261031.7fecbf3 latest | 2026-10-31 | 7fecbf3 | 15,190 B | A | view · diff |
| git:20261017.dc88d60 | 2026-10-17 | dc88d60 | 15,090 B | A | view · diff |
| git:20261012.bc22592 | 2026-10-12 | bc22592 | 15,090 B | A | view · diff |
| git:20261004.7a4079a | 2026-10-04 | 7a4079a | 15,090 B | A | view · diff |
| git:20261003.e164ceb | 2026-10-03 | e164ceb | 15,169 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 (15190 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
pragmatic-design/pragmatic.design · 15 stars · license a license file GitHub does not identify · pushed 2026-11-07 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_tbluo6tvnyxcwawp GET https://markdownregistry.com/api/v1/resolve?ref=pragmatic-design/pragmatic.design/pragmatic-use-events GET https://markdownregistry.com/api/v1/blob/bd2f82e1b88ea569d903d55e1d765cb9850e974a6c63f6235ff352ef299f9dba
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.