Menu

Individual skill

push-notification-copy

Writes push and in-app notification copy that survives lock-screen truncation, ties every send to a user-specific trigger, deep-links to the exact destination, and respects frequency caps. Use when someone asks "write a push notification for this event", "why is our push opt-out rate rising", "draft re-engagement push copy", or is planning lifecycle, transactional, or re-engagement notifications. Do NOT use for implementing the delivery pipeline, tokens, or notification infrastructure - use push-notification-wirer instead; for deciding which lifecycle stage should send push at all, start with lifecycle-journey-map.

skills/push-notification-copy/SKILL.md

Read pinned source

Source commit 97a13607d669157a4a16d5ba79b77f208319f7b9

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Instructions only
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
24
Repository last updated
Oct 13, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Push Notification Copy

Push notifications live one tap away from being blocked permanently. Every send either builds or spends trust, the bar for sending is higher than email, and the margin for error is narrower - one misleading or mistimed push can cost the channel for that user forever. This skill prevents the two fatal patterns: copy that truncates into nonsense on the lock screen, and sends that exist because a calendar said so rather than because something happened.

## Inputs to collect

1. **The triggering event** - what just happened to this specific user (price drop, milestone, message received, task due). If the requester cannot name a user-specific trigger, stop: the send should not exist. Scheduled blasts untied to user events are spam regardless of how well-written they are.
2. **The deep-link destination** - the exact screen the tap opens. A push that dumps the user on the home screen breaks the promise the copy made.
3. **The variable data available** - names, amounts, deadlines, counts. Specifics are what make the body line earn its place.
4. **The user's recent notification history** - what they received in the last 24 hours and 7 days, to check against caps.
5. **Platform(s)** - iOS, Android, browser - for truncation behavior.

## Operating procedure