name: alfred-fb-message-triage description: > [Alfred] Scan Facebook Messenger for work messages. Generate audit table with every work chat, summary, Alfred decision, and status. Every message gets a closed status. Use when: "check Messenger", "FB messages", "what's in my Messenger", "Messenger triage". allowed-tools: Read, Write, Edit, Glob, Grep, Bash(git:, pnpm:), mcp__claude-in-chrome__*
Alfred FB Message Triage
Scope: Last 20 conversations Goal: Every conversation audited with a status. Master sees the full picture.
Before Processing
Read these files:
agents/agent-alfred/context/MASTER_PREFERENCES.mdagents/agent-alfred/context/TEAM.md— Delegation rules
Status Definitions
Every conversation gets exactly ONE status:
| Status | Meaning | Master Action |
|---|---|---|
ACTION_NEEDED |
Requires Master response/decision | Yes |
DELEGATED |
Assigned to team member | No |
REPLIED |
Ball in their court | No |
NOTED |
FYI only | No |
SKIPPED |
Personal, not work | No |
When unsure: ACTION_NEEDED (Master decides).
Process
1. Access Facebook Messages
Use facebook.com/messages (NOT messenger.com)
- Navigate to
facebook.com/messages - If login required, ask Master to authenticate
- Confirm chat list visible in the left sidebar
- Check "Message Requests" folder for non-friend messages
Why facebook.com instead of messenger.com:
- facebook.com shows more message history for E2E encrypted chats
- Better sidebar previews with actual message content
- Same chat list, but more content visible when clicking into conversations
2. Scan Last 20 Conversations
CRITICAL: Click into EVERY conversation to read full message content.
Sidebar previews are often truncated or show "Messages and calls are secured..." which hides the actual content. You MUST click into each chat to see the real messages.
For each conversation:
- Click on the conversation to open it
- Read the actual message content in the chat panel
- Scroll up in the conversation if needed to see recent context
- Note: chat name, last activity time, key message content, who sent the last message
- Classify as WORK or PERSONAL based on full context
- For work chats: determine status based on message content
- Personal chats → SKIPPED (note as personal, move to next)
- Scroll down in the chat list to reveal more conversations as needed
E2E Encryption handling:
- Many chats show "End-to-end encrypted" badge
- Despite the badge, facebook.com usually shows recent message content
- If "Messages are missing" appears, note what IS visible and classify based on that
- Check sidebar preview as backup - it often shows the last message even for encrypted chats
3. Classification Logic
| Pattern | Status |
|---|---|
| Direct question to Master | ACTION_NEEDED |
| Waiting for Master's decision | ACTION_NEEDED |
| Investment/deal inquiry | ACTION_NEEDED |
| Master already replied, waiting on them | REPLIED |
| FYI update, no question | NOTED |
| Team member's domain (per TEAM.md) | DELEGATED |
| Personal/family/social | SKIPPED |
4. Write Report
Output: agents/agent-alfred/outputs/YYYY-MM-DD-HHmm-fb-message-triage.md
Use local time for HHmm timestamp.
# FB Message Triage — YYYY-MM-DD HH:mm
**Conversations scanned:** 20
## Summary
| Status | Count |
|--------|-------|
| ACTION_NEEDED | X |
| DELEGATED | X |
| REPLIED | X |
| NOTED | X |
| SKIPPED | X |
## Master Action Items
| # | Chat | Topic | Suggested Action |
|---|------|-------|------------------|
## Full Audit Table
| # | Chat | Last Activity | Summary | Alfred's Action | Master Action |
|---|------|---------------|---------|-----------------|---------------|
## Master Feedback
> [Fill after review]
Success Criteria
- 20 conversations scanned
- Full Audit Table with all 20 conversations
- Every conversation has exactly one status
- Alfred's Action column filled for every row
- Output written with correct local timestamp