Assess a notification strategy — stop conditions, cooldowns, cadence, quiet hours, and suppression. Use when the user asks to review notifications, push strategy, or messaging cadence. Do not use to design the notification system.
Installs into .claude/skills of the current project.
Are you the author of Notification Strategy?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/sylphxai-notification-strategy)
---
name: notification-strategy
description: "Assess a notification strategy — stop conditions, cooldowns, cadence, quiet hours, and suppression. Use when the user asks to review notifications, push strategy, or messaging cadence. Do not use to design the notification system."
---
# Review Notification Strategy
Every notification needs a stop condition, a cooldown, and a way to make the same outcome available in-product without the ping. A streak or campaign does not inherit emergency rights. Measure useful action after open, not send volume. A message that cannot be turned off is not a notification, it is an interruption with no owner.
Open [notification strategy patterns](references/notification-strategy-patterns.md) for cadence, quiet hours, preference, and suppression.
