spark-recipe-notification-hygiene

Reclassify noisy senders, group repetitive alerts, and archive cleared notifications.

136|6|Updated Apr 22, 2026
One-click install
npx skills add https://github.com/readdle/spark-cli-skills --skill spark-recipe-notification-hygiene
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spark-recipe-notification-hygiene
Source: https://github.com/readdle/spark-cli-skills/tree/main/skills/recipe-notification-hygiene
Command: npx skills add https://github.com/readdle/spark-cli-skills --skill spark-recipe-notification-hygiene

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires use-spark.

What problem does it solve?

Notification hygiene reduces inbox clutter and cognitive overload by reclassifying noisy senders, grouping repetitive alerts, and archiving alerts that are no longer relevant.

Core Features & Use Cases

  • Noisy-sender discovery: Assess unread notification volume and identify dominant sender patterns so you can target the right sources.
  • Sender-level reclassification: Move misplaced “notifications” into the correct category (e.g., newsletters vs. personal) so future messages are handled appropriately.
  • Repetitive notification grouping & cleanup: Group high-frequency senders and bulk-archive cleared notification messages to keep the inbox actionable.
  • Access-controlled execution: Runs under the required triage access level to ensure safe, permission-aware changes.

Quick Start

Run the recipe to identify noisy notification senders, reclassify them at the contact level, group repetitive notifications, and archive cleared alerts in a single hygiene pass.

Frequently Asked Questions about spark-recipe-notification-hygiene

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I reduce email notification overload and archive repetitive alerts?▼

Yes, you can reclassify senders by moving misplaced notification messages into the correct category, such as newsletters, so future emails from that contact are handled appropriately.

Do I need the Spark CLI to group repetitive notifications and clean my inbox?▼

Notification hygiene runs under the triage access level, which ensures safe, permission-aware changes when reclassifying senders and archiving cleared notification messages.

How do I discover which senders are causing the most unread notification clutter?▼

After sender reclassification and repetitive notification grouping, cleared notification messages are bulk-archived in a single hygiene pass to remove clutter and reduce cognitive overload.

What is the best way to batch archive cleared notification emails?▼

Repetitive notification grouping identifies high-frequency senders so you can target them for batch archiving, preventing future inbox clutter from dominant alert sources.

Can I fix misclassified notification senders so they sort correctly in the future?▼

Notification hygiene targets unread notification category messages where volume is high, applying contact-level category hygiene and batch cleanup to tame the overload.