pragmatic-use-distributed SKILL.md skillA
pragmatic-use-distributed 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-distributed@git:20261004.7a4079aPins git:20261004.7a4079a 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-distributed/SKILL.md- Versions recorded
- 3
- Latest version
- git:20261004.7a4079a, committed Oct 4, 2026
- First version recorded
- Oct 2, 2026
- Size
- 8,381 bytes
- Repository stars
- 15
- License
- a license file GitHub does not identify
Use when splitting out a service, scaling a host out, adding a gateway, or when instances disagree (stale cache, a job run twice); [RemoteBoundary], broker, sagas, Agent, YARP gateway. Decide first with pragmatic-architecture.
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 Distributed **Covers:** Run a Pragmatic app as several services or instances: [RemoteBoundary] calls, broker events and request/reply, cross-service sagas, the Pragmatic Agent, the YARP gateway, discovery, cross-instance cache invalidation. Stay a modular monolith until something forces the split: independent deployment or scaling of one area. The modules are already boundaries; splitting changes how they are **wired**, not how they are written. The examples go one step each: Invoicing is two modules in one host, Casework is two services over a broker, Warehouse is three services and two instances of one behind a gateway. ## How services talk: choose per interaction | The caller… | Shape | Mechanism | |---|---|---| | needs the answer now and knows who answers | HTTP call to another service's operations | `[RemoteBoundary<TModule>]` on the host | | needs the answer now, and any instance may answer | request/reply over the broker | `IMessageBus.RequestAsync` + a `[RequestHandler]` | | tells others something happened and does not wait | an event through the outbox | `[Raises<T>]` / published events + `[MessageHandler]` in the consumer | …
Read the whole file at its exact version.
How to install
mdr add pragmatic-design/pragmatic.design/pragmatic-use-distributed@sha256:65e68430086597d8The line at the top of this page pins the label git:20261004.7a4079a, 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_jwuiraxfe4yqtqjg)
0 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Oct 2, 2026 and Oct 4, 2026, more than one a day.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261004.7a4079a latest | 2026-10-04 | 7a4079a | 8,381 B | A | view · diff |
| git:20261003.4c87e6c | 2026-10-03 | 4c87e6c | 8,437 B | A | view · diff |
| git:20261002.ccb0d57 | 2026-10-02 | ccb0d57 | 8,277 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 (8381 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_jwuiraxfe4yqtqjg GET https://markdownregistry.com/api/v1/resolve?ref=pragmatic-design/pragmatic.design/pragmatic-use-distributed GET https://markdownregistry.com/api/v1/blob/65e68430086597d8a9c0ddbd30ae3e87299c5364df5ab62472ba80d6fde3c170
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.