# 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.
沟通技巧
SKILL开发原名 communication-skill
communication-skill 用于补充开发相关能力,适合在 OpenClaw 中需要让 Agent 承接开发相关任务时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。
累计安装
132,203
本周 5,348
GitHub 星标
3
仓库 communication-skill
下载量
41,652
技能市场下载数
权限级别
只读
安装前请确认风险范围
许可证
许可证明确
MIT-0
安装
ClawHub 市场openclaw skills install communication-skill
技能档案
开发作者 / 维护方aatmaan1仓库 communication-skill · 版本 0.1.0
宿主客户端OpenClaw技能可被这些客户端加载
安装方式ClawHub 市场安装包 aatmaan1/communication-skill
权限级别只读安装前请确认风险范围
许可证MIT-0许可证明确,商用前请自行确认条款
仓库可用性available技能仓库当前是否可访问
最近核验2026-05-01上游最后核验时间 · 数据更新 未标注
正文体量6.4 KBSKILL.md 原文大小,越大说明说明书写得越细
能做什么
5 项能力- 按任务关键词查找相关 Skills
- 展示可复制的安装命令
- 保留来源站点、仓库和原始说明,方便继续核验
- 补充不同宿主或平台的使用分布数据
- 展示第三方安全扫描或审计结果
OpenClaw 用户查找和安装 Skill 时用户想查找某类 Agent Skill 时需要根据任务场景推荐可安装能力包时需要对比不同来源的安装命令和来源信息时
权限与风险
只读安装与使用指南
安装步骤
本站只展示命令,不托管安装包,也不自动执行。
怎么用
安装后应在对应宿主中按原始 README 的触发条件使用;当前草稿只做目录说明,具体调用方式由规则抽取,异常条目再复核。
SKILL.md 全文
6.4 KB安全信息
审计结论安全审计VirusTotal、ClawScan、Static analysis第三方安全审计平台给出的结论
热门专题
按场景挑技能
合规与风控
8,993 个技能
行业合规准入、制度比对与风险清单,金融、医疗、制造等行业各有成套技能。
HR 8,966 个技能HR日常会用到的一组技能:把重复的判断和写作交给模型,自己只做决定。
部署运维 8,240 个技能容器化、发布流程、日志与告警处理,偏可重复的运维手册。
电商运营 7,727 个技能开店和做增长的一整套:找货、写卖点、做图、投流、处理售后,能串成闭环。
增长分析 6,089 个技能看数据找增长点:漏斗、留存、渠道归因,最后给到可执行的实验建议。
数据库与 SQL 5,902 个技能建表与迁移、慢查询分析、索引建议与数据核对。
脚本工具 5,882 个技能写一次就能反复用的小工具:命令行脚本、批处理与自动化任务。
营销文案 5,593 个技能广告与推广文案:卖点提炼、活动话术、投放素材与短文案。
技能内容以作者仓库为准;分类、权限级别与许可证状态的中文说明为中文整理,最近核验 2026-05-01。