Menu
Review and finalize multiple pending drafts in a batch session: read context, edit, or discard.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle 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-draft-batch |
| description | Review and finalize multiple pending drafts in a batch session: read context, edit, or discard. |
| metadata | {"version":"1.0.0","requires":{"skills":["spark"],"accessLevel":"triage"}} |
Review and finalize multiple pending drafts in a single session. Read context for each, decide whether to edit, keep, or discard.
Prerequisite: Read the spark base skill for tool reference and filter syntax.
Access level required: triage.
emails { "folder": "Drafts" }
Review the list of drafts - note subjects, recipients, and dates.
For each draft, read the full thread to understand the context:
thread { "message_id": "<id>" }
Check if the conversation has moved on since the draft was created - someone else may have replied, or the topic may be resolved.
For each draft, present the options to the user:
Edit - the draft needs changes before sending:
draft { "edit": "<id>", "body": "Updated content..." }
draft { "edit": "<id>", "subject": "Updated subject" }
Keep as-is - the draft is ready to send. Note it for the user.
Discard - the draft is no longer needed. Move to trash:
action { "action_name": "moveToTrash", "message_ids": ["<id>"] }
Summarize: "Reviewed N drafts. M edited, K ready to send, L discarded."
draft's edit updates the draft in place - it doesn't create a new one.reply_to), read the original thread to verify the reply still makes sense.moveToTrash is reversible - the draft can be recovered from trash if needed.