How do I install the Spark Recipe Draft Batch skill?

Run npx skillmds add readdle/spark-recipe-draft-batch in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Spark Recipe Draft Batch safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Spark Recipe Draft Batch?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Spark Recipe Draft Batch free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Spark Recipe Draft Batch?

readdle (@readdle) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Spark Recipe Draft Batch by readdle

Name: Spark Recipe Draft Batch
Rating: 4.666666666666667 (3 reviews)
Author: readdle

File contents

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.

---name: spark-recipe-draft-batchdescription: Review and finalize multiple pending drafts in a batch session: read context, edit, or discard.--- # 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 ```bash 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: ```bash 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: ```bash 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: ```bash 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.

Frequently asked questions