القائمة
Audit newsletter subscriptions: block unwanted senders, unsubscribe from mailing lists, and enable AI summaries for worth-keeping ones.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
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-newsletter-cleanup |
| description | Audit newsletter subscriptions: block unwanted senders, unsubscribe from mailing lists, and enable AI summaries for worth-keeping ones. |
| metadata | {"version":"1.0.0","requires":{"skills":["use-spark"],"accessLevel":"triage"}} |
Audit and prune newsletter subscriptions. Block the unwanted, unsubscribe from the noisy, and enable AI summaries for the ones worth keeping.
Prerequisite: Read the use-spark base skill for command reference and filter syntax.
Access level required: triage.
spark emails Inbox --filter "category:newsletter"
Review the senders. Look for patterns: senders the user never reads, duplicates, or obsolete subscriptions.
For each sender the user wants to evaluate:
spark thread <id>
For mailing lists with an unsubscribe mechanism:
spark action unsubscribe <id>
For senders that should be blocked entirely:
spark contact-action blockContact spammer@example.com
To block an entire domain:
spark contact-action blockDomain example.com
For newsletters the user wants to keep but not read in full:
spark contact-action enableAutosummaryForContact newsletter@example.com
For senders that send frequently, group their emails to reduce inbox clutter:
spark contact-action groupEmailsFromContact sender@example.com
spark emails Inbox --filter "category:newsletter" --page-size 50 to see a broad list of senders.unsubscribe works through the mailing list's unsubscribe mechanism - it's cleaner than blocking.blockContact stops all future mail from appearing; blockDomain is more aggressive.groupEmailsFromContact) collapses repeated messages from the same sender into a single entry.