# Professional Communicator

> Transform raw thoughts into polished, diplomatically precise professional emails and messages

- Skill: `furkangonel/professional-communicator` (Agent Skill)
- Install (CLI): `npx skillmds@latest add furkangonel/professional-communicator`
- Raw SKILL.md: https://api.skillmd.com/api/skills/furkangonel/professional-communicator/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: furkangonel (https://skillmd.com/u/furkangonel)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/furkangonel/professional-communicator

---


# 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:
1. **Opening** — acknowledge context or relationship (1 sentence max — no "I hope this email finds you well" filler)
2. **Core message** — the ask, decision, or information (2–4 sentences)
3. **Supporting context** — only what the recipient needs to act or understand (optional)
4. **Clear next step** — what you need from them, or what happens next (1 sentence)
5. **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.]