Token导航 LogoToken导航

Agent Skill · 开发

communication-skill(沟通技巧)

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

communication-skill 是开发类 Agent Skill,可用宿主为 OpenClaw,通过ClawHub获取,权限为只读;许可证为 MIT-0,第三方扫描已通过,按安装量在开发类的 21,746 个 Skill 里排第 313。

总安装 132,203周安装 5,348GitHub Stars 3下载 41,652核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
MIT-0
版本
0.1.0

安装方式

通过对话安装

复制提示词发给支持本地命令或 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

这个 Skill 是做什么的

开发类 Skill 面向写代码、改代码和排查问题,一般会读写仓库文件,部分还会执行构建或测试命令。

辅助生成上下文感知且富有同理心的沟通内容。适合客服、协作工具或人际互动类应用中的消息生成。综合情感线索与历史对话优化表达方式。安装命令:openclaw skills install communication-skill。输出建议需人工复核,避免误解风险。

communication-skill 属于开发类 Skill,可作为该场景下的辅助能力补充。

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 OpenClaw;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 openclaw skills install communication-skill;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它标注为只读,先用只读任务试一次,确认行为符合预期再扩大使用范围。

常见问题

6 条

communication-skill 怎么安装?

在终端执行 openclaw skills install communication-skill。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

communication-skill 支持哪些 AI 工具?

公开资料标注支持 OpenClaw。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

communication-skill 需要什么权限?

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

communication-skill 是免费的吗?

来源标注的许可证是 MIT-0。本站不代收任何费用,也不托管安装包;能否商用、要不要署名,以许可证原文为准。

communication-skill 用的人多吗?

公开数据是累计安装 132,203 次,近一周安装 5,348 次,下载 41,652 次,GitHub 3 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

communication-skill 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 专注 OpenClaw 一种宿主,触发方式和使用习惯不用来回切换。
  • 许可证明确为 MIT-0,商用和分发边界好判断。
  • 第三方扫描已通过,常见的高风险行为没有命中。
  • 标注为只读权限,试用阶段不容易误改本地文件。

先想清楚的地方

  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 OpenClaw,想直接扩展它能力的人。
  • 需要处理开发类任务、又不想每次都手写提示词的人。
  • 需要许可证清楚、并且有第三方扫描结果的团队项目。

不太适合

  • 需要厂商级技术支持和 SLA 的生产系统。

开发类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
skill-vetter

技能审查员 · OpenClaw

8,779,018986操作浏览器MIT-0通过
ontology

本体论 · OpenClaw

6,636,960576只读MIT-0通过
entra-app-registration

内部应用程序注册 · Codex、Claude

6,631,872764接触敏感数据未明确通过
entra-app-registration

内部应用程序注册 · Codex、Claude

3,757,680201接触敏感数据未明确通过
nano-banana-pro

纳米香蕉专业版 · OpenClaw

3,526,898364接触敏感数据MIT-0有提醒
communication-skill

沟通技巧 · 本页

132,2033只读MIT-0通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

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.

平台分布

OpenClaw

89.53%
按下载量换算37,291

安全审计

VirusTotal

通过

ClawScan

通过

Static analysis

未展示

权限和风险

只读

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

安装前确认

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

继续浏览同类 Skills