Token导航 LogoToken导航TokenDH.com
开发只读clawhub未标认证来源可访问clear审计通过

communication-skill沟通技巧

Agent Skill

communication-skill 用于补充开发相关能力,适合在 OpenClaw 中需要让 Agent 承接开发相关任务时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

132,203

周安装

5,348

GitHub Stars

3

下载量

41,652
OpenClaw

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

MIT-0

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:communication-skill(沟通技巧)
来源仓库:https://github.com/aatmaan1/communication-skill
安装命令:
openclaw skills install communication-skill
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 OpenClaw 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

ClawHubOpenClaw
openclaw skills install communication-skill

简介

辅助生成上下文感知且富有同理心的沟通内容。

  • 适合客服、协作工具或人际互动类应用中的消息生成。
  • 综合情感线索与历史对话优化表达方式。
  • 安装命令:openclaw skills install communication-skill。
  • 输出建议需人工复核,避免误解风险。communication-skill 属于开发类 Skill,可作为该场景下的辅助能力补充。

SKILL.md

name
communication
description
|
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.

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.

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.

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.

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:

SituationTone Approach
Difficult newsWarm + Direct
ConflictCurious + Neutral
RequestClear + Respectful
SupportEmpathetic + Present
FeedbackSpecific + 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.

适合场景

01

OpenClaw 用户查找和安装 Skill 时

02

用户想查找某类 Agent Skill 时

03

需要根据任务场景推荐可安装能力包时

04

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

补充不同宿主或平台的使用分布数据

能力 5

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

OpenClaw

89.53%
按下载量换算37,291

安全审计

VirusTotal

通过

ClawScan

通过

Static analysis

未展示

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills