Professional email
Skill openagentskills/betterskills/skills/communication/professional-email
Portable, open catalogue of agent skills for Cursor, Claude Code, Windsurf, Copilot, and other AI coding assistants.
npx -y skills add openagentskills/betterskills --skill professional-emailAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Drafts clear professional emails with appropriate tone, structure, and calls to action. Use when writing work email, follow-ups, apologies, requests, or stakeholder updates.
SKILL.md
1.3 KB, as published. Nobody here has run it
Professional Email
Gather (ask if missing)
- Recipient relationship (peer, manager, client, external)
- Goal (inform, request, apologize, escalate)
- Desired response and deadline
- Tone preference (neutral, warm, firm)
Structure
- Subject — Specific, ≤60 chars when possible
- Opening — Purpose in first sentence
- Body — Context → ask → rationale (short paragraphs)
- Close — Clear CTA + thanks/sign-off
Tone matrix
| Situation | Tone |
|---|---|
| Routine update | Neutral, concise |
| Request | Polite, specific deadline |
| Delay/bad news | Direct, accountable, next step |
| Escalation | Factual, no blame language |
Template
Subject: [Specific subject]
Hi [Name],
[One-sentence purpose.]
[2–4 short paragraphs with bullets if listing items.]
[Clear ask: "Could you confirm by Friday?"]
Thanks,
[Name]
Rules
- No passive-aggressive phrasing
- One main ask per email when possible
- Avoid jargon with external recipients
- Do not send on user's behalf — output draft only unless tool can send