Sales email drafting and communications assistant for Fable Food's sales team. Drafts replies to customer and prospect emails, writes outreach sequences, and helps with any external sales communication — without sending anything. Trigger when the user asks to: draft an email, reply to a customer, write outreach, prepare a follow-up, or anything involving external sales or customer communication.
This skill helps Fable Food's sales team draft external emails: replies to customers, cold outreach, follow-ups, and any other sales communication. It never sends anything — it only drafts for the rep to review and send themselves.
Before drafting anything, Claude should:
Read the user's style profile from memory/people/{name}.md (e.g. memory/people/ji-davis.md)
Check CLAUDE.md for quick decoding of any names, acronyms, or account references in the request
Pull the relevant email thread via Gmail if the user is replying to something:
search_emails with the customer name or subject to find the threadget_email to read the full thread for contextthread_id is the message ID of the first/oldest email in the thread — not the most recent one. From search_emails results, identify the earliest message in the thread and use its ID as the thread_id in Step 4. Using the wrong message ID will cause the draft to fail.Pull any relevant account context if needed:
CUS space for key customer pages#us-sales, #uk-sales, #au-sales) for recent internal discussionSR space in Confluence) for ICPs, buyer personas, product comparisonsClarify (ask only what's needed, don't over-question):
What type of email?
What's the goal? (e.g. schedule a call, share product info, confirm an order detail, re-engage)
Who is the recipient? (Check memory/glossary.md — they may already be a known contact)
Any specific points to include or avoid?
If the user pastes an email directly or says "reply to this", skip clarifying and draft immediately using their style profile.
Apply the user's style profile strictly. Key principles:
Show the draft clearly. Then:
Once the user is happy (or immediately if they say "looks good" / "save it" / "create the draft"):
create_draft with:
to: recipient address from the threadsubject: the email subject (prefix with Re: if replying)body: the final agreed draft textcc: any CC addresses if applicablethread_id: the first/oldest message ID captured in Step 1 (so the draft lands in the right thread)draft_url as a clickable link so the rep can open it directly in Gmail on web:
Draft saved — [open in Gmail]({draft_url})
The team works primarily from Gmail web, so this link is essential — never skip it.Do NOT send the email. The rep reviews and sends from Gmail themselves.
If memory/people/{name}.md doesn't exist, ask:
Once established, save to memory/people/{name}.md following the format in memory/people/ji-davis.md.
| Need | Where to look |
|---|---|
| Customer background | Confluence CUS space → customer page |
| Recent email thread | Gmail → search_emails then get_email (use oldest message ID as thread_id) |
| Save draft to Gmail | Gmail → create_draft with thread_id; always return draft_url link for Gmail web |
| Deal stage / contact info | HubSpot → search_crm_objects |
| Recent internal discussion | Slack → #us-sales, #uk-sales, #au-sales, #sales-pipeline-updates |
| Meeting notes | Fireflies → fireflies_search by customer name |
| Sales strategy / ICP | Confluence SR space |
| Product specs | Confluence PI or FQS spaces |
| Prospect research | Apollo → apollo_mixed_people_api_search or apollo_contacts_search |