Professional Communicator Skill
Goal
Convert raw, emotional, rushed, or unclear thoughts into professional communications that are clear, appropriately diplomatic, and achieve the desired outcome — without sounding robotic or corporate-hollow.
Core Principles
- Purpose over politeness: Every word should serve the communication goal. Don't add filler politeness that dilutes the message.
- Appropriate register: Match the relationship (internal/external, peer/manager/client, formal/informal).
- One clear ask: Every professional message should have one primary purpose. If there are multiple, structure them clearly.
- Empathy without weakness: Acknowledge the other party's perspective without conceding things that shouldn't be conceded.
Steps
1. Understand the situation
Before writing a single word, clarify:
- Who is the recipient? (manager, direct report, client, vendor, colleague)
- What is the desired outcome? (approval, information, apology, rejection, escalation)
- What's the relationship tone? (formal, collegial, tense, new)
- What's the urgency? (FYI, needs response today, time-sensitive)
If any of these are unclear from the user's message, ask before writing.
Success criteria: You can write the subject line before writing the body.
2. Choose the appropriate tone
| Situation |
Tone |
| Client complaint |
Empathetic, solution-focused, formal |
| Rejecting a request |
Diplomatic, brief, clear reason |
| Escalating an issue |
Factual, non-accusatory, solution-oriented |
| Following up |
Friendly but direct, no guilt-tripping |
| Delivering bad news |
Direct, empathetic, forward-looking |
| Negotiating |
Collaborative, value-focused |
3. Draft the message
Structure:
- Opening — acknowledge context or relationship (1 sentence max — no "I hope this email finds you well" filler)
- Core message — the ask, decision, or information (2–4 sentences)
- Supporting context — only what the recipient needs to act or understand (optional)
- Clear next step — what you need from them, or what happens next (1 sentence)
- Closing — brief, professional (not "Thanking you in advance" — that's presumptuous)
Success criteria: Recipient knows what to do after reading the first paragraph.
4. Review for traps
Check for:
- Passive-aggressive phrasing: "As I mentioned before..." → remove or rephrase
- Emotional leakage: Frustration that should stay internal
- Ambiguity: Any sentence that could be misread
- Length: If it's longer than 200 words, cut. Busy people don't read long emails.
5. Deliver with subject line
Always provide:
- A suggested subject line
- The message body
- A one-line note on the strategic choice made (e.g., "Led with their concern before stating the decision — makes the 'no' easier to accept")
Why/Failure Modes
[TODO: Explain the reasoning behind this skill's approach and common failure modes to avoid.]
Standalone vs Supercharged
[TODO: Describe how this skill works on its own vs when combined with other tools/context.]
Cross-References
[TODO: Link to other relevant skills or documentation.]
1---2name: professional-communicator3description: Transform raw thoughts into polished, diplomatically precise professional emails and messages4---56# Professional Communicator Skill78## Goal9Convert raw, emotional, rushed, or unclear thoughts into professional communications that are clear, appropriately diplomatic, and achieve the desired outcome — without sounding robotic or corporate-hollow.1011## Core Principles12- **Purpose over politeness**: Every word should serve the communication goal. Don't add filler politeness that dilutes the message.13- **Appropriate register**: Match the relationship (internal/external, peer/manager/client, formal/informal).14- **One clear ask**: Every professional message should have one primary purpose. If there are multiple, structure them clearly.15- **Empathy without weakness**: Acknowledge the other party's perspective without conceding things that shouldn't be conceded.1617## Steps1819### 1. Understand the situation20Before writing a single word, clarify:21- **Who** is the recipient? (manager, direct report, client, vendor, colleague)22- **What** is the desired outcome? (approval, information, apology, rejection, escalation)23- **What's the relationship tone?** (formal, collegial, tense, new)24- **What's the urgency?** (FYI, needs response today, time-sensitive)2526If any of these are unclear from the user's message, ask before writing.2728**Success criteria**: You can write the subject line before writing the body.2930### 2. Choose the appropriate tone31| Situation | Tone |32|-----------|------|33| Client complaint | Empathetic, solution-focused, formal |34| Rejecting a request | Diplomatic, brief, clear reason |35| Escalating an issue | Factual, non-accusatory, solution-oriented |36| Following up | Friendly but direct, no guilt-tripping |37| Delivering bad news | Direct, empathetic, forward-looking |38| Negotiating | Collaborative, value-focused |3940### 3. Draft the message41Structure:421. **Opening** — acknowledge context or relationship (1 sentence max — no "I hope this email finds you well" filler)432. **Core message** — the ask, decision, or information (2–4 sentences)443. **Supporting context** — only what the recipient needs to act or understand (optional)454. **Clear next step** — what you need from them, or what happens next (1 sentence)465. **Closing** — brief, professional (not "Thanking you in advance" — that's presumptuous)4748**Success criteria**: Recipient knows what to do after reading the first paragraph.4950### 4. Review for traps51Check for:52- **Passive-aggressive phrasing**: "As I mentioned before..." → remove or rephrase53- **Emotional leakage**: Frustration that should stay internal54- **Ambiguity**: Any sentence that could be misread55- **Length**: If it's longer than 200 words, cut. Busy people don't read long emails.5657### 5. Deliver with subject line58Always provide:59- A suggested subject line60- The message body61- A one-line note on the strategic choice made (e.g., "Led with their concern before stating the decision — makes the 'no' easier to accept")626364## Why/Failure Modes6566[TODO: Explain the reasoning behind this skill's approach and common failure modes to avoid.]6768## Standalone vs Supercharged6970[TODO: Describe how this skill works on its own vs when combined with other tools/context.]7172## Cross-References7374[TODO: Link to other relevant skills or documentation.]
furkangonel