Menu
Fine-tune Spark's priority category by marking key contacts as primary and adjusting notification importance.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional 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-priority-tuning |
| description | Fine-tune Spark's priority category by marking key contacts as primary and adjusting notification importance. |
| metadata | {"version":"1.0.0","requires":{"skills":["spark"],"accessLevel":"triage"}} |
Fine-tune who gets auto-prioritized by reviewing the current priority category and adjusting contact-level settings.
Prerequisite: Read the spark base skill for tool reference and filter syntax.
Access level required: triage.
emails { "folder": "Inbox", "filter": "category:priority newer_than:14d" }
Look at which senders appear in the priority category. Ask the user: are these the right people? Anyone missing? Anyone who shouldn't be here?
Browse priority mail to identify the senders Spark is auto-prioritizing. Note any patterns - are important contacts missing, or are low-priority senders appearing?
For contacts whose emails should always be prioritized:
contact-action { "action_name": "markContactAsPrimary", "emails": ["vip@company.com"] }
This tells Spark to auto-prioritize all future email from this sender.
For contacts that are showing up in priority but shouldn't be:
contact-action { "action_name": "unmarkContactAsPrimary", "emails": ["noisy-sender@example.com"] }
For contacts where the user wants push notifications:
contact-action { "action_name": "markContactAsImportant", "emails": ["boss@company.com"] }
For contacts that are priority but don't need notifications:
contact-action { "action_name": "unmarkContactAsImportant", "emails": ["low-urgency@example.com"] }
emails { "folder": "Inbox", "filter": "category:priority is:unread" }
Check that the priority category now reflects the user's preferences. New mail from adjusted contacts will appear in the correct category.
markContactAsPrimary is the strongest signal - it guarantees the contact's emails land in priority.markContactAsImportant controls push notifications, which is separate from category placement.contact-action's changeCategoryPersonal / changeCategoryNotification / changeCategoryNewsletters to reclassify all future mail from that sender.category:priority for a reliable "must-read" view.