mcpField
S
spark-recipe-draft-batch

spark-recipe-draft-batch

github.com/readdleProductivity154323 installsUpdated 6d ago
Repository

About spark-recipe-draft-batch

A Spark recipe for reviewing multiple pending email drafts in one session. It guides users to check each draft against its thread, then edit, keep, or discard it.

Key features

  1. 01List pending drafts
  2. 02Read each draft's conversation context
  3. 03Edit, keep, or discard drafts
  4. 04Summarize review outcomes

Use cases

  1. 01Clear an accumulated draft backlog
  2. 02Update replies after new messages arrive
  3. 03Discard drafts for resolved conversations

MCP support

This is a Spark recipe that guides draft review through Spark commands; the input does not describe an MCP connection.

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/readdle/spark-cli-skills --skill spark-recipe-draft-batch

After installing, type/spark-recipe-draft-batchin Claude Code to confirm it loaded.

Details

From the project README

Recipe: Draft Batch Review

Review and finalize multiple pending drafts in a single session. Read context for each, decide whether to edit, keep, or discard.

Prerequisite: Read the use-spark base skill for command reference and filter syntax.

Access level required: triage.

Steps

Step 1: List all pending drafts
spark emails Drafts

Review the list of drafts - note subjects, recipients, and dates.

Step 2: Review each draft in context

For each draft, read the full thread to understand the context:

spark thread <id>

Check if the conversation has moved on since the draft was created - someone else may have replied, or the topic may be resolved.

Step 3: Decide on each draft

For each draft, present the options to the user:

Edit - the draft needs changes before sending:

spark draft --edit <id> --body "Updated content..."
spark 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:

spark action moveToTrash <id>
Step 4: Report

Summarize: "Reviewed N drafts. M edited, K ready to send, L discarded."

Tips

  • Drafts accumulate when the user starts replies but doesn't finish them. This recipe clears the backlog.
  • Always read the thread before editing a draft - the context may have changed since it was created.
  • If a thread has new replies since the draft was created, the draft may be outdated and need rewriting.
  • draft --edit updates the draft in place - it doesn't create a new one.
  • For drafts that are replies (--reply-to), read the original thread to verify the reply still makes sense.
  • Run this recipe weekly to prevent draft accumulation.
  • Discarding via moveToTrash is reversible - the draft can be recovered from trash if needed.

Comments

Markdown supported