queue-draft

Deposit email drafts into a gated action queue for human approval.

10|1|Updated Jun 29, 2026
One-click install
npx skills add https://github.com/mishahanin/heading-os --skill queue-draft
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: queue-draft
Source: https://github.com/mishahanin/heading-os/tree/main/.claude/skills/queue-draft
Command: npx skills add https://github.com/mishahanin/heading-os --skill queue-draft

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill prevents accidental email sends by forcing all outbound drafts into a gated queue that requires explicit human intervention before any transmission can occur.

Core Features & Use Cases

  • Gated Staging: Automatically deposits email drafts into a pending queue with a gated status.
  • Safety Enforcement: Ensures that headless or automated processes can only create drafts, never approve or send them.
  • Use Case: Use this to stage a series of demo emails or outreach messages that you want to review and approve manually before they are sent to recipients.

Quick Start

Invoke the queue-draft skill by providing the recipient, subject, and body separated by double colons to stage your message for review.

Frequently Asked Questions about queue-draft

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I stage email drafts for human approval before sending?

To stage email drafts for human approval, you provide the recipient, subject, and body separated by double colons to deposit the message into a gated action queue with a pending status.

What is a gated email draft queue and how does it prevent unauthorized sends?

A gated email draft queue is a staging system that intercepts outbound messages and holds them in a pending status, ensuring automated processes can only create drafts while explicit human intervention is required to approve transmission.

Can I use automation to create email drafts without risking accidental sends?

Yes, automated processes can safely generate email drafts because the gated queue enforces safety by restricting headless operations to draft creation only, explicitly blocking any automated approval or sending functionality.

How do I manage email draft status transitions in an action queue?

Email draft status transitions are managed by the action-queue script, which handles JSON-based card persistence to maintain the gated workflow and track messages through the human approval process.

What's the best way to review automated outreach emails before they are sent?

The best way to review automated outreach emails is to stage them in a gated action queue, allowing you to manually inspect each draft card and explicitly approve the outbound communication before any transmission occurs.

Why do automated email drafts require a human approval workflow?

Automated email drafts require a human approval workflow to enforce safety, preventing accidental email sends by forcing all outbound messages into a gated queue that requires explicit human intervention before transmission.