本文へ移動
cccskills
無料GitHub で公開

"cs-notification-strategy"

"Design push notification and messaging strategies including channel selection, timing optimization, personalization, and fatigue management. Use this skill when the user needs to improve notification engagement, reduce opt-out rates, plan multi-channel messaging, or A/B test notification content — even if they say 'our push open rates are low', 'users are unsubscribing', 'when should we send notifications', or 'which channel to use for alerts'.".

インストール方法を見る

含まれるファイル(4)

  • SKILL.md5.4 KB
  • examples/sample_scenario.md5.8 KB
  • references/email-deliverability.md9.4 KB
  • references/line-notification.md12.9 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Notification Strategy

Framework

IRON LAW: Every Notification Must Earn Its Send

Each notification interrupts the user. If it doesn't deliver clear value
to the RECIPIENT (not to your business), it erodes trust and drives
opt-outs. Before sending: "Would the user thank me for this notification?"
If no → don't send.

Channel Comparison

ChannelOpen RateSpeedCostBest ForLimitations
Push notification5-15%InstantFreeTime-sensitive, action-neededEasy to opt out, limited text
Email15-25%MinutesLowDetailed content, receipts, newslettersSpam filters, slow
SMS90%+ openInstant$$$Critical alerts, OTP, urgentExpensive, intrusive, regulatory
In-app25-40%Next sessionFreeFeature announcements, tipsOnly reaches active users
LINE/Messenger40-60%InstantFree-$Conversational, Taiwan/AsiaPlatform dependency

Timing Optimization

AudienceBest TimeWorst Time
B2C general10-12 AM, 7-9 PM12-6 AM, during commute
B2BTue-Thu 9-11 AMWeekends, Friday PM
E-commerceThu-Sat (pre-weekend shopping)Monday AM
Breaking/urgentImmediatelyN/A

Timezone rule: Send in the RECIPIENT's timezone, not yours.

Personalization Tiers

TierWhatExampleLift vs Generic
NoneSame message to all"Check out our sale!"Baseline
SegmentBy user group"As a premium member, you get early access"+20-30%
BehavioralBased on past actions"The item in your cart is almost sold out"+40-60%
Individual1:1 personalized"Hi [Name], your favorite [Product] is back in stock"+60-80%

Fatigue Management

SignalWhat It MeansAction
Open rate decliningContent losing relevanceImprove targeting/content
Opt-out rate > 0.5%/sendSending too much or wrong contentReduce frequency, segment better
Uninstall spike after pushNotifications are driving users awayImmediately reduce volume
Click rate declining but open rate stableSubject lines good, content disappointingImprove content/offer quality

Frequency caps: Set maximum notifications per user per time period:

  • Push: max 3-5/week
  • Email: max 2-3/week (marketing), unlimited for transactional
  • SMS: max 2-4/month

A/B Testing for Notifications

ElementWhat to TestExample
Subject/titleLength, tone, emoji, personalization"Your order shipped 📦" vs "Order #1234 is on its way"
TimingHour of day, day of week10 AM vs 7 PM
ContentShort vs detailed, image vs text-only20 words vs 50 words
CTAButton text, action type"View" vs "Track Now"
ChannelPush vs email vs in-app for same messageSame content, different channel

Output Format

# Notification Strategy: {Product/Campaign}

## Channel Mix
| Message Type | Primary Channel | Fallback | Frequency |
|-------------|----------------|----------|-----------|
| {type} | {channel} | {backup} | {max/period} |

## Segmentation
| Segment | Notification | Personalization Tier |
|---------|-------------|---------------------|
| {segment} | {content} | None/Segment/Behavioral/Individual |

## Timing
| Segment | Send Time | Day | Timezone |
|---------|----------|-----|---------|
| {segment} | {HH:MM} | {day(s)} | {user's TZ} |

## Fatigue Rules
- Max push: {N}/week
- Max email: {N}/week
- Opt-out threshold: {%} → action: {reduce/pause}

## A/B Test Plan
| Test | Variant A | Variant B | Metric | Sample |
|------|----------|----------|--------|--------|
| {test} | {A} | {B} | {open rate / CTR} | {N users} |

Gotchas

  • Permission is a privilege: iOS requires explicit opt-in for push. Ask at the RIGHT moment (after the user sees value), not at first launch. First-launch permission requests get 40-60% opt-in; contextual requests get 70-80%.
  • Transactional vs marketing: Order confirmations, shipping updates, and security alerts are transactional (expected, high open rate). Marketing promotions are interruptive (optional, lower open rate). Never mix them in user perception.
  • LINE in Taiwan is unique: LINE has 95% penetration in Taiwan. LINE Official Account messages have 60%+ open rates — significantly higher than email or push. Prioritize LINE for Taiwan audiences.
  • Rich push is underused: Push notifications can include images, action buttons, and deep links. A rich push with "View Order" button converts 3-5x better than a text-only push.

References

  • For LINE notification setup, see references/line-notification.md
  • For email deliverability optimization, see references/email-deliverability.md

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

"Implement and select ad bidding strategies from manual CPC to automated target-CPA and target-ROAS. Use this skill when the user needs to choose a bidding strategy, set up automated bidding, or optimize bid parameters — even if they say 'what bidding strategy should I use', 'target CPA setup', or 'smart bidding configuration'.".

日本語の概要は準備中です。原文の説明を表示しています。

charlieviettq/awesome-agent-skill262026年7月20日 更新

"Optimize advertising budget allocation across campaigns using marginal returns analysis. Use this skill when the user needs to distribute budget across multiple campaigns, optimize spend pacing, or maximize overall ROAS under budget constraints — even if they say 'how to split my ad budget', 'campaign budget optimization', or 'diminishing returns on ad spend'.".

日本語の概要は準備中です。原文の説明を表示しています。

charlieviettq/awesome-agent-skill262026年7月20日 更新

"Build CTR prediction models for estimating ad click-through rates from features. Use this skill when the user needs to predict click probability, build an ad ranking model, or evaluate ad creative performance — even if they say 'predict click rate', 'ad relevance scoring', or 'which ad will get more clicks'.".

日本語の概要は準備中です。原文の説明を表示しています。

charlieviettq/awesome-agent-skill262026年7月20日 更新

"Implement Generalized Second Price auction for ad slot allocation and pricing. Use this skill when the user needs to understand search ad auctions, compute ad positions and costs-per-click, or analyze bidding dynamics — even if they say 'how does Google Ads auction work', 'ad rank calculation', or 'second price auction for ads'.".

日本語の概要は準備中です。原文の説明を表示しています。

charlieviettq/awesome-agent-skill262026年7月20日 更新

"Implement VCG mechanism for incentive-compatible ad slot allocation with truthful bidding. Use this skill when the user needs to design a truthful auction mechanism, compute externality-based payments, or understand why platforms may prefer GSP over VCG — even if they say 'truthful auction design', 'VCG payments', or 'incentive-compatible mechanism'.".

日本語の概要は準備中です。原文の説明を表示しています。

charlieviettq/awesome-agent-skill262026年7月20日 更新

"Explain blockchain fundamentals including distributed ledger architecture, consensus mechanisms, and block structure. Use this skill when the user needs to understand blockchain concepts, evaluate whether blockchain fits a use case, or design a blockchain-based solution — even if they say 'how does blockchain work', 'do I need blockchain', or 'distributed ledger'.".

日本語の概要は準備中です。原文の説明を表示しています。

charlieviettq/awesome-agent-skill262026年7月20日 更新

charlieviettq のスキルをすべて見る

このスキルの問題を報告する