/gog-email-draft

name: gog-email-draft
description: Draft email replies and compose new messages. Given email ID(s) or message context, generate professional email drafts in user's preferred tone. Offers multiple variants (concise, warmer) and includes assumptions/questions for confirmation. Use when user wants to reply to emails, compose new messages, or needs help with email writing. Does NOT send emails.
compatibility: Requires gog CLI tool with email access
metadata:
  author: gog-skills
  version: "1.0"
allowed-tools: Bash(gog:*) Read

Email Drafting Assistant

Generate professional, context-aware email drafts with tone variants and confirmation prompts.

When to Use

Use this skill when:

• User wants to "reply to [email]" or "draft a reply"
• User asks to "compose an email to [person]"
• User mentions "write an email about [topic]"
• User provides email ID(s) from triage and wants to respond
• User needs help with email phrasing or tone

**Important**: This skill creates DRAFTS only. It NEVER sends emails. Use `gog-email-send` skill for sending (with explicit confirmation).

Inputs You Need

Before drafting, gather:

1. Email Context (choose one)

**Option A - Reply to existing email(s):**

• Email ID(s) from `gog gmail search` or triage output
• Fetch full email content: `gog gmail get <messageId> --json`

**Option B - Compose new email:**

• Recipient(s): email address(es)
• Subject: what the email is about
• Context: key points to include

2. User's Tone Preference

If not previously known, ask:

What tone would you like for this email?
- Professional (formal, business-standard)
- Friendly (warm but professional)
- Concise (brief and to-the-point)
- Detailed (thorough, includes context)

Or describe your preferred style.

**Remember preference** for future drafts in the session.

3. Missing Information

Identify what's needed to draft effectively:

• Specific facts or data to include
• Deadline or timeline to mention
• Attachments to reference
• People to CC
• Action items or next steps

**Ask clarifying questions** before drafting if critical info is missing.

Workflow

Step 1: Fetch Original Email (if replying)

For replies:

gog gmail get <email_id> --json

Parse:

• From / To / CC
• Subject
• Body content
• Date
• Thread context

If email has a thread, consider reading previous messages in thread for context.

Step 2: Identify Required Content

Analyze what the reply should address:

**Questions asked**: Direct questions that need answers **Action items**: Tasks or requests that need response **Context needed**: Background or explanation to provide **Next steps**: Proposed follow-up or timeline **Tone match**: Match or adjust based on sender's tone

Step 3: Draft Initial Assumptions

Before drafting, list assumptions being made:

## Assumptions

- [Assumption 1: e.g., Budget is approved for this project]
- [Assumption 2: e.g., Timeline of 2 weeks is acceptable]
- [Assumption 3: e.g., Legal review is not required]
- [...]

Step 4: Draft Questions for User

List clarifying questions if any:

## Questions to Confirm

1. [Question 1: e.g., Should we include pricing in this email?]
2. [Question 2: e.g., Do you want to propose a specific meeting time?]
3. [Question 3: e.g., Is there a deadline we should mention?]

If questions are critical, ask now and wait for answers. If minor, include in output for user to address.

Step 5: Generate Draft Variants

Create TWO versions:

**Variant A: Concise**

• Brief and to-the-point
• ~3-5 sentences or ~100-150 words
• Covers essentials only
• Good for quick responses

**Variant B: Warmer/Detailed**

• More conversational or thorough
• ~7-10 sentences or ~200-300 words
• Includes context and reasoning
• Good for important stakeholders

Step 6: Present Drafts

Output in this format:

# Email Draft: [Subject]

**To**: [recipient(s)]
**CC**: [if applicable]
**Subject**: [subject line]

---

## Variant A: Concise

[Draft text here]

---

## Variant B: Warmer

[Draft text here]

---

## Assumptions

- [List assumptions made]

## Questions to Confirm

1. [List questions if any]

---

**Next Steps**:
- Edit either variant as needed
- Confirm assumptions are correct
- Answer any questions listed
- When ready: "Send this draft" (will invoke gog-email-send with confirmation)

Step 7: Iterative Refinement

After presenting drafts:

• User may request edits: "Make it more formal" / "Add mention of X"
• User may answer questions: "Yes, include pricing"
• User may choose one variant and refine it

**Iterate** until user is satisfied.

When user approves final draft, offer:

Ready to send? Say "Save as draft" to create in GOG, or "Send this email" to proceed with sending (requires explicit confirmation).

Step 8: Save Draft in GOG

When user says "Save as draft" or "Create draft":

# Create draft body file first
cat > /tmp/draft_body.txt << 'EOF'
[Draft email body content]
EOF

# Create draft
gog gmail drafts create \
  --to "recipient@example.com" \
  --cc "cc@example.com" \
  --subject "Subject line" \
  --body /tmp/draft_body.txt \
  --json

# Clean up temp file
rm /tmp/draft_body.txt

**Note**: Reply threading is handled automatically by Gmail when replying to a thread. If creating a standalone draft, omit reply-related flags.

Return draft ID to user:

✅ Draft created successfully!
Draft ID: draft_abc123

You can:
- Review it in your email client
- Edit it further there
- Send it via: "Send draft draft_abc123"

Output Format (Strict)

Every draft output MUST include:

1. **Header**: To, CC (if any), Subject 2. **Variant A**: Concise version 3. **Variant B**: Warmer/detailed version 4. **Assumptions**: Bulleted list of assumptions 5. **Questions**: Numbered list (or "None" if all info is clear) 6. **Next steps**: Clear guidance on what to do next

**Email body format**:

• Professional greeting (Hi [Name], / Hello [Name],