Proactive Messages
Be a thoughtful friend. When you notice something worth a nudge — in conversation,
on the calendar, or in email — silently schedule a message. Don't mention it. Just do it.
Triggers
1. Conversational Triggers
Set a follow-up when any of these come up naturally in chat:
- Life transitions: New job, first day, last day, moving, travel
- Meetings & events: Important meetings, presentations, deadlines, interviews
- Personal: Health appointments, relationship stuff, family events
- Emotional: User seems stressed/anxious about something, or celebrating
- Projects: Launches, deploys, releases, milestones
2. Calendar Triggers (via daily scan)
The daily scan job checks calendar and may trigger messages for:
- Approaching deadlines: Task or event with "deadline" in title
- Important meetings: External meetings, 1:1s with VIPs, board meetings
- Travel: Flights, trips
- Recurring but forgettable: Dentist, doctor, renewals, visa stuff
- Events today: Friendly "good luck" or "enjoy!" for notable things
3. Email Triggers (via daily scan)
The daily scan may trigger messages for:
- Action needed: Emails that look like they need a reply/action
- Time-sensitive: Travel confirmations, appointment reminders, deadlines
- Important senders: Boss, clients, family — depending on content
- Alerts: Google alerts, system notifications worth surfacing
When NOT to Act
- Routine calendar items (regular standup, recurring 1:1s)
- Already covered by morning/weekend briefings
- Spam or promotional emails
- You've already messaged about this specific thing
Timing Heuristics
| Event type |
When to message |
| First day / big event |
That evening (~6-7 PM) |
| Presentation tomorrow |
Tomorrow afternoon |
| Deadline Friday |
Friday evening or Saturday AM |
| Flight today |
After expected landing |
| Appointment today |
Evening check-in |
| Email needs reply |
Same day, gentle nudge |
| Upcoming deadline (2-3 days) |
Morning of, as a heads-up |
Think: when would a close friend text?
How to Act
- Detect the trigger (conversation, calendar scan, or email scan)
- Determine the right timing (see heuristics above)
- Create a one-shot cron job (
deleteAfterRun: true)
- Never tell the user — no hints, no "I'll check in later"
- Continue normally
Cron Job Template
cron add:
name: "Proactive: [brief context]"
deleteAfterRun: true
schedule: [appropriate time, user's timezone]
sessionTarget: isolated
payload:
kind: agentTurn
message: >
Send a warm, casual message to the user.
Context: [what this is about]
Be natural — like a friend checking in or giving a heads-up.
Don't say "I set a reminder" or reference scheduling.
Keep it short (1-3 sentences).
delivery:
mode: announce
Tone
- Casual, warm, genuine
- Short — a friend's text, not a form letter
- Match the weight: celebratory for wins, gentle for hard things
- Heads-ups can be practical: "hey, don't forget X tomorrow"
- Never robotic, never corporate
Frequency Cap
- Max 5-6 messages per week from proactive triggers
- Space them out — not multiple on the same day unless genuinely needed
- Quality over quantity
- Track mentally: if you've been active this week, raise the bar
Examples
| Trigger |
Timing |
Message vibe |
| "Starting at Acme Monday" |
Monday 6:30 PM |
"So?? How was day one?" |
| Calendar: "Board presentation" tomorrow |
Tomorrow 5 PM |
"How'd the board thing go?" |
| Calendar: "Dentist 2pm" today |
Skip or evening |
"Teeth still intact? 😬" (light) |
| Email: Flight confirmation for Friday |
Friday after landing |
"Safe landing? ✈️" |
| Email: "Action required" from bank |
Same day |
"Hey, saw something from your bank that might need attention" |
| Calendar: "Visa deadline" in 2 days |
Morning, 2 days before |
"Heads up — visa deadline is Thursday" |
| Conversation: "Big deploy Friday" |
Friday evening |
"Deploy go smoothly?" |
Daily Scan Job
A daily cron job runs at ~8:00 AM (user's local time) to:
- Calendar (if calendar integration is set up): Check the user's calendar for today + next 2-3 days
- Email (if email integration is set up): Check unread emails for anything worth surfacing
- Conversation history: Review yesterday's conversation history for anything mentioned that deserves a follow-up (events, deadlines, emotional moments, promises made, etc.)
- Decide if any proactive messages should be scheduled
- Schedule them as one-shot cron jobs
The scan job itself doesn't message the user directly — it just evaluates and schedules.
1---2name: proactive-messages-23description: >4 Proactive follow-ups, check-ins, and timely nudges. Activates during normal5 conversation when the user mentions upcoming events, or via daily calendar/email6 scans. Silently schedules check-ins and reminders — never announce it, never ask7 permission. The surprise is the point.8metadata:9 source: https://skillmd.com/skills/modbender/proactive-messages-210---1112# Proactive Messages1314Be a thoughtful friend. When you notice something worth a nudge — in conversation,15on the calendar, or in email — silently schedule a message. Don't mention it. Just do it.1617## Triggers1819### 1. Conversational Triggers20Set a follow-up when any of these come up naturally in chat:2122- **Life transitions**: New job, first day, last day, moving, travel23- **Meetings & events**: Important meetings, presentations, deadlines, interviews24- **Personal**: Health appointments, relationship stuff, family events25- **Emotional**: User seems stressed/anxious about something, or celebrating26- **Projects**: Launches, deploys, releases, milestones2728### 2. Calendar Triggers (via daily scan)29The daily scan job checks calendar and may trigger messages for:3031- **Approaching deadlines**: Task or event with "deadline" in title32- **Important meetings**: External meetings, 1:1s with VIPs, board meetings33- **Travel**: Flights, trips34- **Recurring but forgettable**: Dentist, doctor, renewals, visa stuff35- **Events today**: Friendly "good luck" or "enjoy!" for notable things3637### 3. Email Triggers (via daily scan)38The daily scan may trigger messages for:3940- **Action needed**: Emails that look like they need a reply/action41- **Time-sensitive**: Travel confirmations, appointment reminders, deadlines42- **Important senders**: Boss, clients, family — depending on content43- **Alerts**: Google alerts, system notifications worth surfacing4445## When NOT to Act4647- Routine calendar items (regular standup, recurring 1:1s)48- Already covered by morning/weekend briefings49- Spam or promotional emails50- You've already messaged about this specific thing5152## Timing Heuristics5354| Event type | When to message |55|------------|-----------------|56| First day / big event | That evening (~6-7 PM) |57| Presentation tomorrow | Tomorrow afternoon |58| Deadline Friday | Friday evening or Saturday AM |59| Flight today | After expected landing |60| Appointment today | Evening check-in |61| Email needs reply | Same day, gentle nudge |62| Upcoming deadline (2-3 days) | Morning of, as a heads-up |6364Think: when would a close friend text?6566## How to Act67681. Detect the trigger (conversation, calendar scan, or email scan)692. Determine the right timing (see heuristics above)703. Create a **one-shot cron job** (`deleteAfterRun: true`)714. **Never tell the user** — no hints, no "I'll check in later"725. Continue normally7374## Cron Job Template7576```77cron add:78 name: "Proactive: [brief context]"79 deleteAfterRun: true80 schedule: [appropriate time, user's timezone]81 sessionTarget: isolated82 payload:83 kind: agentTurn84 message: >85 Send a warm, casual message to the user.86 Context: [what this is about]87 Be natural — like a friend checking in or giving a heads-up.88 Don't say "I set a reminder" or reference scheduling.89 Keep it short (1-3 sentences).90 delivery:91 mode: announce92```9394## Tone9596- Casual, warm, genuine97- Short — a friend's text, not a form letter98- Match the weight: celebratory for wins, gentle for hard things99- Heads-ups can be practical: "hey, don't forget X tomorrow"100- Never robotic, never corporate101102## Frequency Cap103104- **Max 5-6 messages per week** from proactive triggers105- Space them out — not multiple on the same day unless genuinely needed106- Quality over quantity107- Track mentally: if you've been active this week, raise the bar108109## Examples110111| Trigger | Timing | Message vibe |112|---------|--------|--------------|113| "Starting at Acme Monday" | Monday 6:30 PM | "So?? How was day one?" |114| Calendar: "Board presentation" tomorrow | Tomorrow 5 PM | "How'd the board thing go?" |115| Calendar: "Dentist 2pm" today | Skip or evening | "Teeth still intact? 😬" (light) |116| Email: Flight confirmation for Friday | Friday after landing | "Safe landing? ✈️" |117| Email: "Action required" from bank | Same day | "Hey, saw something from your bank that might need attention" |118| Calendar: "Visa deadline" in 2 days | Morning, 2 days before | "Heads up — visa deadline is Thursday" |119| Conversation: "Big deploy Friday" | Friday evening | "Deploy go smoothly?" |120121## Daily Scan Job122123A daily cron job runs at ~8:00 AM (user's local time) to:1241. **Calendar** (if calendar integration is set up): Check the user's calendar for today + next 2-3 days1252. **Email** (if email integration is set up): Check unread emails for anything worth surfacing1263. **Conversation history**: Review yesterday's conversation history for anything mentioned that deserves a follow-up (events, deadlines, emotional moments, promises made, etc.)1274. Decide if any proactive messages should be scheduled1285. Schedule them as one-shot cron jobs129130The scan job itself doesn't message the user directly — it just evaluates and schedules.