# Notification Strategy

> 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.

- Skill: `sylphxai/notification-strategy` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add sylphxai/notification-strategy`
- Raw SKILL.md: https://api.skillmd.com/api/skills/sylphxai/notification-strategy/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: SylphxAI (https://skillmd.com/u/sylphxai)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/sylphxai/notification-strategy

---


# 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.