strategic-communication
Strategic Communication Skill
Built on Chris Voss's FBI hostage negotiation approach: tactical empathy and emotion labeling as your primary tools, with a warm "positive & playful" default tone.
When to Use This Skill
- Negotiating: Rentals, salaries, contracts, terms with vendors/hotels
- Making asks: Requesting resources, time, help from colleagues
- Declining: Saying no to requests, opportunities, or offers
- Changing plans: Backing out or modifying commitments
- Navigating tension: Any situation where emotions are running high
- Refining messages: When your draft feels off-tone or unclear
The Foundation: Tactical Empathy + Labeling
Rule from Voss: Every fourth thing you say should be a label.
- Recognize their perspective - imagine yourself in their situation
- Identify their emotions - what are they feeling and why?
- Label those emotions explicitly - "It seems like..." / "It sounds like..." / "You're probably..."
This is not manipulation. This is demonstrating genuine understanding.
Your Default Mode: Positive & Playful
From Voss: "Voice of an easygoing, good-natured person. Relax and smile while talking."
Core Workflow
Step 1: Understand Their Emotional Landscape
Before drafting, ask yourself:
- How does this situation affect them emotionally?
- What are they afraid of or concerned about?
- How have my actions impacted them?
- What do they actually need?
Step 2: Lead With Tactical Empathy
Structure: [Label their emotion] + [Show you understand] + [Your message]
Example: "You're probably frustrated that I'm changing plans last minute, especially since you took time off. I'm sorry about that - something unexpected came up."
Step 3: Use Calibrated Questions
After acknowledging emotions, use "How" and "What" questions:
- "How would [your need] work for you?"
- "What would you need to make this work?"
Avoid: "Why" questions (accusatory), "Can you" questions (easy to refuse)
Step 4: Listen for "That's Right" Not "You're Right"
- "That's Right" = Genuine agreement, they feel understood
- "You're Right" = Dismissive, they want you to go away
Step 5: Reality Check
- Did I acknowledge how this affects them emotionally?
- Am I being genuine about their concerns?
- Am I staying warm and collaborative in tone?
Key Principles From Voss
1. Label Emotions Constantly Pattern: "It seems like..." / "It sounds like..." / "You're probably..." Then pause and let them respond.
2. Accusation Audit - Name The Worst First Say what they might think about you before they can: "You're going to think I'm being flaky..."
3. "I'm Sorry" Is a Tool, Not Weakness Apologize for your impact on them, not for having needs.
4. Three Types of "Yes" Only Commitment Yes matters. Use no-oriented questions: "Would it be crazy to...?"
5. Slow Down and Smile Creates trustworthiness and combats defensiveness.
Reference Files
references/frameworks.md- Deep dive on tactical empathy, BATNA/ZOPA, interests vs positions, power dynamicsreferences/patterns.md- Before/after examples, templates, red flags, tone calibrationreferences/scenarios.md- Common scenarios: rental, salary, work requests, backing out, saying no
Tips for Effective Use
- Label emotions every fourth thing you say
- Lead with accusation audits when changing plans
- Slow down when you feel rushed
- Smile while writing - it changes your tone
- Trust "that's right" over "you're right"
- Apologize when your actions affect them - this builds trust
- Your collaborative instincts are usually right
- Practice on low-stakes situations first
- People are emotional first, rational second - address emotions before facts
More from yulonglin/dotfiles
anthropic-style
Anthropic visual style for plots, diagrams, slides, and web. Use when creating any visual output that should have Anthropic's look-and-feel — matplotlib charts, TikZ diagrams, HTML/CSS, or presentations.
29custom-compact
Compact current work with optional focus using agent-context-summariser
14commit
Commit current work with optional message. Handles git status/diff checking and message formatting.
12my-insights
Run custom usage analytics on all Claude Code sessions
12commit-push-sync
This skill should be used when the user asks to "commit and push", "commit push", "sync changes", "push changes", "commit and sync", or "update remote". Handles the full workflow of committing changes, pulling with rebase, and pushing to remote.
11skill-installer
Install Codex skills into $CODEX_HOME/skills from a curated list or a GitHub repo path. Use when a user asks to list installable skills, install a curated skill, or install a skill from another repo (including private repos).
4