/gog-email-triage

name: gog-email-triage
description: Triage and prioritize inbox emails. Summarize unread messages, classify by urgency and category, propose actions (reply, archive, schedule, create task). Use when user wants to review inbox, process unread emails, or needs help prioritizing messages. Outputs structured summary with top priorities and suggested next actions.
compatibility: Requires gog CLI tool with email access
metadata:
  author: gog-skills
  version: "1.0"
allowed-tools: Bash(gog:*) Read

Email Triage & Prioritization

Efficiently review and prioritize your inbox by classifying emails and suggesting actions.

When to Use

Use this skill when:

• User wants to "review my inbox" or "check my email"
• User asks to "triage emails" or "prioritize messages"
• User mentions "what's urgent" or "what needs my attention"
• User wants help deciding what to do with emails
• At the start of workday for inbox review

**Important**: This skill is READ-ONLY. It analyzes and proposes actions but NEVER sends, archives, or modifies emails.

Dynamic Context

The following live data is available:

**Unread emails:**

!`gog gmail search "is:unread" --max 25 --json 2>/dev/null || echo "GOG_NOT_CONFIGURED"`

Inputs You Need

Before triaging: 1. **User preferences** (ask if not known):

• Categories of interest (work vs personal filter)
• Urgency threshold (show only high/urgent, or include all)
• Any auto-archive patterns (newsletters, notifications)

2. **Context clues** (extract from conversation):

• Current projects or priorities
• Upcoming deadlines
• People user is waiting to hear from

Workflow

Step 1: Fetch Unread Emails

If dynamic context shows `GOG_NOT_CONFIGURED`:

• Inform user that GOG is not configured
• Point to: `skills/gog/_shared/references/gog-interface.md`
• Offer to help with configuration
• STOP here until configured

If email list is empty:

• Inform user: "No unread emails! Inbox Zero achieved."
• Ask if they want to review recent emails instead
• If yes, fetch: `gog gmail search "is:inbox" --max 25 --json`

Step 2: Analyze Each Email

For each email, determine:

**Urgency Level:**

• **urgent**: Immediate attention required (< 2 hours)
• Keywords: "urgent", "ASAP", "immediately", "emergency"
• From: Boss, critical clients, system alerts
• Context: Blocking your work or others
• **high**: Should respond today
• Action required by EOD
• Meeting invitations for soon
• Client/stakeholder requests
• **medium**: Can respond within 2-3 days
• FYI with potential follow-up
• Non-urgent requests
• Team updates that may need input
• **low**: No time pressure
• Newsletters, automated reports
• Social correspondence
• Informational only

**Category:**

• **action-required**: Needs a decision or action from you
• **fyi**: Informational only, no action needed
• **meeting**: Meeting invitation or scheduling
• **social**: Personal correspondence
• **newsletter**: Automated newsletters/updates
• **spam**: Likely spam or unwanted

**Suggested Action:**

• **reply**: Draft a reply (use gog-email-draft skill)
• **reply-all**: Draft reply-all
• **forward**: Forward to someone else
• **archive**: No action needed, remove from inbox
• **create-task**: Convert to task (use gog-tasks skill)
• **schedule-meeting**: Set up meeting (use gog-calendar skill)
• **block-sender**: Mark as spam/block
• **delete**: Junk, delete immediately

Step 3: Generate Triage Summary

Output in this format:

# Email Triage Summary

📧 **Total Unread**: [N] messages
⚠️  **Urgent**: [N] | 🔴 **High**: [N] | 🟡 **Medium**: [N] | 🟢 **Low**: [N]

## Top 3 Priorities

1. **[Subject]** from [Sender]
   - Urgency: [urgent/high/medium/low]
   - Reason: [1-line rationale]
   - Suggested action: [action]

2. [...]

3. [...]

## All Messages

| ID (last 6) | From | Subject (truncated) | Urgency | Category | Action | Rationale |
|-------------|------|---------------------|---------|----------|--------|-----------|
| abc123 | sender@example.com | Meeting tomorrow? | high | meeting | reply | Needs response by EOD |
| def456 | newsletter@... | Weekly update | low | newsletter | archive | FYI only |
| [...] | [...] | [...] | [...] | [...] | [...] | [...] |

## Suggested Next Actions

- [ ] **Reply to [N] urgent/high priority emails** (IDs: abc123, def456)
- [ ] **Create tasks for [N] action items** (IDs: ghi789)
- [ ] **Schedule meeting for [topic]** (ID: jkl012)
- [ ] **Archive [N] newsletters and FYI messages**
- [ ] **Block [N] spam senders**

---

**Next Steps**:
- To draft a reply: "Draft a reply to [email ID or subject]"
- To create task: "Create a task for [email ID or subject]"
- To schedule meeting: "Schedule meeting about [topic]"
- To see email content: "Show me email [ID]"

Step 4: Save HTML Artifact

Read the template at `.claude/templates/html/custom/email-triage.html`, fill all `{{PLACEHOLDER}}` values with the data from Step 3 (email counts, priority groups, suggested actions), and save the completed HTML to `workspace/daily-logs/[C] YYYY-MM-DD-email-triage.html`.

Create the `workspace/daily-logs/` directory if it does not exist.

Step 5: Offer Follow-Up

After presenting the triage:

• Ask: "Which email would you like to tackle first?"
• Or: "Would you like me to draft replies for the top priorities?"
• Or: "Should I create tasks for the action items?"

**Do NOT** proceed to take actions without user confirmation.

Output Format (Strict)

The triage summary MUST include:

1. **Header stats**: Total count + urgency breakdown 2. **Top 3 priorities**: Most urgent/important emails with rationale 3. **Complete table**: All emails with classifications 4. **Suggested next actions**: Checklist of proposed actions grouped by type 5. **Next steps prompt**: Clear options for follow-up

**Table columns** (in order): 1. ID (last 6 chars) - for reference 2. From - sender email or name 3. Subject (truncated to ~40 chars) 4. Urgency - urgent/