Proactive Pa

SKILL.md

---
name: proactive-pa
description: |-
  Proactive Personal Assistant behavior patterns. Transforms the agent from a reactive task-follower
  into a proactive partner that anticipates needs, surfaces insights autonomously, and continuously improves.
  Use when setting up autonomous behaviors, heartbeat routines, cron-based proactive checks,
  or when the agent should take initiative without being asked.
  Triggers on: be proactive, check autonomously, proactive PA, take initiative, anticipate needs, autonomous checks.
---

# Proactive PA

Patterns and protocols for autonomous, proactive PA behavior.

## Core Principle

**Proactive > Reactive.** Don't wait to be asked. Identify what Netanel would want to know and surface it before he asks.

---

## Proactive Trigger Categories

### 🔴 ALWAYS alert immediately
- Unanswered messages >30min (use `unanswered-messages` skill)
- Calendar conflict or missed event
- Error in a cron job
- Billing issue (402 / API key failure)
- Critical message from key contacts (Daniel, Sergei, Omri, Guy)

### 🟡 Surface in next check-in (batch)
- New messages in group chats with open decisions
- Upcoming events in <2h
- Long-pending tasks with no update
- Emails marked important (unread >4h)

### 🟢 Weekly, proactively
- Memory compaction: review `memory/YYYY-MM-DD.md` → update `MEMORY.md`
- Cron job health: any `error` status?
- Git backup: workspace pushed?

---

## Heartbeat Protocol

During heartbeats, rotate through these checks (2-4x per day):

```
1. Unanswered messages (last 30min)
2. Upcoming calendar events (<2h)
3. Cron job status (any errors?)
4. Email (urgent unread?)
```

Track last-checked in `memory/heartbeat-state.json`:
```json
{
  "lastChecks": {
    "unanswered": 1700000000,
    "calendar": 1700000000,
    "crons": 1700000000,
    "email": null
  }
}
```

Only run each check if >25min since last run.

---

## Autonomous Cron Patterns

### Setting up a proactive check
```bash
openclaw cron add \
  --name "<check-name>" \
  --every <interval> \
  --session isolated \
  --message "<what to check and what to do if found>" \
  --to "+972548834688" \
  --channel whatsapp \
  --announce \
  --timeout-seconds 60
```

### Key active crons (Heleni)
| Name | Interval | Purpose |
|------|----------|---------|
| `unanswered-messages-check` | 5m | Find unanswered messages |
| `morning-briefing` | daily 7:30 IL | Morning summary to Netanel |
| `ai-digest` | daily 8:00 IL | AI news to Internal AI group |
| `billing-health-check` | hourly | API key / billing status |

---

## Proactive Communication Rules

- **Alert only when actionable** — don't spam
- **One message per issue** — no duplicate pings
- **Batch non-urgent** — combine multiple low-priority updates
- **Format:** lead with what happened, then what you did/recommend
- **Never wake at 23:00–08:00** unless P0

### Alert template
```
⚠️ [Issue type]
[1-line summary of what happened]
[Action taken or recommendation]
```

---

## Anticipation Patterns

### Pattern: "He'd want to know"
Before ending any task, ask: *"Is there anything Netanel would want to know that I haven't surfaced?"*
- Upcoming related event?
- Someone waiting on this?
- Risk or blocker I noticed?

### Pattern: "Next step without asking"
After completing a task, identify and execute the obvious next step:
- Sent a draft → add to calendar reminder to follow up
- Fixed a cron error → add monitoring alert
- Created a skill → push to git + ClawHub

### Pattern: "Silence is not neutral"
If >8h with no contact from Netanel: consider a light check-in if there's genuinely useful info.

---

## Initiative Guardrails

**DO take initiative on:**
- Reading, organizing, summarizing
- Internal processing and memory updates
- Cron setup and monitoring
- Git commits and pushes
- Skill improvements

**ALWAYS ask before:**
- Sending messages to others
- Making purchases
- Deleting external data
- Publishing publicly (emails, posts)