email-manual-notifications-and-delivery SKILL.md skillA
email-manual-notifications-and-delivery from lingtai-ai/lingtai-kernel is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add lingtai-ai/lingtai-kernel/email-manual-notifications-and-delivery@v1.0.0Pins v1.0.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- lingtai-ai/lingtai-kernel
- Path
src/lingtai/tools/email/manual/reference/notifications-and-delivery/SKILL.md- Versions recorded
- 4
- Latest version
- v1.0.0, committed Oct 6, 2026
- First version recorded
- Sep 7, 2026
- Size
- 4,802 bytes
- Repository stars
- 11
- License
- Apache-2.0
Focused Email reference for daemon delivery, heartbeat/liveness, bounce recovery, unread payloads, persistent bodies, overflow, and read-state refresh. Read when delivery or notices need diagnosis.
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
# Email notifications and delivery ## Delivery, liveness, and recovery `send` writes each recipient's outbox entry, then starts that recipient's daemon `_mailman` thread before that call's unified sent record is written. Even `delay=0` can return `sent` before delivery finishes. A later thread-start or persistence failure can leave earlier deliveries; neither a failed call nor a missing sent record proves zero effect. Delay waits in a daemon thread: this is not a restart-resilient queue. A process exit can strand outbox files; no automatic replay is promised. Non-self POSIX targets need `.agent.json` presence and a Core-fresh `.agent.heartbeat`; use current kernel liveness policy, not a fixed Email timeout. Core currently counts even malformed manifests as present; a valid manifest with missing/null `admin` identifies a human and bypasses heartbeat checks. This is implementation truth, not permission to deliver to an unverified owner. Self-send bypasses this transport handshake. Refresh/relaunch windows can produce `not running`; refused attempts are not queued for a later retry. Failures publish `email.bounce` in `.notification/system.json`. …
Read the whole file at its exact version.
How to install
mdr add lingtai-ai/lingtai-kernel/email-manual-notifications-and-delivery@sha256:6445686a27d9d705The line at the top of this page pins the label v1.0.0, 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_l4fnswmk75fy4hpt)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between Sep 7, 2026 and Oct 6, 2026, about one every 10 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.0.0 latest | 2026-10-06 | be2f520 | 4,802 B | A | view · diff |
| v1.0.0 | 2026-10-02 | cb3dd19 | 4,793 B | A | view · diff |
| v1.0.0 | 2026-09-09 | 79d6664 | 4,716 B | A | view · diff |
| v1.0.0 | 2026-09-07 | bd594c1 | 5,022 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 (4802 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
lingtai-ai/lingtai-kernel · 11 stars · license Apache-2.0 · pushed 2026-10-21 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_l4fnswmk75fy4hpt GET https://markdownregistry.com/api/v1/resolve?ref=lingtai-ai/lingtai-kernel/email-manual-notifications-and-delivery GET https://markdownregistry.com/api/v1/blob/6445686a27d9d705db7e1d6af18370b153a0d75fa4e9860033651cb2a5183402
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.