القائمة
Process GateKeeper's new sender queue: review, accept legitimate contacts, and block unwanted senders.
التثبيت باستخدام 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-new-sender-review |
| description | Process GateKeeper's new sender queue: review, accept legitimate contacts, and block unwanted senders. |
| metadata | {"version":"1.0.0","requires":{"skills":["spark"],"accessLevel":"triage"}} |
Process Spark's GateKeeper queue of new senders. Review each, accept legitimate contacts, and block unwanted ones.
Prerequisite: Read the spark base skill for tool reference and filter syntax.
Access level required: triage.
emails { "folder": "Inbox", "new_senders": true }
This shows emails from senders that GateKeeper has quarantined (explicit mode). The normal inbox view filters these out automatically.
For each new sender email, read the content:
thread { "message_id": "<id>" }
Decide: is this a legitimate contact or unwanted mail?
contact-action { "action_name": "acceptContact", "emails": ["sender@company.com"] }
This moves the sender past GateKeeper - their future emails appear in the normal inbox.
To accept an entire domain:
contact-action { "action_name": "acceptDomain", "emails": ["company.com"] }
contact-action { "action_name": "blockContact", "emails": ["spammer@example.com"] }
To block an entire domain:
contact-action { "action_name": "blockDomain", "emails": ["example.com"] }
emails { "folder": "Inbox", "new_senders": true }
Confirm the queue is empty or report what's left.
emails is called with new_senders - they're filtered from the normal inbox view.acceptDomain is useful for legitimate companies with multiple sender addresses (support@, billing@, etc.).blockDomain is aggressive - use it for clearly spammy domains, not for individual unwanted senders.