professional-email
Skill1 starsChanged 32 days agoMITView on GitHub
Rewrite rough notes, mixed-language drafts (including Roman Urdu, Hinglish, or broken English), or emotional first drafts into clear, professional emails and client messages with the right tone. Use when a user asks to write or fix an email, reply to a client, follow up on payment, ask for a deadline extension, decline work politely, or says make this professional. Covers payment follow-ups from polite to firm.
In this repository11 other files it gives its agents.
- assignment-researcherSkill
- client-brief-analyzerSkill
- fyp-project-managerSkill
- interview-grillerSkill
- learn-in-30-daysSkill
- portfolio-case-studySkill
- pricing-calculatorSkill
- project-scope-plannerSkill
- proposal-writerSkill
- resume-builderSkill
- study-any-topicSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
Ask for or identify: who receives it, what outcome the user wants, and the relationship (new client, regular client, boss, teacher).
- Distinctive: line 15
Read the rough draft for the real message underneath.
- Distinctive: line 19
If the input is in another language or mixed language, translate the meaning faithfully - do not add promises, apologies, or commitments …
- Distinctive: line 22
Never add a commitment, discount, deadline, or apology the user did not write or approve.
- Distinctive: line 23
Never send or claim to send the email - output is a draft for the user to send.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Professional Email and Messages
When to use this skill
- Sending an important email to a client, manager, or teacher
- Following up on an unpaid invoice or a silent client
- Saying no, asking for more time, or delivering bad news professionally
Workflow
- Ask for or identify: who receives it, what outcome the user wants, and the relationship (new client, regular client, boss, teacher). Tone depends on all three.
- Read the rough draft for the real message underneath. Keep every fact (dates, amounts, deliverables) exactly as given - polish the language, never change the facts.
- Choose the tone level and state it: Polite (first follow-up), Clear (second, with dates), Firm (third or later, with consequences stated calmly). For payment follow-ups, count which attempt this is.
- Structure: subject line that states the topic, one-line context, the ask in its own line, a specific date or next step, professional close. Short paragraphs, no wall of text.
- Deliver the clean version first. Under it, give 1-2 alternate subject lines and, if the draft was emotional, one line explaining what was softened and why.
- If the input is in another language or mixed language, translate the meaning faithfully - do not add promises, apologies, or commitments the user did not make.
Rules - never break these
- Never add a commitment, discount, deadline, or apology the user did not write or approve.
- Never send or claim to send the email - output is a draft for the user to send.
- Firm does not mean threatening. State facts and next steps; leave emotion in the deleted draft.
- One email, one main ask. If the user has two topics, recommend two emails.
Output format
- Subject: the chosen subject line
- Email body - ready to copy, in the chosen tone
- Tone used - Polite / Clear / Firm + why
- Alternatives - 1-2 other subject lines
Example
User: Make this professional, it is my second follow-up: bhai payment ka kya hua, 2 week ho gaye hain, kaam to kab ka deliver kar diya tha, please bata dein
Good output (excerpt): Subject: Payment follow-up - Invoice 12, delivered 1 Oct. Body (Clear tone): I hope you are well. I am following up on Invoice 12 for the delivered website work, due on 1 Oct. Could you please confirm the payment date this week? If any document is needed from my side, I will send it today. Facts kept, frustration removed, specific ask added.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

