notification-manual-dismissal-safety SKILL.md skillA
notification-manual-dismissal-safety 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/notification-manual-dismissal-safety@v0.6.0Pins v0.6.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/notification/manual/reference/dismissal-safety/SKILL.md- Versions recorded
- 4
- Latest version
- v0.6.0, committed Oct 2, 2026
- First version recorded
- Aug 24, 2026
- Size
- 4,223 bytes
- Repository stars
- 11
- License
- Apache-2.0
One-shot notification delivery and producer-state safety reference: there is no public notification dismiss action; delivery never clears producer state; how deliberate check, post-molt, protected channels, hooks, and legacy large-result reminders behave. Read after notification-manual when unsure whether a notification will reappear or how to resolve its producer state.
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
# Notification Delivery and Producer-State Safety
## Delivered once; never cleared by delivery
Each notification event is attached to your context automatically once. A new or
changed event (new mail, a new IM message, a new system event, a daemon
completion, a delay alarm, a post-molt record) is attached and wakes you again; an
unchanged one is not re-attached, and later tool results simply carry no
notification keys for it. An absent notification key means *nothing new*, not
*resolved*.
Delivery never clears, completes, or acknowledges anything: notification files
and producer business state (mailbox, IM history, goal, source queues) are left
exactly as they were. There is no public `dismiss_channel`, `dismiss_event`, or
`dismiss_ref` action and no alias for them. Do not delete `.notification/` files.
`notification(action='check', input={}, ...)` is a deliberate read: it returns the
complete current mirrors even if they were already delivered automatically, and
it clears nothing. It is not an automatic replay.
…Read the whole file at its exact version.
How to install
mdr add lingtai-ai/lingtai-kernel/notification-manual-dismissal-safety@sha256:a10e5b117b3c2775The line at the top of this page pins the label v0.6.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_wcf5p56xpkolwwwr)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between Aug 24, 2026 and Oct 2, 2026, about one every 13 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v0.6.0 latest | 2026-10-02 | cb3dd19 | 4,223 B | A | view · diff |
| v0.5.0 | 2026-10-02 | e38649c | 4,521 B | A | view · diff |
| v0.5.0 | 2026-09-09 | 3a368b2 | 4,515 B | A | view · diff |
| v0.4.0 | 2026-08-24 | 984e1eb | 5,845 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 (4223 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_wcf5p56xpkolwwwr GET https://markdownregistry.com/api/v1/resolve?ref=lingtai-ai/lingtai-kernel/notification-manual-dismissal-safety GET https://markdownregistry.com/api/v1/blob/a10e5b117b3c277503bbc5d740874a9634201b4505a0c7a99d6b44b7cdb2917c
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.