Menu
Tame notification overload by reclassifying noisy senders, grouping repetitive notifications, and bulk-archiving cleared alerts.
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 CLI to access the user's Spark email data - list emails, search by topic, read threads, check calendar events, find availability, look up contacts, and view team info. Use when the user asks about their emails, calendar, contacts, meetings, or scheduling.
Full unsubscribe audit: scan inbox, archive, and GateKeeper for newsletter senders, classify by volume and engagement, detect phishing and duplicate subscriptions, then unsubscribe via spark action or extracted footer links.
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.
| name | spark-recipe-notification-hygiene |
| description | Tame notification overload by reclassifying noisy senders, grouping repetitive notifications, and bulk-archiving cleared alerts. |
| metadata | {"version":"1.0.0","requires":{"skills":["use-spark"],"accessLevel":"triage"}} |
Tame notification overload by identifying noisy senders, reclassifying misplaced mail, grouping repetitive notifications, and clearing out what's no longer relevant.
Prerequisite: Read the use-spark base skill for command reference and filter syntax.
Access level required: triage.
spark emails Inbox --filter "category:notification is:unread"
Count the unread notifications. If the number is high, scan the sender list for patterns - which senders dominate?
Look for senders that generate high-volume, low-value notifications (CI bots, social media alerts, shipping updates after delivery, etc.).
Read a few to confirm they're noise:
spark thread <id>
Some "notifications" are really newsletters in disguise:
spark contact-action changeCategoryNewsletters noisy-digest@example.com
Some are actually from real people and should be in People:
spark contact-action changeCategoryPersonal colleague@example.com
These changes apply to all future mail from the sender.
For senders that are useful but send too often (CI systems, monitoring alerts):
spark contact-action groupEmailsFromContact ci-bot@company.com
This collapses their messages into grouped entries, reducing inbox clutter while keeping them accessible.
For notifications that have been seen and are no longer relevant:
spark action archive <id1> <id2> <id3>
Pass multiple IDs in a single command to archive in batch.
For senders whose emails you want to receive but not be alerted about:
spark contact-action unmarkContactAsImportant alerts@service.com
contact-action) is more effective than per-message (action) because it fixes all future mail.recipe-newsletter-cleanup for a full inbox declutter session.