---
name: email-template-writer
description: |
  Professional email templates for common scenarios - follow-ups, introductions, cold outreach, declining requests, asking for help, and navigating difficult conversations.
  Use when the user asks about email template writer, related techniques, best practices, or needs guidance in this domain.
  Do NOT use when the request is outside the scope of email template writer or requires a different specialized skill.
license: Apache-2.0
metadata:
  author: foundry-skills
  version: "1.0.0"
  tags: "quickstart writing template research email"
  category: "writing"
  subcategory: "content-marketing"
  depends: ""
  disclaimer: "none"
  difficulty: "intermediate"
---

# Email Template Writer

You are a professional communication specialist. Help the user write clear, effective emails for any situation. Provide templates they can customize. Prioritize brevity, clarity, and appropriate tone.


## When to Use

**Use this skill when:**
- User asks about email template writer techniques or best practices
- User needs guidance on email template writer concepts
- User wants to implement or improve their approach to email template writer

**Do NOT use when:**
- The request falls outside the scope of email template writer
- User needs a different specialized skill for their specific situation
- The topic requires professional consultation beyond general guidance

## Email Structure Formula

Every professional email follows this structure:

1. **Subject line** - Specific, action-oriented, under 50 characters
2. **Opening** - Why you're writing (1 sentence)
3. **Body** - Details, context, ask (2-4 sentences)
4. **Call to action** - What you need from them (1 sentence)
5. **Close** - Thanks + sign-off

## Professional Templates

### Follow-Up After No Response

**Subject: Following up: [Original Subject]**

```
Hi [Name],

I wanted to follow up on my email from [date] about [topic].
I understand you're busy - just want to make sure this didn't
slip through.

[One sentence restating the key ask or question.]

Would [specific day/time] work for a quick chat, or would you
prefer to handle this over email?

Thanks,
[Your name]
```

### Meeting Request

**Subject: Meeting request: [Topic] - [Time estimate]**

```
Hi [Name],

I'd like to schedule [time estimate, e.g., 30 minutes] to discuss
[specific topic].

Context: [1-2 sentences on why this meeting is needed and what
you hope to accomplish.]

Would any of these times work?
- [Option 1]
- [Option 2]
- [Option 3]

Happy to adjust if none work. [Or: I've sent a calendar invite
for [time] - let me know if that works.]

Best,
[Your name]
```

### Asking for Help / Information

**Subject: Quick question about [topic]**

```
Hi [Name],

I'm working on [project/task] and could use your expertise on
[specific area].

Specifically, I'm trying to [what you need] and I'm stuck on
[the blocker].

I've already [what you've tried], but I think you might have
insight on [specific question].

Would you have 10 minutes this week to point me in the right
direction?

Thanks so much,
[Your name]
```

### Introduction / Networking

**Subject: Introduction - [Your Name], [Role/Company]**

```
Hi [Name],

I'm [Your Name], [your role] at [company/context]. I came across
your [work/article/talk on topic] and it resonated with me because
[specific reason - shows you actually engaged with their work].

[1-2 sentences about what you're working on that connects to
their expertise.]

I'd love to [specific, low-commitment ask: buy you a coffee /
ask you one question / get your take on something]. No pressure
at all if you're too busy.

Best,
[Your name]
```

### Cold Outreach (Business)

**Subject: [Specific value prop in 5-7 words]**

```
Hi [Name],

I noticed [something specific about their company/role that shows
research, not generic flattery].

At [your company], we help [target audience] with [specific problem]
by [brief solution]. [One concrete result/metric if available.]

Would you be open to a 15-minute call to see if this could help
[their company name]? If not the right time, no worries at all.

Best,
[Your name]

P.S. [Optional: link to relevant case study or resource]
```

## Difficult Conversations

### Declining a Request

**Subject: Re: [Original Subject]**

```
Hi [Name],

Thank you for thinking of me for [the request]. I appreciate it.

Unfortunately, I'm not able to [take this on / participate / commit]
right now due to [brief, honest reason - current workload,
conflicting priorities, etc.].

[Optional alternative:]
- I'd suggest reaching out to [person] who might be a great fit.
- I could help with [smaller alternative] if that would be useful.
- I'd be happy to revisit this in [timeframe].

Thanks for understanding,
[Your name]
```

### Delivering Bad News

**Subject: Update on [Project/Topic]**

```
Hi [Name],

I want to give you a transparent update on [topic].

[State the issue directly - don't bury it.]
[What caused it - brief, factual, no excuses.]

Here's what I'm doing about it:
1. [Action already taken]
2. [Next step and timeline]
3. [How you'll prevent recurrence]

[The revised timeline / expectation.]

I take responsibility for this and am committed to [resolution].
Happy to discuss further if you have questions.

[Your name]
```

### Disagreeing Professionally

**Subject: Re: [Original Subject]**

```
Hi [Name],

Thanks for sharing your perspective on [topic]. I see the
reasoning behind [their position - show you understood them].

I have a different view, and I want to share it constructively.
[State your position clearly in 1-2 sentences.]

My reasoning:
- [Point 1 with evidence]
- [Point 2 with evidence]

That said, I'm open to being wrong. Could we [discuss this in
person / look at the data together / get a third perspective]?

Appreciate the dialogue,
[Your name]
```

### Apologizing

**Subject: Apology regarding [specific thing]**

```
Hi [Name],

I owe you an apology. [State what you did wrong - specifically,
no vague "if I offended anyone" language.]

[Brief explanation of impact you understand it had - shows
empathy, not excuses.]

[What you're doing to fix it / prevent it from happening again.]

I value [the relationship / working together / your trust] and
I'm committed to doing better.

[Your name]
```

## Workplace Scenarios

### Status Update

**Subject: [Project] status update - [date]**

```
Hi [Name/Team],

Quick update on [project]:

PROGRESS:
- Completed: [what's done]
- In progress: [what's underway]
- Blocked: [any blockers and what's needed to resolve]

NEXT STEPS:
- [Next milestone] by [date]
- [Action item] - [owner]

Overall status: On track / At risk / Behind

Let me know if you have questions.

[Your name]
```

### Requesting Feedback

**Subject: Feedback request: [what you want reviewed]**

```
Hi [Name],

I'd appreciate your feedback on [document/design/proposal].

Link: [link]

Specifically, I'd love your input on:
1. [Specific question]
2. [Specific question]

A quick gut reaction is fine - no need for a deep review.
If you could share thoughts by [date], that would be great.

Thanks,
[Your name]
```

### Thank You / Appreciation

**Subject: Thank you for [specific thing]**

```
Hi [Name],

I wanted to take a moment to thank you for [specific action
they took].

[Why it mattered - the impact it had on you, the project,
or the team. Be specific.]

I really appreciate [quality they demonstrated: your generosity,
your quick turnaround, your thoughtful feedback, etc.].

Thanks again,
[Your name]
```

## Email Best Practices

| Do | Don't |
|----|-------|
| Front-load the key message | Bury the ask in paragraph 3 |
| Use specific subject lines | "Quick question" or "Hi" |
| Keep under 5 sentences when possible | Write essay-length emails |
| Use bullet points for multiple items | Wall of text |
| State deadline if there is one | Assume they'll respond today |
| Proofread names and titles | Misspell their name |
| CC people who need awareness | CC everyone "just in case" |
| Reply-all only when everyone needs it | Default to reply-all |
| Send during business hours | Send at 2 AM (use schedule send) |


## Process

1. **Gather information.** Ask the user clarifying questions to understand their specific situation, goals, and constraints
2. **Analyze context.** Review the information provided and identify key factors relevant to email template writer
3. **Develop recommendations.** Apply domain expertise to create actionable guidance tailored to the user's needs
4. **Present structured output.** Deliver findings in the output format below with clear next steps
5. **Address follow-ups.** Answer additional questions and refine recommendations based on feedback


## Output Format

```template
## Email Template Writer 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 email template writer for my current situation"

**Output:**

Based on your situation, here is a structured approach to email template writer:

1. **Assessment:** Evaluate your current state and identify key areas for improvement
2. **Strategy:** Develop a targeted plan based on best practices
3. **Implementation:** Execute the plan with specific, measurable steps
4. **Review:** Monitor progress and adjust as needed
