Back to skills
SkillHub ClubShip Full StackFull Stack
communication
$3a
Packaged view
This page reorganizes the original catalog entry around fit, installability, and workflow context first. The original raw source lives below.
Stars
3,084
Hot score
99
Updated
March 20, 2026
Overall rating
C5.2
Composite score
5.2
Best-practice grade
C56.0
Install command
npx @skill-hub/cli install openclaw-skills-communication-skill
Repository
Best for
Primary workflow: Ship Full Stack.
Technical facets: Full Stack.
Target audience: everyone.
License: Unknown.
Original source
Catalog source: SkillHub Club.
Repository owner: openclaw.
This is still a mirrored public skill entry. Review the repository before installing into production workflows.
What it helps with
- Install communication into Claude Code, Codex CLI, Gemini CLI, or OpenCode workflows
- Review https://github.com/openclaw/skills before adding communication to shared team environments
- Use communication for development workflows
Works across
Claude CodeCodex CLIGemini CLIOpenCode
Favorites: 0.
Sub-skills: 0.
Aggregator: No.
Original source / Raw SKILL.md
---
name: communication
description: |
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.
---
## Referenced Files
> The following files are referenced in this skill and included for context.
### references/listening-framework.md
```markdown
# Deep Listening Framework
## The Listening Hierarchy
Process inputs in this order:
### 1. Surface Layer - What Was Said
- Explicit words and statements
- - Direct requests or questions
- - Stated facts and positions
- ### 2. Context Layer - The Surrounding Story
- - What conversations preceded this?
- - Who else is involved?
- - What's the timeline and urgency?
- ### 3. Subtext Layer - What's Beneath
- - What emotions underlie the words?
- - What fears or concerns aren't stated?
- - What does this person actually need?
- ### 4. Pattern Layer - Historical Intelligence
- - How does this person typically communicate?
- - What patterns work well with them?
- - What past experiences shape their stance?
- ## Emotional State Detection
- | Emotion | Signals | Response Approach |
- |---------|---------|-------------------|
- | Frustration | Short responses, escalating language | Acknowledge, don't defend |
- | Anxiety | Questions, hedging, seeking reassurance | Provide clarity and safety |
- | Excitement | Rapid messages, expansive ideas | Match energy, build momentum |
- | Withdrawal | Delayed responses, brevity | Create space, reduce pressure |
- ## The "Unsaid" Checklist
- Before responding, consider:
- - What elephant in the room isn't being addressed?
- - What outcome does this person really want?
- - What are they afraid of happening?
- - What would make them feel truly heard?
```
### references/principles.md
```markdown
# Communication Principles
## Core Principles
### 1. Presence Over Performance
Focus on truly understanding, not on sounding smart or being right. The goal is connection and clarity, not winning.
### 2. Curiosity Before Judgment
When something seems off, get curious about what's driving it rather than jumping to conclusions. There's always context you don't have.
### 3. Clarity is Kindness
Being clear—even when it's uncomfortable—respects the other person's time and intelligence. Vagueness often creates more problems than directness.
### 4. Repair Over Perfection
Missteps happen. The quality of a relationship is determined by how ruptures are repaired, not by avoiding them entirely.
### 5. Timing Matters
The right message at the wrong time is the wrong message. Consider when someone is ready to hear something.
## First Principles Thinking
When facing a communication challenge:
**Step 1: Strip away assumptions**
- What do I actually know vs. what am I assuming?
- **Step 2: Identify the core need**
- - What does each party fundamentally need?
- **Step 3: Challenge conventions**
- - "This is how it's always done" isn't a reason
- **Step 4: Build up from truth**
- - Start with what's verifiably true
- - Add only what's necessary
- ## User-Defined Principles
- The skill should also incorporate principles specific to the user's context:
- - Professional values they hold
- - Relationship-specific boundaries
- - Cultural or organizational norms
- - Personal communication style preferences
```
### references/psychology-patterns.md
```markdown
# Psychology & Human Behavior Patterns
## Cognitive Biases in Communication
### Biases Affecting Message Senders
- **Curse of Knowledge**: Assuming others know what you know
- - **Illusion of Transparency**: Believing your intent is obvious
- - **Spotlight Effect**: Overestimating how much others notice your mistakes
- ### Biases Affecting Message Recipients
- - **Fundamental Attribution Error**: Attributing behavior to character rather than circumstance
- - **Negativity Bias**: Weighing negative information more heavily
- - **Confirmation Bias**: Interpreting messages to confirm existing beliefs
- ## Emotional Intelligence Framework
- ### Signs of Dysregulation (reduce complexity, increase safety)
- - ALL CAPS, excessive punctuation
- - Unusually short/curt responses
- - Dramatic language ("always," "never," "everyone")
- ### Signs of Engagement (match energy, build momentum)
- - Questions and curiosity
- - Building on ideas
- - Appropriate response times
- ## Relationship Dynamics
- ### Power Awareness
- - Who has positional/relational/informational power?
- - How does power affect what can be said directly?
- ### Trust Level Assessment
- - **New relationship**: More explicit, more formal
- - **Established trust**: Can be more direct
- - **Damaged trust**: Over-communicate, follow through meticulously
- ## Difficult Conversation Archetypes
- | Type | Pattern | Approach |
- |------|---------|----------|
- | Avoided | Something needs to be said but hasn't | Name the avoidance gently |
- | Repeating | Same conflict keeps arising | Address the pattern itself |
- | Competing Needs | Both parties have legitimate but conflicting needs | Make both needs explicit |
- | Misunderstanding Spiral | Each response makes it worse | Pause, reset, clarify intent |
```
### references/response-crafting.md
```markdown
# Response Crafting Guide
## Pre-Draft Checklist
Before drafting, answer:
1. What must this message accomplish?
2. 2. What tone fits this person and situation?
3. 3. What obstacles might prevent this landing well?
4. 4. What structure serves the objective?
5. ## Structure Patterns
6. ### Acknowledge-Bridge-Guide (difficult conversations)
7. 1. Acknowledge their perspective genuinely
2. 2. Bridge to shared understanding
3. 3. Guide toward path forward
4. ### Context-Content-Call (requests)
5. 1. Brief relevant context
2. 2. The actual content/request
3. 3. Clear next step
4. ### Observation-Impact-Request (feedback)
5. 1. Specific, non-judgmental observation
2. 2. How it affected outcomes
3. 3. What you'd like instead
4. ## Tone Calibration
5. | Situation | Tone | Avoid |
6. |-----------|------|-------|
7. | Difficult news | Warm + Direct | Euphemisms, excessive softening |
8. | Conflict | Curious + Neutral | Blame, defensiveness |
9. | Request | Clear + Respectful | Demanding, passive-aggressive |
10. | Support | Empathetic + Present | Problem-solving too fast |
11. | Feedback | Specific + Constructive | Vagueness, personal attacks |
12. ## Common Pitfalls
13. - **Over-explaining**: More words ≠ more clarity
- - **Defensiveness masking as explanation**: "Well, the reason I..."
- - **Premature problem-solving**: Sometimes people need to be heard first
- - **Emotional matching**: Don't escalate when they're escalated
```
---
## Skill Companion Files
> Additional files collected from the skill directory layout.
### _meta.json
```json
{
"owner": "aatmaan1",
"slug": "communication-skill",
"displayName": "Communication Skill",
"latest": {
"version": "0.1.0",
"publishedAt": 1769872622737,
"commit": "https://github.com/clawdbot/skills/commit/76c0013dba43bfc202e1034b9dad7e05893c7e95"
},
"history": []
}
```