custom-notification-type-design SKILL.md skillA
custom-notification-type-design from pranavnagrecha/awesomesalesforceskills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add pranavnagrecha/awesomesalesforceskills/custom-notification-type-design@v1.0.1Pins v1.0.1 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- pranavnagrecha/awesomesalesforceskills
- Path
skills/admin/custom-notification-type-design/SKILL.md- Versions recorded
- 5
- Latest version
- v1.0.1, committed Aug 15, 2026
- First version recorded
- Apr 23, 2026
- Size
- 18,436 bytes
- Repository stars
- 19
- License
- a license file GitHub does not identify
Use when designing Custom Notification Types that fire via Flow, Apex, or Process Builder to Lightning bell, desktop, mobile (push), and Slack. Covers channel enablement, targeting, deliverability, consent, and anti-spam discipline. NOT for actually sending one from Flow or Apex, or the recipient limit — use admin/custom-notification-types. NOT for email templates and alerts — use admin/email-templates-and-alerts.
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
# Custom Notification Type Design A Custom Notification Type is the *definition* of a notification: its label, its API name, and which delivery channels it is allowed to use. It is not the send. Designing one badly is cheap, invisible, and permanent — the notification still "works" in the sense that `send()` returns without an exception, and the user still never sees it, or sees it forty times a day and mutes the whole channel. Two failure shapes dominate, and they need opposite fixes: | Symptom | Actual cause | Where it is designed away | |---|---|---| | "The notification never arrives" | One of four independent delivery gates is closed | The delivery chain, below | | "Users muted the bell / uninstalled the app" | Every event became a notification | Targeting, throttling, and the registry | **Scope.** This skill owns the *design and governance* decisions: which channels a type should declare, who should receive it, how often, what the deep link opens, and how the org keeps the set of notification types from sprawling. The mechanics of the send — `Messaging.CustomNotification`, the Flow `customNotificationAction`, the 500-value recipient cap, bulk send patterns — …
Read the whole file at its exact version.
How to install
mdr add pranavnagrecha/awesomesalesforceskills/custom-notification-type-design@sha256:b361babb1cb77908The line at the top of this page pins the label v1.0.1, 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_fenijk3z3qcodlt2)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Apr 23, 2026 and Aug 15, 2026, about one every 28 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.0.1 latest | 2026-08-15 | c68b1c4 | 18,436 B | A | view · diff |
| v1.0.0 | 2026-08-14 | 25df1fd | 5,079 B | A | view · diff |
| v1.0.0 | 2026-05-09 | efe29f6 | 5,004 B | A | view · diff |
| v1.0.0 | 2026-04-28 | 11a35fb | 4,903 B | A | view · diff |
| v1.0.0 | 2026-04-23 | e6e608c | 5,088 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 (18436 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
pranavnagrecha/awesomesalesforceskills · 19 stars · license a license file GitHub does not identify · pushed 2026-10-20 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_fenijk3z3qcodlt2 GET https://markdownregistry.com/api/v1/resolve?ref=pranavnagrecha/awesomesalesforceskills/custom-notification-type-design GET https://markdownregistry.com/api/v1/blob/b361babb1cb779082bd552d848a7ed2f4b5ed61aaeb25f2ddea45fa150869de3
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.