See It In Action

1 turns·claude

The project codebase is in your current working directory. Explore the files to understand the code before making changes. need a client update email asap for our biggest customer after the payment outage is fixed, they want it before their 4pm review

Here's a draft ready to send before the 4pm review:

Subject: [RESOLVED] Payment Processing Outage — Full Service Restored

Hi [Customer Name],

I wanted to reach out directly to confirm that the payment processing issue has been fully resolved and all systems are operating normally.

What happened: Earlier today, our payment processing service experienced an outage that temporarily prevented transactions from being completed. The root cause was [a configuration issue in our payment gateway / a disruption in our third-party processor connection — update as appropriate].

What we did:

Identified and isolated the issue within [X] minutes of detection
Deployed a fix and verified full transaction processing capability
Confirmed no transactions were lost — any pending payments have been processed successfully

What we're doing to prevent recurrence:

Implementing additional monitoring and automated failover for the affected component
Conducting a full post-incident review this week, and we'll share the findings with your team
Adding redundancy to the specific failure point identified

Current status: All payment services are fully operational. No action is required on your end.

We understand the critical role payment reliability plays in your operations, and we take this seriously. Please don't hesitate to reach out if you have any questions ahead of your review this afternoon — I'm available by email or phone.

Thank you for your continued partnership.

Best regards, [Your Name] [Title] [Phone Number]

A few things to customize before sending:

[Customer Name] — swap in the contact's name
Root cause — fill in the specific technical cause (I left a placeholder)
[X] minutes — insert the actual detection-to-fix timeline
Your sign-off details — name, title, direct phone number

If you give me the specifics (customer name, root cause, timeline), I can finalize it for you.

Claude Sonnet 4.6

SKILL.md

Email Composer

Quick start

Provide context and purpose, and I'll draft an appropriate email.

What I need:

Purpose of email (request, follow-up, announcement, etc.)
Recipient relationship (colleague, customer, manager, vendor)
Key points to include
Desired tone (formal, casual, urgent, friendly)

Email structure

Standard professional email format:

Subject: [Clear, specific subject line]

[Greeting],

[Opening - context/purpose]

[Body - main points]

[Closing - call to action]

[Sign-off]
[Your name]

Common email types

Request for information

Subject: Question about Q4 project timeline

Hi [Name],

I hope this email finds you well. I'm reaching out regarding the Q4 product launch timeline.

Could you provide an update on:
- Current progress on feature development
- Expected completion date for testing phase
- Any blockers or dependencies we should be aware of

This will help us coordinate with the marketing team for the launch materials.

Thanks in advance for your help!

Best regards,
[Your name]

Follow-up email

Subject: Following up: Proposal for new payment system

Hi [Name],

I wanted to follow up on the payment system proposal I sent last week. I understand you're busy, so I wanted to make sure it didn't get lost in your inbox.

To recap, the proposed system would:
- Reduce transaction fees by 30%
- Integrate with existing accounting software
- Improve customer checkout experience

I'd be happy to schedule a brief call to discuss any questions you might have.

Looking forward to hearing from you.

Best,
[Your name]

Technical update

Subject: API Maintenance Window - [Date]

Team,

This is a reminder that we'll be performing scheduled maintenance on our API infrastructure on [Date] from [Time] to [Time] [Timezone].

During this window:
- API endpoints will be unavailable
- Database will be upgraded to v14
- SSL certificates will be renewed

Expected downtime: 2 hours

What you need to do:
- Notify your users of the planned downtime
- Ensure retry logic is in place for API calls
- Monitor your application after maintenance completes

If you have any concerns or conflicts with this schedule, please let me know by [Date].

Technical details available in our status page: [link]

Thanks,
[Your name]

Customer support

Subject: Re: Issue with order #12345

Hi [Customer name],

Thank you for reaching out about your order. I'm sorry to hear you're experiencing this issue.

I've looked into your order (#12345) and found the following:

[Explanation of the issue]

To resolve this, I've:
- [Action taken 1]
- [Action taken 2]

You should see [expected outcome] within [timeframe].

If you continue to experience any problems, please don't hesitate to reply to this email or call us at [phone number].

We appreciate your patience and understanding.

Best regards,
[Your name]
Customer Support Team

Meeting request

Subject: Meeting request: Discuss database migration strategy

Hi [Name],

I'd like to schedule a meeting to discuss our approach for the upcoming database migration.

Agenda items:
- Review migration timeline and milestones
- Discuss rollback strategy
- Identify potential risks and mitigation plans
- Assign team responsibilities

Estimated duration: 45 minutes

I'm available:
- Monday 2-4 PM
- Wednesday 10 AM - 12 PM
- Friday 1-3 PM

Please let me know what works best for you, or feel free to suggest alternative times.

Best,
[Your name]

Tone guidelines

Formal tone

Use complete sentences
Avoid contractions
Professional language
Proper titles (Dr., Mr., Ms.)

Casual tone

Contractions acceptable
Conversational language
Still professional
First names

Urgent tone

Clear subject line with [URGENT] or [ACTION REQUIRED]
Bold key points
Explicit deadline
Direct call to action

Subject line best practices

Good subject lines:

"Action required: Submit timesheet by Friday"
"Q4 Sales Report - Review needed"
"Meeting rescheduled: Project kickoff now Thursday"
"Quick question about deployment process"

Bad subject lines:

"Update"
"Question"
"Hello"
"Following up"

Email etiquette

DO:

Respond within 24 hours (even if just to acknowledge)
Use clear, specific subject lines
Keep it concise
Proofread before sending
Include relevant context
Use bullet points for multiple items
End with clear call to action

DON'T:

Use ALL CAPS
Over-use exclamation marks!!!
Mark everything as urgent
Reply all unless necessary
Send when emotional
Include unnecessary recipients
Forget attachments mentioned in email

Templates by scenario

Decline request politely

Subject: Re: [Original subject]

Hi [Name],

Thank you for thinking of me for [request/opportunity].

Unfortunately, I won't be able to [participate/help/attend] due to [brief reason - optional]. However, I'd recommend [alternative suggestion if applicable].

I appreciate your understanding, and I hope we can collaborate on future opportunities.

Best regards,
[Your name]

Apologize for mistake

Subject: Apology and correction: [Issue]

Hi [Name],

I'm writing to apologize for [specific mistake]. This was an error on my part, and I take full responsibility.

To correct this:
- [Action 1 already taken]
- [Action 2 in progress]
- [Preventive measure for future]

I understand this may have caused [impact], and I'm committed to ensuring it doesn't happen again.

If you have any concerns or questions, please don't hesitate to reach out.

Sincerely,
[Your name]

Share good news

Subject: Great news: [Achievement/milestone]

Team,

I'm excited to share that we've [accomplished goal]!

This success is thanks to:
- [Team/person contribution 1]
- [Team/person contribution 2]

Impact:
- [Metric improvement]
- [Business benefit]

Thank you all for your hard work and dedication. Let's keep up the momentum!

Cheers,
[Your name]

Closing phrases by context

Formal:

Sincerely
Best regards
Respectfully
Cordially

Professional:

Best
Thanks
Kind regards
Regards

Casual:

Cheers
Thanks!
Talk soon
Best

Email composition checklist

FAQ

What does Email Composer do?

Draft professional emails for various contexts including business, technical, and customer communication. Use when the user needs help writing emails or composing professional messages.

When should I use Email Composer?

Use it when you need a repeatable workflow that produces text response.

What does Email Composer output?

In the evaluated run it produced text response.

How do I install or invoke Email Composer?

npx skills add https://github.com/davila7/claude-code-templates --skill email-composer

Which agents does Email Composer support?

Claude Code

What tools, channels, or permissions does Email Composer need?

It uses no extra tools; channels commonly include text; permissions include no explicit permission scopes.

Is Email Composer safe to install?

Static analysis marked this skill as low risk; review side effects and permissions before enabling it.

How is Email Composer different from an MCP or plugin?

A skill packages instructions and workflow conventions; tools, MCP servers, and plugins are dependencies the skill may call during execution.

Does Email Composer outperform not using a skill?

About Email Composer

When to use Email Composer

When you need to draft or revise a professional email quickly. When you want the right tone for requests, follow-ups, updates, or support replies. When you need structured email templates for common workplace scenarios.

When Email Composer is not the right choice

When the task is to actually send email through an email service or API. When you need legal review or highly specialized compliance-approved messaging.

What it produces

Produces text response.

Install

npx skills add https://github.com/davila7/claude-code-templates --skill email-composer

Invoke: Ask Claude Code to use Email Composer for the task.