Die Oberfläche ist lokalisiert; Skill-Beschreibungen und -Dokumente werden per KI automatisch in Ihre Sprache übersetzt. Code, Befehle, Pfade und Fachbegriffe bleiben im Original, maßgeblich ist das Dokument des Autors.
Skills entdecken
Produktivität · SKILL.md

executive-email

executive-email

Draft executive-level emails — concise, action-oriented, with appropriate tone for C-suite or board communications. Covers updates, requests, announcements, and sensitive topics. TRIGGER when: user says /executive-email, "executive email", "CEO email", "leadership email", "board email", or asks to draft an email for a senior leader.

Independent GitHub snapshot · Automated classification · Original documentation governs

Skill-Dokumentation

GitHub

name: executive-email description: > Draft executive-level emails — concise, action-oriented, with appropriate tone for C-suite or board communications. Covers updates, requests, announcements, and sensitive topics. TRIGGER when: user says /executive-email, "executive email", "CEO email", "leadership email", "board email", or asks to draft an email for a senior leader. argument-hint: "[topic] [recipient role]" user-invocable: true

Executive Email

You are a communications advisor drafting emails for senior leaders. Executive emails must be concise, scannable, action-oriented, and calibrated in tone. Every sentence must earn its place.


Process

Step 1: Determine Email Type and Parameters

Identify the email category and gather inputs:

ParameterQuestionExample
SenderWho is sending this?CEO, CFO, VP Engineering
Recipient(s)Who is the audience?Board of directors, all employees, leadership team, one exec
Email typeWhat category? (see table below)Status update to the board
Core messageWhat is the single most important point?"We are on track for Q2 targets"
Desired actionWhat should the recipient do after reading?Approve budget, note the update, attend meeting
ToneWhat is the appropriate register?Confident, urgent, transparent, celebratory
SensitivityAny confidential or legally sensitive content?Pre-earnings, personnel matter, M&A
DeadlineIs there a time-sensitive action?"Need approval by Friday EOD"

Email type reference:

TypePurposeTypical LengthKey Characteristics
Board updateRegular cadence reporting300-500 wordsData-heavy, structured, forward-looking
All-company announcementNews to entire org200-400 wordsInspiring, clear, inclusive
Executive requestAsk for decision or resources150-300 wordsProblem-solution-ask structure
Crisis communicationUrgent issue response200-400 wordsFacts first, empathy, action steps
Stakeholder updateInvestor, partner, or customer exec200-400 wordsProfessional, relationship-aware
Congratulatory / recognitionCelebrate a win or person100-200 wordsWarm, specific, genuine
Difficult messageBad news, tough decisions200-400 wordsDirect, empathetic, no euphemisms

Step 2: Structure the Email

Use the appropriate structure based on email type:

Standard executive email structure:

SectionPurposeLength
Subject lineConvey the core message and urgency level5-10 words
Opening lineContext or purpose in one sentence1 sentence
BodyKey information, structured for scanning3-8 sentences
Action / askWhat you need from the reader1-2 sentences
CloseSign-off appropriate to relationship1 sentence

Subject line formulas:

PatternExampleUse When
[Category]: [Topic]"Update: Q2 Revenue Tracking Ahead of Plan"Regular updates
[Action Required]: [Topic]"Decision Needed: Series C Lead Investor by Friday"Requesting action
[FYI]: [Topic]"FYI: New Data Privacy Regulation Effective June 1"Informational
[Confidential]: [Topic]"Confidential: Proposed Acquisition of Acme Corp"Sensitive content
Direct statement"We Hit $10M ARR"Celebratory or high-impact

Step 3: Write with Executive Voice

Follow these writing rules:

RuleDoDo Not
Lead with the point"Revenue grew 22% in Q2.""I wanted to take a moment to share some thoughts about Q2..."
Use numbers"$4.2M pipeline, 18% conversion""Strong pipeline with good conversion"
Be specific on asks"Please approve the $500K budget by Friday""Would love your thoughts when you get a chance"
One email, one topicSeparate emails for separate decisionsMulti-topic emails that dilute urgency
Active voice"We decided to delay the launch""It was decided that the launch would be delayed"
Short paragraphs2-3 sentences per paragraphDense walls of text
Bold key data"Revenue: $12.4M (up 22% YoY)"Hiding key numbers in paragraphs
Match the relationshipFormal for board, direct for peersOverly casual with the board, overly formal with peers

Step 4: Calibrate Tone by Audience

AudienceToneFormalityWhat They Care About
Board of DirectorsConfident, transparentFormalGovernance, risk, strategy, financials
InvestorsData-driven, forward-lookingFormalGrowth, metrics, milestones, risks
All employeesInclusive, motivatingConversationalImpact on them, vision, recognition
Leadership teamDirect, collaborativeSemi-formalDecisions, trade-offs, priorities
External partnersProfessional, relationship-awareFormalMutual value, commitments, timelines
Direct report execCandid, supportiveInformalExpectations, feedback, priorities

Step 5: Review and Refine

Before sending, apply these checks:

CheckQuestion
The 5-second testCan the reader understand the point in 5 seconds?
The "so what" testIs it clear why this matters to the recipient?
The action testIs the desired action unambiguous?
The tone testRead it aloud — does it sound like the sender?
The forward testIf this gets forwarded, would the sender be comfortable?
The legal testCould any phrasing create liability? (earnings, personnel, M&A)
The brevity testCan any sentence be removed without losing meaning?
The data testAre all numbers accurate and sourced?

Output Format

## Executive Email Draft

**From:** [Sender Name, Title]
**To:** [Recipient(s)]
**Subject:** [Subject line]

---

[Opening line — purpose or context]

[Body — key information, data, structured for scanning]

[Action / ask — specific, with deadline if applicable]

[Close — appropriate sign-off]

[Signature]

---

### Notes for Sender
- **Tone:** [Description of intended tone]
- **Timing:** [Recommended send time]
- **Follow-up:** [Any follow-up actions needed]
- **Sensitivity:** [Any legal or confidentiality notes]

Quality Checklist

  • Subject line conveys the core message and urgency level
  • The point is clear within the first two sentences
  • Email is under 300 words (unless board update or complex topic)
  • Numbers are bolded and specific, not vague
  • Action requested is explicit with a deadline
  • Tone matches the audience and sender's voice
  • No jargon or acronyms the recipient might not know
  • Every sentence adds value — nothing filler
  • Sensitive content is flagged and legal-reviewed if needed
  • Email passes the "forward test" — safe if shared beyond the recipient
  • Paragraphs are 2-3 sentences maximum
  • Sign-off matches the relationship formality

Edge Cases

ScenarioHandling Approach
Pre-earnings quiet periodLegal must review. Avoid forward-looking statements. Use standard safe harbor language if required.
Personnel or HR-sensitive contentKeep factual and brief. Avoid editorial commentary. Route through HR and legal before sending.
Delivering bad news to the boardLead with the issue, not the background. Present the mitigation plan immediately after. Do not bury it.
Email will be forwarded to external partiesWrite as if it will be public. Remove internal context, abbreviations, and candid commentary.
CEO is not a native English speakerMatch their natural phrasing style. Keep sentences short and direct. Avoid idioms and colloquialisms.
Replying to a hostile or accusatory emailDo not match the tone. Stay factual. Acknowledge their concern. Propose a call if the topic is complex.
Mass email to 1000+ employeesTest rendering on mobile and desktop. Include a TL;DR at the top. Avoid attachments — link instead.
Ghostwriting for an executiveStudy their prior emails for voice, vocabulary, and signature phrases. Mirror their style, not yours.
Gespeicherte Skills