Menu
Process inbox to zero using category-first triage: review by category, read threads, then archive, move, or mark done.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use the Spark MCP extension to access and act on the user's Spark email data - list emails, search by topic, read threads, check calendar events, find availability, look up contacts, view team info, draft messages (from scratch or saved templates), send drafts, share drafts with teammates, post team comments, triage threads, create/update/delete calendar events and manage attendees, and manage contacts. Use when the user asks about their emails, calendar, contacts, meetings, scheduling, or wants to send, reply, archive, snooze, assign, comment, categorize, or schedule.
Executive assistant persona for Spark. Morning briefings, draft replies, schedule management, and contact lookup.
Founder / CEO persona for Spark. High-volume triage, aggressive delegation, cross-team oversight, and selective engagement.
Freelancer / solo operator persona for Spark. Multi-client management, invoice follow-ups, availability, and quick responses.
Meeting manager persona for Spark. Meeting preparation, transcript review, follow-up drafts, and scheduling.
Project manager persona for Spark. Project thread tracking, stakeholder updates, action item extraction, and cross-team coordination.
| name | spark-recipe-inbox-zero |
| description | Process inbox to zero using category-first triage: review by category, read threads, then archive, move, or mark done. |
| metadata | {"version":"1.0.0","requires":{"skills":["spark"],"accessLevel":"triage"}} |
Process the inbox to zero using category-first triage. Work through categories in priority order, then take action on each email.
Prerequisite: Read the spark base skill for tool reference and filter syntax.
Access level required: triage.
Process inbox in priority order:
emails { "folder": "Inbox", "filter": "category:priority is:unread" }
emails { "folder": "Inbox", "filter": "category:personal is:unread" }
emails { "folder": "Inbox", "filter": "category:invitation" }
emails { "folder": "Inbox", "filter": "category:notification is:unread" }
emails { "folder": "Inbox", "filter": "category:newsletter newer_than:7d" }
For emails that need attention, read the thread:
thread { "message_id": "<id>" }
Then decide the action:
Archive - handled or informational, no further action needed:
action { "action_name": "archive", "message_ids": ["<id>"] }
Move to folder - needs filing:
action { "action_name": "moveToFolder", "message_ids": ["<id>"], "folder": "user@example.com:Projects" }
Mark as done - completed/resolved:
action { "action_name": "markAsDone", "message_ids": ["<id>"] }
Pin - important, need to come back to:
action { "action_name": "pin", "message_ids": ["<id>"] }
Snooze - not relevant now, revisit later:
action { "action_name": "snooze", "message_ids": ["<id>"], "date": "2026-04-10" }
Set aside - save for later review:
action { "action_name": "setAside", "message_ids": ["<id>"] }
For categories with many items, batch archive:
action { "action_name": "archive", "message_ids": ["<id1>", "<id2>", "<id3>", "<id4>"] }
emails { "folder": "Inbox", "filter": "is:unread" }
Confirm the inbox is clear or report what's left.
draft with reply_to and then archive - the draft keeps the task alive.contact-action's changeCategory* actions to reclassify all future mail from that sender.