Email Ghostwriter
Draft professional email in a supplied writer or organization voice. Use when someone needs an outreach email, follow-up, reply, introduction, project update, scheduling note, or concise rewrite, especially when they want the message to sound like a specific person without inventing private identity details.
Package
Skill files
SKILL.md
markdown
name: email-ghostwriter
description: Draft professional email in a supplied writer or organization voice. Use when someone needs an outreach email, follow-up, reply, introduction, project update, scheduling note, or concise rewrite, especially when they want the message to sound like a specific person without inventing private identity details.
Email Ghostwriter
Draft emails that sound like the supplied writer while preserving the writer's intent, facts, boundaries, and next step.
Identity and privacy
Use identity, role, signature, links, examples, and preferences only when the user supplies them or points to an authorized source. Never invent a biography, relationship, contact detail, calendar link, employer, or private writing history. If the user has not supplied a voice, use a neutral professional voice and say so.
Workflow
- Identify the email type: outreach, scheduling, follow-up, reply, project update, introduction, decline, thank-you, or internal note.
- Identify the recipient, relationship, goal, required facts, call to action, deadline, and desired tone.
- Load only the authorized voice guide, examples, or phrase references relevant to the request.
- Draft the shortest message that accomplishes the goal. Lead with context, state the useful information, and end with one clear next step.
- Preserve names, dates, numbers, links, and commitments exactly. Flag any missing or uncertain fact instead of guessing.
- Run the review checklist below and return the draft in the requested format.
Voice controls
Adjust explicitly requested dimensions such as warmth, directness, formality, brevity, enthusiasm, and assertiveness. Prefer specific language over corporate filler. Avoid generic openings, unnecessary apologies, vague asks, over-explaining, and more than one main call to action.
Review checklist
- Does the opening make the reason for writing clear?
- Does the email sound like the supplied writer rather than a generic template?
- Are all factual claims supported by the source material?
- Is the ask easy to answer?
- Is the tone appropriate for the relationship and stakes?
- Are the subject line, greeting, sign-off, and signature appropriate?
- Have private details been included only for the intended recipient?
When the user asks to send the email, confirm the final recipient, channel, and content before taking the sending action.
--- name: email-ghostwriter description: Draft professional email in a supplied writer or organization voice. Use when someone needs an outreach email, follow-up, reply, introduction, project update, scheduling note, or concise rewrite, especially when they want the message to sound like a specific person without inventing private identity details. --- # Email Ghostwriter Draft emails that sound like the supplied writer while preserving the writer's intent, facts, boundaries, and next step. ## Identity and privacy Use identity, role, signature, links, examples, and preferences only when the user supplies them or points to an authorized source. Never invent a biography, relationship, contact detail, calendar link, employer, or private writing history. If the user has not supplied a voice, use a neutral professional voice and say so. ## Workflow 1. Identify the email type: outreach, scheduling, follow-up, reply, project update, introduction, decline, thank-you, or internal note. 2. Identify the recipient, relationship, goal, required facts, call to action, deadline, and desired tone. 3. Load only the authorized voice guide, examples, or phrase references relevant to the request. 4. Draft the shortest message that accomplishes the goal. Lead with context, state the useful information, and end with one clear next step. 5. Preserve names, dates, numbers, links, and commitments exactly. Flag any missing or uncertain fact instead of guessing. 6. Run the review checklist below and return the draft in the requested format. ## Voice controls Adjust explicitly requested dimensions such as warmth, directness, formality, brevity, enthusiasm, and assertiveness. Prefer specific language over corporate filler. Avoid generic openings, unnecessary apologies, vague asks, over-explaining, and more than one main call to action. ## Review checklist - Does the opening make the reason for writing clear? - Does the email sound like the supplied writer rather than a generic template? - Are all factual claims supported by the source material? - Is the ask easy to answer? - Is the tone appropriate for the relationship and stakes? - Are the subject line, greeting, sign-off, and signature appropriate? - Have private details been included only for the intended recipient? When the user asks to send the email, confirm the final recipient, channel, and content before taking the sending action.
references/intro-email-examples.md
markdown
Generic Introduction Examples
These examples illustrate structure only. They contain no real people, organizations, or contact details.
Colleague to prospective partner
Hi [Recipient A] and [Recipient B],
Connecting you because [Recipient A] is exploring [topic] and [Recipient B] has relevant experience with [specific area]. I thought a short conversation could be useful for both of you.
I will leave you to take it from here.
Best, [Sender]
Customer to specialist
Hi [Recipient A] and [Recipient B],
[Recipient A], meet [Recipient B], who works on [relevant capability]. [Recipient B], [Recipient A] is evaluating [specific problem] and may benefit from your perspective.
Hope you two find the conversation useful.
Best, [Sender]
Post-call introduction
Hi [Recipient A] and [Recipient B],
Following up on our conversation, I wanted to connect you with [Recipient B], who has worked on [relevant problem]. [Recipient A] is currently focused on [context].
I will let you coordinate directly from here.
Best, [Sender]
# Generic Introduction Examples These examples illustrate structure only. They contain no real people, organizations, or contact details. ## Colleague to prospective partner Hi [Recipient A] and [Recipient B], Connecting you because [Recipient A] is exploring [topic] and [Recipient B] has relevant experience with [specific area]. I thought a short conversation could be useful for both of you. I will leave you to take it from here. Best, [Sender] ## Customer to specialist Hi [Recipient A] and [Recipient B], [Recipient A], meet [Recipient B], who works on [relevant capability]. [Recipient B], [Recipient A] is evaluating [specific problem] and may benefit from your perspective. Hope you two find the conversation useful. Best, [Sender] ## Post-call introduction Hi [Recipient A] and [Recipient B], Following up on our conversation, I wanted to connect you with [Recipient B], who has worked on [relevant problem]. [Recipient A] is currently focused on [context]. I will let you coordinate directly from here. Best, [Sender]
references/phrases-and-templates.md
markdown
Email Patterns and Phrase Bank
Use these as adaptable patterns, not text to copy blindly. Replace bracketed fields with supplied facts only.
Outreach
Hi [Name],
[One sentence on why you are reaching out]. [One sentence connecting the recipient's context to the reason for writing.] Would you be open to [specific next step]?
Best, [Sender]
Follow-up
Hi [Name],
Thanks for [the conversation / the note / the introduction]. I took away [specific point]. As a next step, I suggest [action]. Would [option or timing] work?
Best, [Sender]
Project update
Hi [Name],
Quick update on [project]. We completed [progress], and [decision or result]. The main item to resolve is [risk or question]. Could you confirm [specific decision] by [date]?
Best, [Sender]
Introduction
Hi [Name 1] and [Name 2],
Connecting you because [specific reason]. [Name 1] is [relevant context]; [Name 2] is [relevant context]. I will leave you both to take it from here.
Best, [Sender]
Decline
Hi [Name],
Thank you for thinking of me. I am going to pass because [brief reason]. I wanted to respond directly rather than leave you waiting. I hope [specific useful next step or good wish].
Best, [Sender]
Useful phrase choices
- “The main question is…”
- “To keep this moving, could you…”
- “My recommendation is…”
- “I took away three things…”
- “I do not have enough information to confirm that yet.”
- “If that works, I will…”
# Email Patterns and Phrase Bank Use these as adaptable patterns, not text to copy blindly. Replace bracketed fields with supplied facts only. ## Outreach Hi [Name], [One sentence on why you are reaching out]. [One sentence connecting the recipient's context to the reason for writing.] Would you be open to [specific next step]? Best, [Sender] ## Follow-up Hi [Name], Thanks for [the conversation / the note / the introduction]. I took away [specific point]. As a next step, I suggest [action]. Would [option or timing] work? Best, [Sender] ## Project update Hi [Name], Quick update on [project]. We completed [progress], and [decision or result]. The main item to resolve is [risk or question]. Could you confirm [specific decision] by [date]? Best, [Sender] ## Introduction Hi [Name 1] and [Name 2], Connecting you because [specific reason]. [Name 1] is [relevant context]; [Name 2] is [relevant context]. I will leave you both to take it from here. Best, [Sender] ## Decline Hi [Name], Thank you for thinking of me. I am going to pass because [brief reason]. I wanted to respond directly rather than leave you waiting. I hope [specific useful next step or good wish]. Best, [Sender] ## Useful phrase choices - “The main question is…” - “To keep this moving, could you…” - “My recommendation is…” - “I took away three things…” - “I do not have enough information to confirm that yet.” - “If that works, I will…”
Related
Other Operations skills
Format Like Mckinsey
Review and improve spreadsheet structure and formatting so the main takeaway is immediately clear. Use after building or editing a spread...
Hands On Deck
Use this skill any time a .pptx file is involved in any way — as input, output, or both. This includes reading, analyzing, or extracting...
Intercom API
Operate Intercom conversations and help center content.