50 lines
1.7 KiB
Markdown
50 lines
1.7 KiB
Markdown
---
|
|
name: inbox-triage
|
|
description: Triage inbound messages by urgency and importance, summarize what needs attention, and propose concise reply options. Use when users ask to review inboxes/mentions, prioritize responses, or generate draft replies without notification spam.
|
|
---
|
|
|
|
# Inbox Triage
|
|
|
|
## Triage goals
|
|
|
|
- Identify messages requiring action soon.
|
|
- Separate urgent from merely unread.
|
|
- Minimize noise while preserving important context.
|
|
|
|
## Priority model
|
|
|
|
Use shared labels from: `skills/_shared/briefing-conventions.md`
|
|
|
|
- **P1 Urgent:** deadline/time-sensitive, blocker, critical personal/work item.
|
|
- **P2 Important:** requires response/decision but not immediate.
|
|
- **P3 Routine:** informational or can wait.
|
|
- **P4 FYI/Archive:** no action needed.
|
|
|
|
## Triage workflow
|
|
|
|
1. Gather recent inbound messages from trusted sources.
|
|
2. Deduplicate threads/conversations.
|
|
3. Assign priority with one-line reason.
|
|
4. Extract explicit asks, deadlines, and blockers.
|
|
5. Produce compact summary and suggested response plan.
|
|
|
|
## Reply drafting rules
|
|
|
|
- Draft only for P1/P2 by default.
|
|
- Keep tone aligned with user preference (warm/direct).
|
|
- Provide 1-2 short reply options; do not auto-send unless asked.
|
|
|
|
## Output template
|
|
|
|
- **Urgent now (P1):** item -> why urgent -> suggested action
|
|
- **Important next (P2):** item -> needed decision/response
|
|
- **Can wait (P3/P4):** compact grouped bullets
|
|
- **Suggested replies:** short drafts for top items
|
|
- **Next actions (1-3):** practical sequence
|
|
|
|
## Noise controls
|
|
|
|
- Avoid re-reporting unchanged low-priority items repeatedly.
|
|
- Batch updates when multiple messages arrive close together.
|
|
- If nothing important changed, explicitly say inbox is stable.
|