pragmatic-use-email SKILL.md skillA
pragmatic-use-email 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-email@git:20261017.dc88d60Pins git:20261017.dc88d60 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-email/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261017.dc88d60, committed Oct 17, 2026
- First version recorded
- Oct 2, 2026
- Size
- 8,628 bytes
- Repository stars
- 15
- License
- a license file GitHub does not identify
Use when the app sends mail directly, configures SMTP, signs with DKIM or S/MIME, or asserts on sent mail (Pragmatic.Email). Bodies are pragmatic-use-documents; routing across channels is pragmatic-use-notifications.
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 Email
**Covers:** Send e-mail with Pragmatic.Email: message builder, pooled SMTP with STARTTLS and AUTH, DKIM and S/MIME signing, middleware, in-memory and file transports for tests.
`Pragmatic.Email` sends mail over SMTP with no external dependencies: it builds the MIME itself, pools
connections, and exposes a middleware pipeline for cross-cutting concerns.
Sending *one* e-mail? Use this. Routing a notification across e-mail/webhook with user preferences and
delivery tracking? Use `pragmatic-use-notifications`, which delegates to this library.
## Packages
```xml
<PackageReference Include="Pragmatic.Email" Version="1.0.0-alpha.3" />
<PackageReference Include="Pragmatic.Email.Testing" Version="1.0.0-alpha.3" /> <!-- test projects -->
```
## Core pattern
Build the message with the builder, send it through the injected `IEmailSender`:
```csharp
var message = new EmailMessageBuilder()
.From("booking@hotel.com", "Hotel Booking")
.To(guest.Email, guest.FullName)
.Cc("desk@hotel.com")
.ReplyTo("noreply@hotel.com")
.Subject("Reservation confirmed")
.TextBody("Your reservation is confirmed.")
…Read the whole file at its exact version.
How to install
mdr add pragmatic-design/pragmatic.design/pragmatic-use-email@sha256:cddcea4eb93745feThe line at the top of this page pins the label git:20261017.dc88d60, 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_fyf4xuyqdvjfbfqi)
0 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Oct 2, 2026 and Oct 17, 2026, about one every 4 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261017.dc88d60 latest | 2026-10-17 | dc88d60 | 8,628 B | A | view · diff |
| git:20261012.bc22592 | 2026-10-12 | bc22592 | 8,628 B | A | view · diff |
| git:20261004.7a4079a | 2026-10-04 | 7a4079a | 8,628 B | A | view · diff |
| git:20261003.e164ceb | 2026-10-03 | e164ceb | 8,662 B | A | view · diff |
| git:20261002.ccb0d57 | 2026-10-02 | ccb0d57 | 8,662 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 (8628 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_fyf4xuyqdvjfbfqi GET https://markdownregistry.com/api/v1/resolve?ref=pragmatic-design/pragmatic.design/pragmatic-use-email GET https://markdownregistry.com/api/v1/blob/cddcea4eb93745fe63db451dfd96bb26e7cc4daaba310fc1aeca799fdbe45982
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.