メニュー
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 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-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":["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 spark base skill for tool reference and filter syntax.
Access level required: triage.
emails { "folder": "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:
thread { "message_id": "<id>" }
For mailing lists with an unsubscribe mechanism:
action { "action_name": "unsubscribe", "message_ids": ["<id>"] }
For senders that should be blocked entirely:
contact-action { "action_name": "blockContact", "emails": ["spammer@example.com"] }
To block an entire domain:
contact-action { "action_name": "blockDomain", "emails": ["example.com"] }
For newsletters the user wants to keep but not read in full:
contact-action { "action_name": "enableAutosummaryForContact", "emails": ["newsletter@example.com"] }
For senders that send frequently, group their emails to reduce inbox clutter:
contact-action { "action_name": "groupEmailsFromContact", "emails": ["sender@example.com"] }
emails on Inbox filtered to category:newsletter and a page_size of 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.