Follow email conventions that keep you professional and considerate: CC/BCC, reply-all, response times, and threading. Use when unsure of the norms, or to avoid the mistakes that annoy colleagues and burn goodwill.
Scanned 9/5/2026
Install to Claude Code
npx -y skills add Amey-Thakur/AI-SKILLS --skill email-etiquette --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Email Etiquette?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/amey-thakur-email-etiquette)More formats (shields.io, HTML) on the badges page.
---
name: email-etiquette
description: "Follow email conventions that keep you professional and considerate: CC/BCC, reply-all, response times, and threading. Use when unsure of the norms, or to avoid the mistakes that annoy colleagues and burn goodwill."
---
# Email etiquette
Email etiquette is the set of small conventions that mark you as
considerate and professional, and whose violation quietly costs goodwill.
The rules are mostly about respecting other people's time and attention:
who you copy, when you reply-all, and how fast you respond.
## Method
1. **Use To, CC, and BCC deliberately.** To is for the people who must act;
CC is for those who need to be aware but need not respond; BCC is for
privacy (hiding a large recipient list) or discreetly dropping someone
from a thread, not for secretly looping in third parties (which
backfires when they reply-all). Copying people needlessly buries them in
noise.
2. **Think before reply-all.** Reply only to the sender unless everyone on
the thread genuinely needs your message. "Thanks!" or "+1" to twenty
people is the classic reply-all annoyance. When you do reply-all,
confirm the recipient list is still appropriate.
3. **Respect response-time norms.** Reply within the expectation for the
context (same-day for most work email, faster for urgent, and set an
out-of-office when away; see async-communication). If a full answer will
take time, a quick "got it, will reply by Thursday" prevents the sender
from wondering (see email-follow-ups from the other side).
4. **Keep threads coherent.** Reply within the existing thread for a
continuing conversation (so context stays together), and start a new
thread with a fresh subject when the topic changes (see
email-subject-lines). Do not hijack an unrelated thread for a new topic;
the reader loses the history.
5. **Mind tone and permanence.** Email lacks vocal cues, so neutral can
read as cold and a joke can misfire; err toward warmth and clarity (see
email-tone). And remember email is forwardable and permanent: do not
write what you would not want seen widely, and never handle a heated
conflict over email.
6. **Handle attachments and links considerately.** Mention the attachment
in the body (and actually attach it: the forgotten-attachment follow-up
is universal), keep files reasonably sized or share a link, and give
links context so the reader knows what they are clicking (link safety
matters to them too).
## Boundaries
- Norms vary by culture, company, and relationship: some workplaces are
formal, others chat-casual; read the room and mirror the sender's
register rather than applying one rulebook (see email-tone,
audience-adaptation).
- Etiquette is about consideration, not rigid formality; a quick casual
reply to a close colleague needs none of the ceremony a first email to
an executive does.
- These are conventions, not laws; the underlying principle (respect the
recipient's time and attention) resolves the cases the rules do not
cover.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!