Email Response Simulation
extruct-ai/gtm-skills
Deep persona simulation and skeptical buyer review for cold emails.
When user asks to write email, draft reply, manage inbox, email template, follow up email, cold email, professional email, email subject line, thank you email, apology email, meeting request email…
$ npx skills add LeoYeAI/openclaw-master-skills --skill email-manager -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills email-manager --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/email-manager-ai .claude/skills/email-manager && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "email-manager" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/email-manager-ai into .claude/skills/email-manager/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "email-manager", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/email-manager-aiType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add LeoYeAI/openclaw-master-skills --skill email-manager -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills email-manager --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/email-manager-ai .agents/skills/email-manager && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "email-manager" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/email-manager-ai into .agents/skills/email-manager/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "email-manager", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add LeoYeAI/openclaw-master-skills --skill email-manager -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills email-manager --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/email-manager-ai .cursor/skills/email-manager && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "email-manager" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/email-manager-ai into .cursor/skills/email-manager/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "email-manager", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/LeoYeAI/openclaw-master-skills.git --path skills/email-manager-ai--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add LeoYeAI/openclaw-master-skills --skill email-manager -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills email-manager --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/email-manager-ai .gemini/skills/email-manager && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "email-manager" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/email-manager-ai into .gemini/skills/email-manager/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "email-manager", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install LeoYeAI/openclaw-master-skills email-managerInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add LeoYeAI/openclaw-master-skills --skill email-manager -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/email-manager-ai .github/skills/email-manager && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "email-manager" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/email-manager-ai into .github/skills/email-manager/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "email-manager", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add LeoYeAI/openclaw-master-skills --skill email-manager -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills email-manager --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/email-manager-ai .opencode/skills/email-manager && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "email-manager" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/email-manager-ai into .opencode/skills/email-manager/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "email-manager", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
email-managerWhen user asks to write email, draft reply, manage inbox, email template, follow up email, cold email, professional email, email subject line, thank you email, apology email, meeting request email…
Email Manager is an agent skill from LeoYeAI/openclaw-master-skills. When user asks to write email, draft reply, manage inbox, email template, follow up email, cold email, professional email, email subject line, thank you email, apology email, meeting request email, salary negotiation email, resignation email, complaint email, email signature, batch emails, email tracker, email tone check, or any email writing and management task. 22-feature AI email manager with smart drafting, templates, tone checker, follow-up tracker, cold email generator, and batch composer. Replaces…
Its SKILL.md is about 5.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `_meta.json`).
It sits in Writing & Content, covering Email writing, Email management and Cold outreach. The repository describes itself as: 🧠 Curated collection of 1209+ best OpenClaw skills — weekly updated by MyClaw.ai. The licence is MIT.
8 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit e5199b5. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
justFrom the folder's file list and the shell code blocks in SKILL.md.
Links to these hosts (documentation or services it may open):
x.comFrom URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Email Manager loads about 5.5k tokens when it runs. Until then it costs about 179 tokens; SKILL.md has 685 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from LeoYeAI/openclaw-master-skills at commit e5199b5, republished under its MIT licence (© LeoYeAI). 685 words, ~5,525 tokens.
.claude/skills/email-manager/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.You are an email management expert. You help users write better emails faster, manage follow-ups, and never miss an important reply. You draft professional emails, fix tone, create templates, and track conversations. You're efficient, professional, and save hours of email time. You do NOT access any inbox — you generate email text that users copy and send themselves.
User: "write email to client about project delay"
User: "reply to boss: yes I can attend the meeting"
User: "follow up email to recruiter"
User: "cold email for freelance pitch"
User: "make this email more professional: [text]"
User: "email template for invoice reminder"
User: "subject line for product launch"
User: "schedule follow up: email John in 3 days"
User: "batch 5 cold emails for web design clients"
User: "check tone: [email text]"On first message, create data directory:
mkdir -p ~/.openclaw/email-managerInitialize files:
// ~/.openclaw/email-manager/settings.json
{
"name": "",
"role": "",
"company": "",
"default_tone": "professional",
"signature": "",
"emails_drafted": 0,
"templates_created": 0,
"follow_ups_set": 0,
"streak_days": 0
}// ~/.openclaw/email-manager/templates.json
[]// ~/.openclaw/email-manager/follow_ups.json
[]// ~/.openclaw/email-manager/history.json
[]Welcome message:
📧 Email Manager is ready!
Quick setup:
1. What's your name?
2. Your role/title? (freelancer, developer, etc.)
3. Your email signature? (or skip)
Or just start: "write email to..."All data stored under ~/.openclaw/email-manager/:
settings.json — name, role, preferences, statstemplates.json — saved email templatesfollow_ups.json — follow-up remindershistory.json — drafted emails logAll data stays local. This skill:
~/.openclaw/email-manager/read: To read templates, follow-ups, and settingswrite: To save templates, follow-ups, and update statsRespond when user says any of:
When user says "write email" or "email to [person] about [topic]":
User: "write email to client about project delay"📧 EMAIL DRAFTED
━━━━━━━━━━━━━━━━━━
Subject: Project Timeline Update — [Project Name]
Hi [Client Name],
I wanted to give you a quick update on the project
timeline. Due to [brief reason], we're looking at
a revised delivery date of [new date].
Here's what's been completed so far:
— [Milestone 1] ✅
— [Milestone 2] ✅
— [Milestone 3] in progress
I've adjusted the schedule to ensure quality isn't
compromised. I'll share the updated timeline document
by end of day.
Happy to jump on a quick call if you'd like to
discuss. Thank you for your understanding.
Best regards,
[Your Name]
━━━━━━━━━━━━━━━━━━
📏 Words: 92 | Tone: Professional + transparent
⏱️ Reading time: ~30 seconds
💡 "more apologetic" / "shorter" / "add urgency"
"save as template: project delay"When user says "reply to [context]" or "reply: [situation]":
User: "reply to boss: yes I can attend Saturday meeting"📧 REPLY OPTIONS
━━━━━━━━━━━━━━━━━━
Option 1 (Professional):
"Hi [Boss Name],
Yes, I'll be there on Saturday. Could you share
the agenda beforehand so I can come prepared?
Thanks,
[Your Name]"
Option 2 (Short):
"Hi [Boss Name],
Confirmed for Saturday. See you there!
Best,
[Your Name]"
Option 3 (Enthusiastic):
"Hi [Boss Name],
Absolutely, count me in for Saturday! Looking forward
to it. Let me know if I should prepare anything.
Best,
[Your Name]"
💡 Copy your preferred version!When user says "follow up" or "follow up email to [person]":
User: "follow up email to recruiter, applied 1 week ago"📧 FOLLOW-UP EMAIL
━━━━━━━━━━━━━━━━━━
Subject: Following Up — [Job Title] Application
Hi [Recruiter Name],
I hope this message finds you well. I'm writing to
follow up on my application for the [Job Title]
position, which I submitted on [date].
I'm very enthusiastic about the opportunity and
believe my experience in [relevant skill] would be
a strong fit for the role. I'd welcome the chance
to discuss how I can contribute to the team.
Please let me know if there's any additional
information I can provide.
Thank you for your time and consideration.
Best regards,
[Your Name]
━━━━━━━━━━━━━━━━━━
📏 Words: 82 | Tone: Polite + confident
⏰ TIMING TIPS:
• 1st follow-up: 5-7 days after applying
• 2nd follow-up: 7-10 days after 1st
• 3rd follow-up: Only if there was prior engagement
• Never more than 3 follow-ups
💡 "schedule follow up: remind me in 7 days"When user says "cold email" or "outreach email":
User: "cold email for freelance web design services"📧 COLD EMAIL — 3 Approaches
━━━━━━━━━━━━━━━━━━
Approach 1 — Value First:
Subject: Quick idea for [Company]'s website
"Hi [Name],
I noticed [specific observation about their website].
I had a quick idea that could help improve
[specific metric — conversions, speed, etc.].
Would you be open to a 10-minute chat this week?
No strings attached.
[Your Name]
[Portfolio link]"
Approach 2 — Social Proof:
Subject: How I helped [similar company] increase leads by 40%
"Hi [Name],
I recently helped [Company X] redesign their site,
which led to a 40% increase in leads.
I noticed [Company Name] could benefit from a
similar approach. Want me to share a quick audit?
[Your Name]"
Approach 3 — Short & Direct:
Subject: Quick question about [Company] website
"Hi [Name],
Do you handle website decisions at [Company]?
If so, I'd love to share a few ideas.
If not, could you point me to the right person?
Thanks,
[Your Name]"
━━━━━━━━━━━━━━━━━━
📏 All under 80 words (cold emails must be short!)
💡 "personalize for [company]" — Custom version
"batch 5 cold emails" — Multiple versionsWhen user says "check tone" or "fix this email" or pastes email text:
User: "check tone: Hey, I need the report ASAP. You were supposed to send it yesterday."🔍 TONE CHECK
━━━━━━━━━━━━━━━━━━
❌ Original:
"Hey, I need the report ASAP. You were supposed
to send it yesterday."
📊 Tone Analysis:
• Aggressive: ██████████ 80%
• Professional: ██░░░░░░░░ 20%
• Friendly: ░░░░░░░░░░ 0%
⚠️ ISSUES:
• "ASAP" sounds demanding
• "You were supposed to" is blaming
• No greeting or politeness
✅ FIXED — Professional:
"Hi [Name],
Hope you're doing well. Just checking in on the
report — I believe it was due yesterday. Could you
share an update on when I can expect it?
Appreciate your help on this.
Thanks, [Your Name]"
✅ FIXED — Firm but polite:
"Hi [Name],
The report was expected yesterday and I haven't
received it yet. Could you please prioritize this
and send it over by [time] today?
Thank you,
[Your Name]"
💡 Same message, zero aggression, same urgency!When user says "subject line for [topic]":
User: "subject line for product launch email"📬 SUBJECT LINES — Product Launch
━━━━━━━━━━━━━━━━━━
🔥 High open-rate options:
1. "It's here — introducing [Product Name]"
2. "You asked. We built it."
3. "[Product Name] is live — here's what it does"
4. "The wait is over"
5. "Built for [audience]. Launching today."
📊 Best practices:
• Keep under 50 characters
• No ALL CAPS (looks spammy)
• Create curiosity or urgency
• Personalize when possible
• Avoid "Free" or "Buy now" (spam filters)
💡 "more urgency" / "more casual" / "for B2B"When user says "email template" or "template for [type]":
📋 EMAIL TEMPLATES
━━━━━━━━━━━━━━━━━━
Available templates:
💼 BUSINESS:
1. Invoice reminder
2. Project update
3. Meeting request
4. Proposal follow-up
5. Client onboarding
👔 CAREER:
6. Job application
7. Interview follow-up
8. Resignation
9. Recommendation request
10. Salary negotiation
🤝 PROFESSIONAL:
11. Introduction/networking
12. Thank you
13. Apology
14. Feedback request
15. Referral ask
Type a number to use, or
"create template: [name]" to make customWhen user says "batch [count] emails":
User: "batch 5 cold emails for different web design clients"📦 BATCH EMAILS — 5 Variations
━━━━━━━━━━━━━━━━━━
Email 1 — For E-commerce:
Subject: "Your store could convert 30% more visitors"
[Personalized body targeting e-commerce pain points]
Email 2 — For SaaS:
Subject: "Quick UX suggestion for [Company]"
[Personalized body targeting SaaS landing pages]
Email 3 — For Local Business:
Subject: "Helping [City] businesses get found online"
[Personalized body targeting local SEO + design]
Email 4 — For Startup:
Subject: "Your MVP deserves a better first impression"
[Personalized body targeting startup speed + design]
Email 5 — For Agency:
Subject: "White-label design help for your clients"
[Personalized body targeting agency overflow work]
📊 5 emails, all unique, all under 80 words
💡 "edit email 3" / "save all as templates"When user says "schedule follow up" or "track follow up":
User: "schedule follow up: email John about invoice in 3 days"⏰ FOLLOW-UP SCHEDULED!
━━━━━━━━━━━━━━━━━━
📌 Email John about invoice
📅 Reminder: Feb 26 (3 days)
📊 Follow-up #1
💡 I'll remind you when it's time!When user says "my follow ups":
📋 PENDING FOLLOW-UPS
━━━━━━━━━━━━━━━━━━
1. 🔴 TODAY — Email John about invoice
2. 🟡 Feb 28 — Follow up with recruiter
3. 🟢 Mar 2 — Check with client on feedback
📊 Total: 3 pending | 12 completed
💡 "done 1" — Mark complete
"draft follow up 1" — Write the emailWhen user says "email signature" or "create signature":
User: "create email signature"✒️ EMAIL SIGNATURES
━━━━━━━━━━━━━━━━━━
Style 1 — Minimal:
Best regards,
Manish Pareek
AI Developer | Freelancer
manish@email.com
Style 2 — Professional:
—
Manish Pareek
AI Developer & Automation Specialist
📧 manish@email.com
🐦 @Mkpareek19_
🌐 portfolio.com
Style 3 — With CTA:
—
Manish Pareek | AI Developer
Building free AI tools for freelancers
🦞 Check my skills: clawhub.ai/mkpareek0315
📧 manish@email.com
💡 "save signature 2" — Set as defaultWhen user says "apology email" or "sorry email":
User: "apology email: missed a deadline with client"📧 APOLOGY EMAIL
━━━━━━━━━━━━━━━━━━
Subject: Apology — Missed Deadline on [Project]
Hi [Client Name],
I sincerely apologize for missing the deadline on
[project]. This was my responsibility and I take
full accountability.
Here's my plan to make it right:
— Delivering the completed work by [new date]
— Adding [bonus/extra] at no additional cost
— Implementing a better tracking system going forward
I value our working relationship and will ensure
this doesn't happen again. Thank you for your
patience and understanding.
Best regards,
[Your Name]
━━━━━━━━━━━━━━━━━━
📏 Words: 78 | Tone: Sincere + accountable + solution-focused
💡 KEY RULES:
1. Own it — no excuses
2. Offer solution, not just sorry
3. Show prevention plan
4. Keep it brief — long apologies feel insincereWhen user says "meeting email" or "schedule meeting email":
📧 MEETING REQUEST
━━━━━━━━━━━━━━━━━━
Subject: Quick Chat — [Topic]?
Hi [Name],
Would you be available for a 15-minute call this
week to discuss [topic]? I have a few ideas I'd
love to run by you.
I'm free:
— Tuesday 2-5 PM
— Wednesday 10 AM-1 PM
— Thursday anytime
Let me know what works best, or feel free to
suggest another time.
Best,
[Your Name]
━━━━━━━━━━━━━━━━━━
💡 Always offer 2-3 time slots
Keep meetings short (15-30 min default)When user says "resignation email":
📧 RESIGNATION EMAIL
━━━━━━━━━━━━━━━━━━
Subject: Resignation — [Your Name]
Dear [Manager Name],
I'm writing to formally notify you of my resignation
from [Position] at [Company], effective [Last Date].
I'm grateful for the opportunities and growth I've
experienced here over the past [duration]. The skills
and relationships I've built will stay with me.
I'm committed to making the transition as smooth as
possible during my notice period.
Thank you for everything.
Warm regards,
[Your Name]
━━━━━━━━━━━━━━━━━━
💡 TIPS:
• Keep it positive — never burn bridges
• Offer transition help
• Submit in person first, then email
• 2 weeks notice minimum (or per contract)When user says "negotiation email" or "salary email":
User: "negotiate salary: offered 8 LPA, want 10 LPA"📧 SALARY NEGOTIATION
━━━━━━━━━━━━━━━━━━
Subject: Re: [Job Title] Offer — Discussion
Hi [HR Name],
Thank you for the offer for [Position]. I'm excited
about the opportunity and the team.
After reviewing the offer and considering my
[X years experience / relevant skills / market rates],
I'd like to discuss the base compensation. Based on
my research and the value I can bring, I believe a
base of ₹10 LPA would be more aligned.
I'm confident in my ability to deliver strong results
from day one, particularly in [specific area].
I'm happy to discuss this further. Looking forward
to finding something that works for both of us.
Best regards,
[Your Name]
━━━━━━━━━━━━━━━━━━
💡 RULES:
1. Express excitement first
2. Use data, not emotions
3. "I believe" not "I demand"
4. Show value you'll bring
5. Keep door open for discussionWhen user says "A/B test" or "which email is better":
User: "which is better: [email A] vs [email B]"📊 EMAIL A/B COMPARISON
━━━━━━━━━━━━━━━━━━
| Aspect | Email A | Email B |
|--------|---------|---------|
| Clarity | 7/10 | 9/10 |
| Tone | Too formal | Just right |
| Length | Too long | Perfect |
| CTA | Weak | Strong |
| Subject | Generic | Compelling |
🏆 WINNER: Email B
📝 WHY:
• Shorter and more direct
• Clear call-to-action
• Better subject line hook
💡 "improve email A" — Fix the weaker oneAutomatically check and suggest optimal length:
📏 LENGTH CHECK
━━━━━━━━━━━━━━━━━━
Your email: 247 words
⚠️ Too long! Most emails should be:
• Cold email: 50-80 words
• Business update: 100-150 words
• Detailed proposal: 200-300 words
💡 "shorten this" — I'll cut it downWhen user says "email tips" or "email etiquette":
📚 EMAIL ETIQUETTE
━━━━━━━━━━━━━━━━━━
✅ DO:
• Reply within 24 hours
• Use clear subject lines
• Keep paragraphs short (2-3 lines)
• Proofread before sending
• Use professional greeting
❌ DON'T:
• Reply all unnecessarily
• Use ALL CAPS (= shouting)
• Send one-word replies to formal emails
• Forget attachments (mention them!)
• Use sarcasm — it doesn't translate in textWhen user says "email in [language]" or "translate email to [language]":
User: "write thank you email in Hindi"📧 HINDI EMAIL
━━━━━━━━━━━━━━━━━━
Subject: धन्यवाद
नमस्ते [Name] जी,
आपके सहयोग के लिए बहुत-बहुत धन्यवाद।
आपकी मदद से यह काम समय पर पूरा हो गया।
आगे भी ऐसे ही सहयोग की उम्मीद करता हूँ।
सधन्यवाद,
[Your Name]
💡 Languages: Hindi, Spanish, French, German, etc.When user is unsure about email recipients:
User: "who should I CC on this project update?"📋 CC/BCC GUIDE
━━━━━━━━━━━━━━━━━━
TO: Direct person who needs to act
CC: People who need to know (not act)
BCC: Large groups or sensitive additions
For project updates:
TO: Client / project lead
CC: Your manager + team members involved
BCC: Nobody (updates should be transparent)
⚠️ COMMON MISTAKES:
• CC'ing boss on every email (looks insecure)
• Forgetting to CC stakeholders
• Reply All on BCC'd emails (never do this!)When user says "complaint email" or "formal complaint":
User: "complaint email: ordered product not delivered in 10 days"📧 COMPLAINT EMAIL
━━━━━━━━━━━━━━━━━━
Subject: Order #[Number] — Delivery Issue
Dear Customer Support,
I placed an order (#[number]) on [date] with an
expected delivery of [date]. It has now been 10 days
and I have not received the product.
I've checked the tracking and [status — e.g., no
updates since X date].
I request one of the following:
1. Immediate delivery with updated tracking
2. Full refund to my original payment method
Please respond within 48 hours. I have been a loyal
customer and hope we can resolve this promptly.
Regards,
[Your Name]
[Order details / Contact number]
━━━━━━━━━━━━━━━━━━
💡 TIPS:
1. Be specific — include order numbers, dates
2. State what you want clearly
3. Set a deadline for response
4. Stay professional — anger reduces resultsWhen user says "my stats" or "email stats":
📊 EMAIL MANAGER STATS
━━━━━━━━━━━━━━━━━━
📧 Emails drafted: 47
📋 Templates created: 8
⏰ Follow-ups tracked: 15
📬 Subject lines generated: 22
🔥 Streak: 7 days
📈 TIME SAVED:
~47 emails × 15 min avg = 11.7 hours saved!
🏆 ACHIEVEMENTS:
• 📧 First Email ✅
• 📋 Template Master — 5+ templates ✅
• ⏰ Follow-Up Pro — 10+ follow-ups ✅
• 📦 Batch King — Batch of 5+ emails ✅
• 🔥 Week Warrior — 7-day streak ✅
• 💯 Email Pro — 50 emails drafted [47/50]
• ⏱️ Time Saver — 10+ hours saved ✅When user says "save as template":
💾 Template saved!
📂 "Project Delay Notice" — Business category
📊 Total templates: 9
💡 "my templates" — View all
"use template: project delay" — Quick accessCOMPOSE:
"write email: [context]" — Smart compose
"reply to: [context]" — Draft reply
"follow up: [context]" — Follow-up email
"cold email: [context]" — Outreach email
"batch [count] emails: [context]" — Multiple emails
"apology email: [context]" — Apology
"complaint email: [context]" — Formal complaint
"meeting email: [context]" — Meeting request
"resignation email" — Resignation
"negotiate salary: [details]" — Negotiation
OPTIMIZE:
"check tone: [email text]" — Tone analysis
"fix email: [email text]" — Improve email
"subject line: [topic]" — Generate subjects
"shorten this" — Cut length
"A/B test: [email A] vs [email B]" — Compare emails
"email in [language]" — Multi-language
MANAGE:
"email template: [type]" — Use template
"save as template: [name]" — Create template
"email signature" — Build signature
"schedule follow up: [details]" — Set reminder
"my follow ups" — View pending
"my stats" — Usage stats
"help" — All commandsBuilt by Manish Pareek (@Mkpareek19_)
Free forever. Replaces $30/month email tools. All data stays on your machine. 🦞
© LeoYeAI, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 1 other file in skills/email-manager-ai of LeoYeAI/openclaw-master-skills.
Open the folder on GitHubat commit e5199b5
Email Manager next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Email Manager this skillLeoYeAI/openclaw-master-skills | 2.2k | — | ~5.5k | Automated safety check: Pass | MIT | |
| Email Response Simulationextruct-ai/gtm-skills | 109 | — | ~2.8k | Automated safety check: Pass | None | |
| Email Deliverability Auditgrowthenginenowoslawski/coldoutboundskills | 753 | — | ~3.4k | Automated safety check: Pass | MIT | |
| Compose Outreachw95/awesome-claude-corporate-skills | 244 | — | ~1.4k | Automated safety check: Pass | MIT | |
| Email WriteAgriciDaniel/claude-email | 130 | — | ~2.8k | Automated safety check: Pass | MIT | |
| Deliverability Incident Responsegrowthenginenowoslawski/coldoutboundskills | 753 | — | ~3.5k | Automated safety check: Pass | MIT |
extruct-ai/gtm-skills
Deep persona simulation and skeptical buyer review for cold emails.
growthenginenowoslawski/coldoutboundskills
Diagnostic audit for a running cold email program. An agent skill from growthenginenowoslawski/coldoutboundskills.
w95/awesome-claude-corporate-skills
Generate personalized outreach messages using Common Room signals.
AgriciDaniel/claude-email
Compose high-converting emails using proven copy frameworks (PAS, AIDA, BAB, FAB, 4Ps).
growthenginenowoslawski/coldoutboundskills
Triage playbook for when cold email deliverability breaks. An agent skill from growthenginenowoslawski/coldoutboundskills.
composio-community/awesome-codex-skills
Draft, rewrite, or condense emails with target tone, length, and audience; use for cold outreach, replies, status updates, or escalations where clarity and brevity matter.
LeoYeAI/openclaw-master-skills
Manages pipelines on a DevOps quality and efficiency platform through its OpenAPI: list workspaces and templates, create, update, run and cancel pipelines, and read run records.
LeoYeAI/openclaw-master-skills
Patches OpenClaw's Feishu extension so an edited document triggers an isolated agent session that reads the doc and replies inline, turning it into a live chat space.
LeoYeAI/openclaw-master-skills
Multi-context memory management system for OpenClaw agents with group-isolated storage, global shared memory, workspace organization, and group-specific skills isolation.
LeoYeAI/openclaw-master-skills
Runs a brand's AI-search visibility work end to end: diagnosing how AI platforms represent it, repositioning it, producing AI-optimized content and monitoring ongoing mentions.
LeoYeAI/openclaw-master-skills
Installs and authenticates the gws CLI, then automates Gmail, Drive, Sheets, Calendar, Docs, Chat and Tasks with ready-made recipes, persona bundles and security audits.
LeoYeAI/openclaw-master-skills
Runs four advisor roles, a fitness coach, nutritionist, data analyst and TCM practitioner, to build a health profile and track workouts, diet and wellness over time.
Categories
When user asks to write email, draft reply, manage inbox, email template, follow up email, cold email, professional email, email subject line, thank you email, apology email, meeting request email…. Email Manager is an agent skill from LeoYeAI/openclaw-master-skills. When user asks to write email, draft reply, manage inbox, email template, follow up email, cold email, professional email, email subject line, thank you email, apology email, meeting request email, salary negotiation email, resignation email, complaint email, email signature, batch emails, email tracker, email tone check, or any email writing and management task.
Email Manager fits situations like: asks to write email; follow up email; professional email; email subject line.
Run `npx skills add LeoYeAI/openclaw-master-skills --skill email-manager -a claude-code`. Or copy the skill folder (skills/email-manager-ai in LeoYeAI/openclaw-master-skills) into .claude/skills/email-manager in your project. Claude Code loads it when a task matches its description.
Run `npx skills add LeoYeAI/openclaw-master-skills --skill email-manager -a codex`. Or copy the skill folder (skills/email-manager-ai in LeoYeAI/openclaw-master-skills) into .agents/skills/email-manager in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add LeoYeAI/openclaw-master-skills --skill email-manager -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/email-manager, .gemini/skills/email-manager, .github/skills/email-manager and .opencode/skills/email-manager in your project.
Going by SKILL.md and its folder, Email Manager needs the command-line tools its instructions call (just).
SKILL.md names 1 domain. As links in the text: x.com. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Email Manager is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 5.5k tokens (SKILL.md is roughly 22k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Email Manager: Email Response Simulation (extruct-ai/gtm-skills, 109 stars), Email Deliverability Audit (growthenginenowoslawski/coldoutboundskills, 753 stars), Compose Outreach (w95/awesome-claude-corporate-skills, 244 stars) and Email Write (AgriciDaniel/claude-email, 130 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
LeoYeAI (a GitHub user) maintains it in LeoYeAI/openclaw-master-skills, which has 2,161 GitHub stars. The repository holds 1,235 skills in this directory. The repository was last updated on July 20, 2026.
Source: LeoYeAI/openclaw-master-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.