transactional-messaging SKILL.md skillA
transactional-messaging from 808enzo/chappie is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add 808enzo/chappie/transactional-messaging@git:20261009.fdb6855Pins git:20261009.fdb6855 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- 808enzo/chappie
- Path
skills/transactional-messaging/SKILL.md- Versions recorded
- 4
- Latest version
- git:20261009.fdb6855, committed Oct 9, 2026
- First version recorded
- Sep 17, 2026
- Size
- 19,263 bytes
- Repository stars
- 2
- License
- MIT
Decide which service messages an order, booking, payment or account request sets off, what each contains, and how fast it arrives. Use when people keep asking where their order is, a delay notice comes late, or someone wants a cross-sell in the confirmation. Not marketing event flows (triggered-messages) or the cap (contact-orchestration).
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
# transactional-messaging This skill answers one question: **what the program owes a person about something they set in motion (an order, a booking, a payment, an account request): which state change, or which promised time about to go unkept, produces a message, what the message has to contain, how fast and through which channel it has to arrive, what else it may carry, and how you know the set of messages does its job.** What sets this work apart from the rest of the library opens `references/service-vocabulary.md`. **Three units, named apart.** The *transaction* is what the person set in motion and is waiting on: an order with all its shipments, a booking, a payment, an account request. It is the unit of reading. The *service message* is a row of the register: one person-facing state, or one promised time about to be missed, with its trigger, content contract, deadline, channels and owner. It is the unit of construction. The *send* is one message to one person, on one attempt, in one channel. It is the unit of delivery. Mixing the first two is the argument about "how many statuses to send": one side counts messages, the …
Read the whole file at its exact version.
How to install
mdr add 808enzo/chappie/transactional-messaging@sha256:f990db4a2684c3e7The line at the top of this page pins the label git:20261009.fdb6855, 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_tibwrp2jv44qrxfd)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between Sep 17, 2026 and Oct 9, 2026, about one every 7 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261009.fdb6855 latest | 2026-10-09 | fdb6855 | 19,263 B | A | view · diff |
| git:20260929.08d0187 | 2026-09-29 | 08d0187 | 19,139 B | A | view · diff |
| git:20260929.bff2a99 | 2026-09-29 | bff2a99 | 19,072 B | A | view · diff |
| git:20260917.0d90f8f | 2026-09-17 | 0d90f8f | 28,318 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 (19263 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
808enzo/chappie · 2 stars · license MIT · pushed 2026-10-15 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_tibwrp2jv44qrxfd GET https://markdownregistry.com/api/v1/resolve?ref=808enzo/chappie/transactional-messaging GET https://markdownregistry.com/api/v1/blob/f990db4a2684c3e72e9bb42a3106927ce0c10f8aedf781c0d4cde2e4840b61c3
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.