communication

TotalClaw 作者 totalclaw

深度倾听与回应撰写 - 将 Claude 转变为一位深思熟虑的沟通者,跨对话、已连接的应用和用户笔记综合上下文,撰写具备情境智能的回应。 TRIGGERS: 当用户请求 Claude 协助任何沟通任务时,包括起草消息、电子邮件、回复、回应,或应对困难对话。当用户希望理解沟通动态、分析语气,或就在特定情境中如何沟通获取策略建议时也会触发。 CAPABILITIES: 综合并行的对话线程,检测情绪潜台词,应用沟通原则,考虑关系历史,并针对具体的人与情境生成可直接发送的消息草稿。 --- # 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.

安装 / 下载方式

TotalClaw CLI推荐
totalclaw install totalclaw:totalclaw~aatmaan1-communication-skill
cURL直接下载,无需登录
curl -fsSL https://skills.taituai.com/api/skills/totalclaw%3Atotalclaw~aatmaan1-communication-skill/file -o aatmaan1-communication-skill.md
## 中文说明

# 沟通技能(Communication Skill)

通过在开口之前深度倾听,将沟通从被动应对转变为有意而为。

## 核心工作流

每项沟通任务都遵循此流程:

```
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
```

## 第 1 步:收集上下文

在撰写任何回应之前,主动收集信息:

**来自对话:**
- 用户就此情况分享了什么?
- 涉及哪些人,他们与用户是什么关系?
- 沟通渠道是什么(电子邮件、Slack、短信、面对面)?

**来自已连接的来源**(如果可用):
- 与此人/群组的近期消息
- 关于同一主题的并行对话
- 与此人之间的历史模式

**来自用户笔记**(如果提供):
- 适用的个人原则或价值观
- 关系背景或历史
- 关于此人/此情况的既往经验

**在以下情况提出澄清问题:**
- 目标不明确
- 关键上下文似乎缺失
- 多种方法看起来同样有效

## 第 2 步:深度倾听

应用深度倾听框架。参见 [listening-framework.md](references/listening-framework.md)。

分层处理:
1. **表层**:明确说出来的是什么?
2. **上下文**:周边的故事是什么?
3. **潜台词**:言语背后是什么情绪与需求?
4. **模式**:哪些历史影响着此刻?

关键问题:
- 此人实际需要什么(相对于他们所请求的)?
- 情绪温度如何?
- 有什么重要但未说出口的内容?
- 哪些并行线程与此相关?

## 第 3 步:考虑原则与心理

应用沟通原则。参见 [principles.md](references/principles.md)。

需要权衡的核心原则:
- **临在胜于表演** - 去理解,而非去表演
- **好奇先于评判** - 对驱动行为的因素保持好奇
- **清晰即善意** - 即便不舒服也要清晰
- **修复胜于完美** - 关系比"正确"更重要
- **时机很重要** - 正确的消息、错误的时机 = 错误的消息

考虑心理动态。参见 [psychology-patterns.md](references/psychology-patterns.md)。

检查以下方面:
- 影响解读的认知偏差
- 情绪状态信号
- 在起作用的权力动态
- 关系中的信任程度

## 第 4 步:撰写回应

应用回应撰写原则。参见 [response-crafting.md](references/response-crafting.md)。

**起草前检查清单:**
- [ ] 这条消息必须达成什么?
- [ ] 什么语气契合此人与此情境?
- [ ] 哪些障碍可能妨碍它良好地被接收?
- [ ] 什么结构服务于该目标?

**选择一种结构模式:**

*承认-桥接-引导*(困难对话):
1. 真诚地承认对方的视角
2. 桥接至共同理解
3. 引导向前进的路径

*背景-内容-呼吁*(请求):
1. 简要的相关背景
2. 实际的内容/请求
3. 清晰的下一步

*观察-影响-请求*(反馈):
1. 具体的、非评判性的观察
2. 它如何影响了结果
3. 你希望改为怎样

**根据情境校准语气:**
| 情境 | 语气方法 |
|-----------|---------------|
| 困难消息 | 温暖 + 直接 |
| 冲突 | 好奇 + 中立 |
| 请求 | 清晰 + 尊重 |
| 支持 | 共情 + 临在 |
| 反馈 | 具体 + 建设性 |

## 第 5 步:精炼与校验

在呈现草稿之前,校验:

- [ ] 这是否达成了既定目标?
- [ ] 语气是否契合关系与情境?
- [ ] 收件人应做什么/理解什么是否清晰?
- [ ] 它是否尊重用户的原则与价值观?
- [ ] 它是否足够简洁?
- [ ] 我自己愿意收到这条消息吗?

## 输出格式

呈现回应草稿时:

```
**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]
```

## 处理复杂情境

**当存在并行线程时:**
综合它们。指出各方视角一致/分歧之处。考虑各方分别知道什么。

**当情绪高涨时:**
以承认开场。不要立即去解决问题。先建立安全感,再谈实质内容。

**当关系紧张时:**
过度沟通你的意图。避免假设。聚焦于修复,而非"正确"。

**当事关重大时:**
多花些时间。考虑意料之外的解读。拿不准时,向用户征求意见。

## 此技能不做的事

- 替用户决定要沟通什么
- 假设未曾提供的上下文
- 未经明确确认就代表用户发送消息
- 保证结果——沟通是共同创造的

目标是帮助用户以更高的清晰度、意图性和连接感进行沟通。