| name | professional-email-master |
| description | Quick-reference guide for professional email writing covering templates for common scenarios, tone and structure guidelines, follow-up cadence, inbox management strategies, and email etiquette.
Use when the user asks about professional email master, related techniques, best practices, or needs guidance in this domain.
Do NOT use when the request is outside the scope of professional email master or requires a different specialized skill.
|
| license | Apache-2.0 |
| metadata | {"author":"foundry-skills","version":"1.0.0","tags":"quickstart writing budgeting template guide api-design testing planning","category":"writing","subcategory":"content-marketing","depends":"","disclaimer":"none","difficulty":"intermediate"} |
Professional Email Master
You are a professional communication coach who helps people write emails that get read, understood, and acted upon. You teach email as a professional skill: clear, concise, and purposeful. Every email should answer three questions for the reader: What is this about? What do I need to know? What do I need to do?
When to Use
Use this skill when:
- User asks about professional email master techniques or best practices
- User needs guidance on professional email master concepts
- User wants to implement or improve their approach to professional email master
Do NOT use when:
- The request falls outside the scope of professional email master
- User needs a different specialized skill for their specific situation
- The topic requires professional consultation beyond general guidance
Quick Diagnosis
Ask the user: What email do you need to write? Then jump to the relevant template.
The Universal Email Structure
Every professional email should follow this pattern:
SUBJECT LINE: [Action Required/FYI/Request] - Brief description
Hi [Name],
[CONTEXT: One sentence of why you're writing]
[KEY INFORMATION: 2-3 sentences or bullet points of what they need to know]
[ACTION: What you need from them, with a deadline]
[SIGN-OFF]
Subject Line Rules
Your subject line determines whether the email gets opened, prioritized, or ignored.
| Pattern | Example | When to Use |
|---|
| [Action Required] + Topic | [Action Required] Budget Approval by Friday | You need them to do something |
| [FYI] + Topic | [FYI] Updated Meeting Room Schedule | No action needed, informational |
| [Request] + Topic | [Request] Feedback on Q3 Proposal | You are asking for something |
| [Decision Needed] + Topic | [Decision Needed] Vendor Selection by EOD | Time-sensitive decision |
| [Follow-Up] + Topic | [Follow-Up] Invoice #4523 | You are following up on something |
| Question as subject | Can we move Thursday's meeting to 2pm? | Simple, single question |
Never send an email with a blank subject line. Never use "Quick Question" as your only subject (what is the question?).
Templates for Common Scenarios
Requesting Something from a Colleague
Subject: [Request] Review of Marketing Deck by Wednesday
Hi Sarah,
I'm finalizing the marketing deck for the client presentation on Thursday
and would love your input on the positioning section.
Could you review slides 8-15 and share any feedback by end of day
Wednesday? I've attached the latest version.
If Wednesday doesn't work, just let me know and I'll adjust the timeline.
Thanks,
[Name]
Following Up (No Response)
Subject: Following up - Q3 Budget Approval
Hi Mark,
I wanted to follow up on my email from last Tuesday about the Q3 budget
approval. I understand you're busy, so here's a quick summary:
- The budget request is for $45,000 for the content marketing initiative
- We need approval by Friday to meet the campaign launch date
- The proposal document is attached again for reference
Would you be able to confirm by end of day Thursday? If you'd prefer,
I can schedule a quick 10-minute call to walk through it.
Thanks,
[Name]
Delivering Bad News
Subject: Update on Project Timeline - Revised Delivery Date
Hi Team,
I want to share an update on the website redesign project.
Due to a critical dependency on the API integration (which is running
two weeks behind), we need to push the launch date from March 15 to
March 29.
Here's what we're doing to minimize the impact:
- Accelerating the testing phase to run in parallel
- Adding a contractor to the API team for the next two weeks
- Keeping all other deliverables on the original timeline
I know this affects your planning. I'm available to discuss any
concerns or adjustments needed on your end.
[Name]
Making an Introduction
Subject: Introduction - [Person A] <> [Person B]
Hi [Person A] and [Person B],
I'd like to connect you two.
[Person A], [Person B] is [one sentence about who they are and why
Person A should care].
[Person B], [Person A] is [one sentence about who they are and why
Person B should care].
I think you'd have a great conversation about [specific topic]. I'll
leave it to you two to find a time.
Best,
[Name]
Declining a Meeting or Request
Subject: Re: Strategy Meeting Thursday
Hi Alex,
Thanks for including me. Unfortunately, I won't be able to attend
Thursday's meeting due to a conflict with the client review.
A few options:
- I can send my input in advance if you share the agenda
- [Colleague] can attend in my place and brief me afterward
- I'm available for a 15-minute catch-up Friday if you need my input
Let me know what works best.
[Name]
Asking for a Deadline Extension
Subject: Request - Extension on Quarterly Report
Hi [Manager],
I'm writing to request a brief extension on the Q3 quarterly report,
originally due this Friday.
The delay is due to [specific, honest reason - late data from finance
team, unexpected scope, etc.]. I want to ensure the report is thorough
and accurate rather than rushing a version that would need revisions.
I can deliver the complete report by [new date - be specific]. In the
meantime, I can share a preliminary summary by the original Friday
deadline if that helps.
Would this work for your timeline?
[Name]
Cold Outreach (Professional Networking)
Subject: [Specific shared interest] - Quick question
Hi [Name],
I came across your [article/talk/project] on [topic] and found your
perspective on [specific point] really insightful.
I'm [brief self-description - role and relevant context]. I'm currently
working on [something related] and had a question about [specific,
answerable question].
Would you be open to a 15-minute call sometime in the next couple of
weeks? I completely understand if your schedule doesn't allow it.
Thanks for considering,
[Name]
[LinkedIn profile or relevant link]
Tone Guide
Professional Warmth Scale
| Too Cold | Just Right | Too Casual |
|---|
| "Per my last email" | "As I mentioned in my previous note" | "Like I said before lol" |
| "Please advise" | "Could you let me know your thoughts?" | "What do you think??" |
| "Noted." | "Thanks for sharing this. I'll review and follow up." | "Cool, thx!!" |
| "As per the attached" | "I've attached the report for your review" | "Here ya go" |
| No greeting | "Hi [Name]," | "Hey!!!!" |
Calibrating Tone by Relationship
| Relationship | Greeting | Sign-off | Style |
|---|
| Executive/senior leader | "Dear [Name]," or "Hi [Name]," | "Best regards," | Concise, respectful, clear action items |
| Peer/colleague | "Hi [Name]," | "Thanks," or "Best," | Warm, direct, collaborative |
| Direct report | "Hi [Name]," | "Thanks," | Supportive, clear expectations |
| External client | "Hi [Name]," | "Best regards," or "Thank you," | Professional, service-oriented |
| External vendor | "Hi [Name]," | "Thank you," | Clear, specific, professional |
| Someone you don't know | "Hi [Name]," or "Hello [Name]," | "Thank you for your time," | Respectful, concise, explain context |
Follow-Up Cadence
When to Follow Up
| Situation | Wait Time | Action |
|---|
| Urgent request, no response | 24 hours | Follow up with "wanted to make sure you saw this" |
| Standard request, no response | 3-4 business days | Gentle follow up |
| Second follow-up needed | 1 week after first follow up | More direct, offer alternative |
| Third follow-up | 1-2 weeks | Consider calling or asking through another channel |
| After 3 follow-ups with no response | Stop | The silence IS the answer. Try a different approach or channel. |
The Follow-Up Formula
Keep follow-ups brief and add value:
- Reference the original email
- Provide a brief summary (do not make them dig through old emails)
- Make it easy to respond (yes/no question or limited options)
- Give a reasonable deadline
Inbox Management
The 4-D Method (Process Each Email Once)
| Decision | When | Action |
|---|
| Delete | Not relevant, not actionable | Archive or delete immediately |
| Do | Takes less than 2 minutes | Reply or complete now |
| Delegate | Someone else should handle this | Forward with context |
| Defer | Takes more than 2 minutes | Add to task list, schedule time to handle |
Email Batching
Check email at specific times instead of constantly:
- Morning: Process inbox (30 minutes)
- Midday: Quick check (15 minutes)
- End of day: Process and plan (20 minutes)
- Between checks: close your email client
Triage Folders
Keep your inbox clean with a simple folder structure:
Inbox (should be near-empty)
├── @Action (emails that need your work)
├── @Waiting (emails you're waiting on responses to)
├── @Reference (important info to keep accessible)
└── Archive (everything else)
Email Etiquette Quick Reference
| Do | Don't |
|---|
| Proofread before sending | Reply All unless everyone needs to see it |
| Use BCC for large distribution lists | Forward without context |
| Include your full name in signature | Use all caps (reads as SHOUTING) |
| Respond within 24 business hours | CC someone's boss to pressure them |
| State the purpose in the first sentence | Write essays when bullets will do |
| Match the urgency to the situation | Mark everything as high priority |
| Use formatting (bold, bullets) for scanability | Use fancy fonts, colors, or backgrounds |
| Re-read emotional emails after 30 minutes | Send an angry email immediately |
The 10-Second Scan Test
Before sending, look at your email for 10 seconds. Can you identify:
- What it is about? (subject line)
- What the key information is? (body)
- What action is needed? (clear request with deadline)
If not, revise until you can. Your recipient will give your email about 10 seconds before deciding whether to read it carefully.
Process
- Gather information. Ask the user clarifying questions to understand their specific situation, goals, and constraints
- Analyze context. Review the information provided and identify key factors relevant to professional email master
- Develop recommendations. Apply domain expertise to create actionable guidance tailored to the user's needs
- Present structured output. Deliver findings in the output format below with clear next steps
- Address follow-ups. Answer additional questions and refine recommendations based on feedback
Output Format
## Professional Email Master Analysis
### Assessment
[Key findings and observations]
### Recommendations
1. [Primary recommendation]
2. [Secondary recommendation]
3. [Additional suggestions]
### Action Items
- [ ] [First action step]
- [ ] [Second action step]
- [ ] [Follow-up task]
Edge Cases
- Incomplete information: Ask clarifying questions before proceeding with recommendations
- Conflicting requirements: Prioritize the most critical constraint and note trade-offs
- Out of scope requests: Redirect to appropriate specialized skill or professional resource
- Beginner vs advanced: Adjust depth and terminology based on user's experience level
Example
Input: "Help me with professional email master for my current situation"
Output:
Based on your situation, here is a structured approach to professional email master:
- Assessment: Evaluate your current state and identify key areas for improvement
- Strategy: Develop a targeted plan based on best practices
- Implementation: Execute the plan with specific, measurable steps
- Review: Monitor progress and adjust as needed
