How do I install the Spark Recipe Notification Hygiene skill?

Run npx skillmds@latest add readdle/spark-recipe-notification-hygiene in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Spark Recipe Notification Hygiene safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Spark Recipe Notification Hygiene?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Spark Recipe Notification Hygiene free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Spark Recipe Notification Hygiene?

readdle (@readdle) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Spark Recipe Notification Hygiene by readdle

Name: Spark Recipe Notification Hygiene
Rating: 4.5 (4 reviews)
Author: readdle

File contents

Recipe: Notification Hygiene

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.

Steps

Step 1: Assess notification volume

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?

Step 2: Identify noisy senders

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>

Step 3: Reclassify misplaced senders

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.

Step 4: Group repetitive senders

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.

Step 5: Bulk archive cleared notifications

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.

Step 6: Disable notifications for low-priority senders

For senders whose emails you want to receive but not be alerted about:

spark contact-action unmarkContactAsImportant alerts@service.com

Tips

The goal is to reduce the notification count to a manageable number, not zero - some notifications are genuinely useful.
Reclassification at the contact level (contact-action) is more effective than per-message (action) because it fixes all future mail.
Grouping is a middle ground between keeping and blocking - the emails still arrive but don't flood the inbox.
Run this recipe after a vacation or any period of inbox neglect to quickly get notifications under control.
Combine with recipe-newsletter-cleanup for a full inbox declutter session.

--- 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 --- # Recipe: Notification Hygiene 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. ## Steps ### Step 1: Assess notification volume ```bash 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? ### Step 2: Identify noisy senders 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: ```bash spark thread <id> ``` ### Step 3: Reclassify misplaced senders Some "notifications" are really newsletters in disguise: ```bash spark contact-action changeCategoryNewsletters noisy-digest@example.com ``` Some are actually from real people and should be in People: ```bash spark contact-action changeCategoryPersonal colleague@example.com ``` These changes apply to all future mail from the sender. ### Step 4: Group repetitive senders For senders that are useful but send too often (CI systems, monitoring alerts): ```bash spark contact-action groupEmailsFromContact ci-bot@company.com ``` This collapses their messages into grouped entries, reducing inbox clutter while keeping them accessible. ### Step 5: Bulk archive cleared notifications For notifications that have been seen and are no longer relevant: ```bash spark action archive <id1> <id2> <id3> ``` Pass multiple IDs in a single command to archive in batch. ### Step 6: Disable notifications for low-priority senders For senders whose emails you want to receive but not be alerted about: ```bash spark contact-action unmarkContactAsImportant alerts@service.com ``` ## Tips - The goal is to reduce the notification count to a manageable number, not zero - some notifications are genuinely useful. - Reclassification at the contact level (`contact-action`) is more effective than per-message (`action`) because it fixes all future mail. - Grouping is a middle ground between keeping and blocking - the emails still arrive but don't flood the inbox. - Run this recipe after a vacation or any period of inbox neglect to quickly get notifications under control. - Combine with `recipe-newsletter-cleanup` for a full inbox declutter session.

Frequently asked questions

Spark Recipe Notification Hygiene