← Back to list

missive-inbox-triage
by jjeremycai
⭐ 0🍴 0📅 Jan 20, 2026
SKILL.md
name: missive-inbox-triage description: This skill should be used when the user asks to "triage my inbox", "prioritize emails", "what needs my attention", "sort through my messages", "help me process my inbox", or is reviewing conversations to determine what needs action in Missive.
Core Principles
Decide, Don't Defer
Every conversation should get a decision: respond, delegate, schedule, archive, or delete. Avoid "I'll deal with this later" piles.
Urgency vs Importance
- Urgent + Important: Handle immediately
- Important, not urgent: Schedule time for it
- Urgent, not important: Delegate or quick response
- Neither: Archive or delete
Time-Based Triage
For regular inbox processing, work through conversations newest-to-oldest. For catch-up after absence, oldest-to-newest.
Triage Decision Framework
1. Can I Delete/Archive This?
- Spam → Delete
- Newsletter I don't read → Unsubscribe or delete
- FYI with no action needed → Archive
- Completed thread → Archive/close
2. Does This Need a Response?
- Direct question to me → Yes
- Request for me → Yes
- CC'd for awareness only → Probably not
- Auto-notification → No
3. Can I Respond in 2 Minutes?
- Yes → Do it now (or draft it)
- No → Schedule dedicated time
4. Am I the Right Person?
- Yes → Process it
- No → Delegate/forward with context
Identifying Priority Conversations
High Priority Indicators
- From VIPs (executives, key clients, important contacts)
- Time-sensitive language ("urgent", "ASAP", "by EOD", "deadline")
- Blockers (someone waiting on you to proceed)
- Revenue/customer impact
- Escalations
Medium Priority Indicators
- Direct requests with reasonable timelines
- Follow-ups on ongoing work
- Meeting requests
- Questions requiring research
Low Priority Indicators
- FYI/informational
- Newsletters you actually read
- Non-urgent internal updates
- Social/networking messages
Triage Workflow
Quick Scan Phase
- Fetch recent conversations:
missive_conversationsaction:list - Scan subjects and senders for high-priority flags
- Identify spam/obvious archives first
Decision Phase
For each conversation:
- Read enough to understand what's needed
- Classify: Archive, Respond, Delegate, Schedule, or Task
- Take action or note the decision
Action Phase
- Archive: Close the conversation
- Respond: Draft reply (use draft-reply skill)
- Delegate: Assign to appropriate team member
- Schedule: Create task with due date
- Task: Add to task list for follow-up
Skip/Archive Criteria
Automatically skip or archive:
- Marketing emails - Promotional content, sales pitches
- Newsletters - Unless explicitly wanted
- Automated notifications - System alerts with no action needed
- Social media notifications - LinkedIn, Twitter, etc.
- Completed transactions - Order confirmations, receipts (archive, don't delete)
- Calendar confirmations - Meeting accepted/declined notifications
Batch Processing Strategies
The 4 D's
- Delete: Trash it
- Do: Handle it now (< 2 min)
- Delegate: Assign to someone else
- Defer: Schedule for later
Touch It Once
Avoid re-reading the same email multiple times. Make a decision on first read when possible.
Time Boxing
Set a fixed time for triage (e.g., 15 min morning, 15 min afternoon). Process what you can, then stop.
Using Missive Features for Triage
Conversation Status
- Open/Close conversations as you process
- Use closed status to indicate "handled"
Assignments
- Assign to self = "I own this"
- Assign to others = delegation
- Use
missive_conversationsto check assignee
Tasks
- Create tasks for follow-ups:
missive_tasksaction:create - Include due dates for time-sensitive items
- Link tasks to conversations
Score
Total Score
50/100
Based on repository quality metrics
✓SKILL.md
SKILL.mdファイルが含まれている
+20
○LICENSE
ライセンスが設定されている
0/10
○説明文
100文字以上の説明がある
0/10
○人気
GitHub Stars 100以上
0/15
○最近の活動
3ヶ月以内に更新がある
0/10
○フォーク
10回以上フォークされている
0/5
✓Issue管理
オープンIssueが50未満
+5
✓言語
プログラミング言語が設定されている
+5
○タグ
1つ以上のタグが設定されている
0/5
Reviews
💬
Reviews coming soon