Email drafting
Skill furkangonel/cowrangler/bundled_skills/email/email-drafting
Autonomous terminal AI agent for workflows and feasible project procedures. Co-Worker Co-Wrangler π
npx -y skills add furkangonel/cowrangler --skill email-draftingAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Professional email drafting β structure, tone, and templates for common business contexts
SKILL.md
4.6 KB, as published. Nobody here has run it
Email Drafting SOP
Goal
Write clear, professional emails that get read and acted upon. Match tone to context. Drive the desired outcome with minimal friction for the recipient.
Email Anatomy
Subject: [Category] Specific, actionable title
Hi [Name / Team],
[Opening: 1 sentence β context or reason for writing]
[Body: 2-4 sentences β the point, details, or ask]
[CTA: 1 clear ask or next step]
[Closing],
[Your name]
Subject Line Formulas
| Pattern | Example |
|---|---|
| Direct action | "Review needed: API proposal by Friday" |
| Question | "Quick question about Q3 roadmap scope" |
| FYI/update | "Update: auth migration completed" |
| Number | "3 options for the database decision" |
| Deadline | "Decision needed before Thursday standup" |
Rules:
- Under 50 characters where possible
- Put the most important word first
- Avoid "Hello", "Following up", "Just checking in" as openers
- Never use ALL CAPS
Tone Calibration
| Context | Tone | Avoid |
|---|---|---|
| Executive / C-suite | Concise, direct, no fluff | Long intros, excessive detail |
| Colleague / peer | Conversational, collaborative | Overly formal language |
| Client / external | Professional, warm | Jargon, internal acronyms |
| Vendor / support | Clear, factual, firm | Aggressive or passive |
| Sensitive topics | Empathetic, non-accusatory | Blame, assumptions |
Templates
Follow-up
Subject: Following up β [topic]
Hi [Name],
I wanted to follow up on [topic] from [context/date].
[One sentence on current status or what you're waiting on]
Could you let me know [specific ask] by [date]?
Thanks,
[Name]
Meeting request
Subject: 30 min: [topic] this week?
Hi [Name],
I'd love to get 30 minutes with you to discuss [topic and why it matters].
My availability this week:
- [Day], [time range]
- [Day], [time range]
Does any of these work? Happy to adjust.
[Calendly link if available]
Thanks,
[Name]
Cold outreach
Subject: [Specific hook β their work, mutual connection, or shared interest]
Hi [Name],
[1 sentence: who you are + why you're reaching out β be specific, not generic]
[1-2 sentences: the value or relevance to them specifically]
[Clear, low-friction ask β not "let me know if you're interested" but a specific question or step]
[Name]
Decline / no
Subject: Re: [original subject]
Hi [Name],
Thank you for thinking of me / reaching out about [topic].
Unfortunately, [reason β brief and honest, not over-explained].
[Optional: alternative or redirect if helpful]
I appreciate your understanding.
Best,
[Name]
Escalation
Subject: [ESCALATION] [topic] β needs resolution by [date]
Hi [Name],
I'm escalating [issue] as it's blocking [impact].
**Background**: [2 sentences max]
**What's needed**: [specific decision or action]
**Deadline**: [date/time and why]
**Who's involved**: [names]
Let me know how you'd like to proceed.
[Name]
Status update / progress report
Subject: [Project] update β [date or sprint]
Hi [Name/Team],
Quick update on [project]:
β
Done: [key completions]
π In progress: [current work, ETA]
β οΈ Blocked: [blockers, if any]
π
Next: [upcoming milestones]
Full details in [link if applicable].
[Name]
Opening Lines That Work
Instead of "I hope this finds you well":
- "I wanted to share a quick update on..."
- "Following our conversation last Tuesday..."
- "I have a decision I need your input on."
- "Good news β [milestone] is complete."
For cold email:
- "I read your post on [topic] and wanted to..."
- "[Mutual contact] suggested I reach out..."
- "I noticed [specific thing about their work]..."
Proofreading Checklist
- Subject line is specific and under 50 chars
- Recipient name spelled correctly
- One clear ask per email
- No passive-aggressive tone ("as per my last email", "per our conversation")
- Attachments actually attached (if mentioned)
- Reply-all vs reply checked
- No internal info that shouldn't go external
- Deadline is explicit (not "soon" or "ASAP")
- CTA requires a yes/no or a date, not an open-ended response
Length Guide
| Email type | Target length |
|---|---|
| Internal quick update | 3-5 sentences |
| Meeting request | 5-8 sentences |
| External professional | 100-150 words |
| Escalation | 150-200 words with structure |
| Cold outreach | Under 100 words |