writing-email-subjects
Installation
SKILL.md
Writing Email Subjects
Overview
Create a small set of subject line options that match the email’s intent and tone without adding new commitments or changing meaning.
When to Use
- You have the body (or a rough draft) but no subject line yet
- The current subject is vague (“Update”, “Quick question”) or too long
- You need variants for different tones (neutral vs. urgent) or audiences (internal vs. external)
When NOT to use
- The subject is fixed by a system/process (ticket IDs, legal notices)
Quick Reference
- Keep it short: ~3–8 words when possible
- Put the differentiator early (topic, date, action)
- Avoid spammy phrasing (ALL CAPS, excessive punctuation)
Implementation
- Identify the email’s purpose: inform / request / confirm / schedule.
- Extract the key noun(s) and the key action or date.
- Produce 5 options:
- 2 neutral/professional
- 2 slightly more direct/urgent (if appropriate)
- 1 very short “minimal” option
Common Mistakes
- Changing meaning: Don’t imply deadlines or decisions not stated in the email.
- Too generic: “Reminder” alone is rarely helpful—add topic/date.
Related skills
More from danbars/skills
writing-meeting-notes
Use when a meeting just occurred and notes need to be turned into a clear summary with decisions, action items, owners, and dates.
12triaging-bugs
Use when a bug report is ambiguous or incomplete and you need a consistent way to assess severity, impact, reproducibility, and the next investigative step.
10writing-release-notes
Use when changes are ready to ship and you need to communicate what changed, who it affects, and any required actions without exposing internal-only details.
9