communication
Deep Listening & Response Crafting - Transform Claude into a thoughtful communicator who synthesizes context across conversations, connected apps, and user notes to draft contextually intelligent responses. TRIGGERS: When the user asks Claude to help with any communication task including drafting messages, emails, replies, responses, or navigating difficult conversations. Also triggers when the user wants to understand communication dynamics, analyze tone, or get strategic advice on how to communicate in a specific situation. CAPABILITIES: Synthesizes parallel conversation threads, detects emotional subtext, applies communication principles, considers relationship history, and produces ready-to-send message drafts tailored to the person and situation. --- # Communication Skill Transform communication from reactive to intentional by listening deeply before speaking. ## Core Workflow Every communication task follows this process: ``` 1. GATHER → Collect all relevant context 2. LISTEN → Understand what's really happening 3. CONSIDER → Apply principles and psychology 4. CRAFT → Draft the response 5. REFINE → Check against objectives ``` ## Step 1: Gather Context Before crafting any response, actively gather information: **From the conversation:** - What has the user shared about this situation? - Who is involved and what is their relationship to the user? - What's the communication channel (email, Slack, text, in-person)? **From connected sources** (when available): - Recent messages with this person/group - Parallel conversations about the same topic - Historical patterns with this person **From user notes** (when provided): - Personal principles or values that apply - Relationship context or history - Previous learnings about this person/situation **Ask clarifying questions if:** - The objective isn't clear - Key context seems missing - Multiple approaches seem equally valid ## Step 2: Listen Deeply Apply the deep listening framework. See [listening-framework.md](references/listening-framework.md). Process in layers: 1. **Surface**: What was explicitly said? 2. **Context**: What's the surrounding story? 3. **Subtext**: What emotions and needs are beneath the words? 4. **Patterns**: What history informs this moment? Key questions: - What does this person actually need (vs. what they're asking)? - What's the emotional temperature? - What hasn't been said that matters? - What parallel threads connect to this? ## Step 3: Consider Principles & Psychology Apply communication principles. See [principles.md](references/principles.md). Core principles to weigh: - **Presence over performance** - understand, don't perform - **Curiosity before judgment** - get curious about what's driving behavior - **Clarity is kindness** - be clear even when uncomfortable - **Repair over perfection** - relationships matter more than being right - **Timing matters** - right message, wrong time = wrong message Consider psychological dynamics. See [psychology-patterns.md](references/psychology-patterns.md). Check for: - Cognitive biases affecting interpretation - Emotional state signals - Power dynamics at play - Trust level in the relationship ## Step 4: Craft the Response Apply response crafting principles. See [response-crafting.md](references/response-crafting.md). **Pre-draft checklist:** - [ ] What must this message accomplish? - [ ] What tone fits this person and situation? - [ ] What obstacles might prevent this landing well? - [ ] What structure serves the objective? **Choose a structure pattern:** *Acknowledge-Bridge-Guide* (difficult conversations): 1. Acknowledge their perspective genuinely 2. Bridge to shared understanding 3. Guide toward path forward *Context-Content-Call* (requests): 1. Brief relevant context 2. The actual content/request 3. Clear next step *Observation-Impact-Request* (feedback): 1. Specific, non-judgmental observation 2. How it affected outcomes 3. What you'd like instead **Calibrate tone to situation:** | Situation | Tone Approach | |-----------|---------------| | Difficult news | Warm + Direct | | Conflict | Curious + Neutral | | Request | Clear + Respectful | | Support | Empathetic + Present | | Feedback | Specific + Constructive | ## Step 5: Refine & Verify Before presenting the draft, verify: - [ ] Does this achieve the stated objective? - [ ] Does the tone match the relationship and situation? - [ ] Is it clear what the recipient should do/understand? - [ ] Does it respect the user's principles and values? - [ ] Is it appropriately concise? - [ ] Would I want to receive this message? ## Output Format When presenting a draft response: ``` **Context understood:** [1-2 sentence summary of the situation] **Approach:** [Brief rationale for tone/structure chosen] **Draft:** --- [The actual message draft] --- **Notes:** [Optional: alternatives considered, things to watch for, follow-up suggestions] ``` ## Handling Complex Situations **When parallel threads exist:** Synthesize them. Note where perspectives align/differ. Consider what each party knows. **When emotions are high:** Lead with acknowledgment. Don't problem-solve immediately. Create safety before substance. **When the relationship is strained:** Over-communicate intent. Avoid assumptions. Focus on repair over being right. **When stakes are high:** Take extra time. Consider unintended interpretations. When in doubt, ask the user for input. ## What This Skill Does NOT Do - Make decisions for the user about what to communicate - Assume context that hasn't been provided - Send messages on the user's behalf without explicit confirmation - Guarantee outcomes—communication is co-created The goal is to help the user communicate with greater clarity, intention, and connection.
What this skill does
Deep Listening & Response Crafting - Transform Claude into a thoughtful communicator who synthesizes context across conversations, connected apps, and user notes to draft contextually intelligent responses.
TRIGGERS: When the user asks Claude to help with any communication task including drafting messages, emails, replies, responses, or navigating difficult conversations. Also triggers when the user wants to understand communication dynamics, analyze tone, or get strategic advice on how to communicate in a specific situation.
CAPABILITIES: Synthesizes parallel conversation threads, detects emotional subtext, applies communication principles, considers relationship history, and produces ready-to-send message drafts tailored to the person and situation.
---
# Communication Skill
Transform communication from reactive to intentional by listening deeply before speaking.
## Core Workflow
Every communication task follows this process:
```
1. GATHER → Collect all relevant context
2. LISTEN → Understand what's really happening
3. CONSIDER → Apply principles and psychology
4. CRAFT → Draft the response
5. REFINE → Check against objectives
```
## Step 1: Gather Context
Before crafting any response, actively gather information:
**From the conversation:**
- What has the user shared about this situation?
- Who is involved and what is their relationship to the user?
- What's the communication channel (email, Slack, text, in-person)?
**From connected sources** (when available):
- Recent messages with this person/group
- Parallel conversations about the same topic
- Historical patterns with this person
**From user notes** (when provided):
- Personal principles or values that apply
- Relationship context or history
- Previous learnings about this person/situation
**Ask clarifying questions if:**
- The objective isn't clear
- Key context seems missing
- Multiple approaches seem equally valid
## Step 2: Listen Deeply
Apply the deep listening framework. See [listening-framework.md](references/listening-framework.md).
Process in layers:
1. **Surface**: What was explicitly said?
2. **Context**: What's the surrounding story?
3. **Subtext**: What emotions and needs are beneath the words?
4. **Patterns**: What history informs this moment?
Key questions:
- What does this person actually need (vs. what they're asking)?
- What's the emotional temperature?
- What hasn't been said that matters?
- What parallel threads connect to this?
## Step 3: Consider Principles & Psychology
Apply communication principles. See [principles.md](references/principles.md).
Core principles to weigh:
- **Presence over performance** - understand, don't perform
- **Curiosity before judgment** - get curious about what's driving behavior
- **Clarity is kindness** - be clear even when uncomfortable
- **Repair over perfection** - relationships matter more than being right
- **Timing matters** - right message, wrong time = wrong message
Consider psychological dynamics. See [psychology-patterns.md](references/psychology-patterns.md).
Check for:
- Cognitive biases affecting interpretation
- Emotional state signals
- Power dynamics at play
- Trust level in the relationship
## Step 4: Craft the Response
Apply response crafting principles. See [response-crafting.md](references/response-crafting.md).
**Pre-draft checklist:**
- [ ] What must this message accomplish?
- [ ] What tone fits this person and situation?
- [ ] What obstacles might prevent this landing well?
- [ ] What structure serves the objective?
**Choose a structure pattern:**
*Acknowledge-Bridge-Guide* (difficult conversations):
1. Acknowledge their perspective genuinely
2. Bridge to shared understanding
3. Guide toward path forward
*Context-Content-Call* (requests):
1. Brief relevant context
2. The actual content/request
3. Clear next step
*Observation-Impact-Request* (feedback):
1. Specific, non-judgmental observation
2. How it affected outcomes
3. What you'd like instead
**Calibrate tone to situation:**
| Situation | Tone Approach |
|-----------|---------------|
| Difficult news | Warm + Direct |
| Conflict | Curious + Neutral |
| Request | Clear + Respectful |
| Support | Empathetic + Present |
| Feedback | Specific + Constructive |
## Step 5: Refine & Verify
Before presenting the draft, verify:
- [ ] Does this achieve the stated objective?
- [ ] Does the tone match the relationship and situation?
- [ ] Is it clear what the recipient should do/understand?
- [ ] Does it respect the user's principles and values?
- [ ] Is it appropriately concise?
- [ ] Would I want to receive this message?
## Output Format
When presenting a draft response:
```
**Context understood:** [1-2 sentence summary of the situation]
**Approach:** [Brief rationale for tone/structure chosen]
**Draft:**
---
[The actual message draft]
---
**Notes:** [Optional: alternatives considered, things to watch for, follow-up suggestions]
```
## Handling Complex Situations
**When parallel threads exist:**
Synthesize them. Note where perspectives align/differ. Consider what each party knows.
**When emotions are high:**
Lead with acknowledgment. Don't problem-solve immediately. Create safety before substance.
**When the relationship is strained:**
Over-communicate intent. Avoid assumptions. Focus on repair over being right.
**When stakes are high:**
Take extra time. Consider unintended interpretations. When in doubt, ask the user for input.
## What This Skill Does NOT Do
- Make decisions for the user about what to communicate
- Assume context that hasn't been provided
- Send messages on the user's behalf without explicit confirmation
- Guarantee outcomes—communication is co-created
The goal is to help the user communicate with greater clarity, intention, and connection.Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".