Professional email

Rewrite or draft emails that are clear, kind, and specific about the next step.

Install in Claude Code

Create a folder whose name matches the skill name field (professional-email/). Save the text below as SKILL.md inside it. Personal skills go in ~/.claude/skills/professional-email/. Project skills go in .claude/skills/professional-email/. Claude Code discovers them from the filesystem.

Upload on claude.ai

Zip the skill folder (the zip should contain the folder, which contains SKILL.md) and upload it in Claude’s Skills settings. Anthropic’s current platform docs list custom uploads on Pro, Max, Ultra, Team, and Enterprise plans when code execution is enabled. Check the Claude Help Center for the latest plan details. Read the files before you turn a skill on.

Use with the Claude API

Custom API Skills are uploaded through the Skills API and referenced with the code execution tool. Skills do not sync automatically from Claude Code or claude.ai — install this folder again on the surface where you need it. See Anthropic’s Agent Skills overview.

---
name: professional-email
description: Drafts or rewrites professional emails with a clear request, the right tone, and a specific next step. Use when the user asks to write, shorten, soften, or strengthen an email, outreach note, or reply.
---

# Professional email

## Goal
Help the user send an email that the recipient can answer quickly. Preserve the user's facts and intent. Improve structure, tone, and specificity.

## Ask if missing
If these are not clear, ask before drafting: recipient, relationship, goal, tone (for example warm, firm, or formal), deadline, and any facts that must appear unchanged.

## Workflow
1. Restate the goal in one line: inform, request, decline, follow up, apologize, or escalate.
2. Keep every factual claim the user supplied. Do not invent dates, prices, names, or attachments.
3. Lead with the point. Put context second.
4. Make the ask specific: what you need, by when, and how to reply.
5. Offer 2 versions when tone is sensitive (for example a decline or an escalation): a direct version and a warmer version.
6. Include a subject line of 6–9 words.

## Output template
```markdown
**Subject:**

**Version A — [tone]**
[email body]

**Why this works**
-
```

## Rules
- Do not add legal threats, fake urgency, or implied authority the user did not claim.
- Do not include Bcc strategies that hide participants in a way that would surprise the user.
- Avoid hollow intensifiers and corporate filler: *circle back*, *synergy*, *just checking in* as the only point.
- If the user's draft is already strong, make small edits and say what you changed.
- For apologies, own the issue, state the fix, and do not blame the recipient.

You may copy and adapt this free skill for personal or commercial use. If you republish it, please credit Skillory with a link. Audit any skill — including this one — before enabling it in an environment with access to private data.

Related skills

Claude Engineering SKILL.md

Changelog writer

Turn commits and merged PRs into a readable changelog grouped the way users scan it.

Open skill →

Claude Engineering SKILL.md

Code review

Review a diff like a careful teammate: correctness first, then security, then clarity.

Open skill →

Claude Engineering SKILL.md

Git commit messages

Write conventional commit messages from a staged diff, without fluff or invented ticket IDs.

Open skill →