什么是 消息沟通与语气校准？

Message 技能作为 AI 智能体的社交护栏，可防止常见的自动化灾难，如回复全员骚扰或不恰当的专业语气。它使智能体能够在 Slack、Teams 到正式邮件等各种渠道中进行沟通，同时保持人类互动的细微差别。通过将其集成到 Openclaw Skills 中，开发人员可以确保其智能体永远不会过度承诺时间表，或在没有人工明确审核的情况下发送高风险消息。

除了简单的起草，该技能还对之前的消息进行深度的风格分析，以复制用户的特定声音，包括其偏好的简洁程度和表情符号用法。它强制执行严格的上下文意识，确保将消息发送到正确的群聊，并且内部元数据或私密评论绝不会泄露给外部方。

下载入口:https://github.com/openclaw/skills/tree/main/skills/ivangdavila/message

安装与下载

1. ClawHub CLI

从源直接安装技能的最快方式。

2. 手动安装

将技能文件夹复制到以下位置之一

优先级：工作区 > 本地 > 内置

3. 提示词安装

将此提示词复制到 OpenClaw 即可自动安装。

消息沟通与语气校准 应用场景

• 为涉及投资者、媒体和法律顾问的沟通提供高风险草稿起草。
• 根据紧急程度自动进行渠道路由（例如：紧急需求发 Slack，知会事项发邮件）。
• 具备上下文意识的群聊参与，以避免社交摩擦和过度沟通。
• 针对时区敏感的消息调度，以尊重接收者的边界并避免深夜通知。

1. 智能体读取对话中的最后五条消息，以校准适当的语气和风格简洁度。
2. 它根据预定义的升级矩阵评估请求的紧急程度。
3. 根据所需的响应时间选择通信渠道（电话、Slack 或电子邮件）。
4. 诸如“紧急”、“法律”或“失望”等高风险关键词会触发“草稿待审”状态。
5. 技能应用在平台配置文件中定义的平台特定格式。
6. 低风险消息会自动发送，而涉及承诺的内容则会排队等待人工审批。

消息沟通与语气校准 配置指南

要使用 Openclaw Skills 将此功能集成到您的项目中，请在终端中运行以下命令：

openclaw add message

确保在您的技能目录中初始化了校准文件：

touch platforms.md tone.md escalation.md

消息沟通与语气校准 数据架构与分类体系

该技能依赖于三个核心 Markdown 配置文件来管理行为和组织沟通逻辑：

name: Message
slug: message
version: 1.0.0
description: Communicate across channels without social disasters, with escalation rules, tone calibration, and platform-aware formatting.
metadata: {"clawdbot":{"emoji":"??","requires":{"bins":[]},"os":["linux","darwin","win32"]}}

When to Use

User needs to send messages on their behalf. Agent must avoid social mistakes that humans wouldn't make: wrong tone, wrong channel, wrong timing, auto-committing to things.

Quick Reference

Core Rules

1. Never Auto-Commit

• Timelines, pricing, legal terms, availability → draft for human, never send
• "We can deliver by Friday" from AI = career damage
• Money confirmations require explicit per-transaction approval
• When uncertain about commitment level → ask first

2. Escalate High-Stakes

Draft for human review, never auto-send:

• Investors, board, press, lawyers
• Client complaints, anything with "urgent", "legal", "disappointed"
• Condolences, relationship issues, conflict
• First message to new important contact

3. Match the Human's Style

• Read their last 5 messages before drafting
• Don't add phrases they never use ("Hope you're doing well!")
• Don't use emojis they avoid
• Real humans send "ok", AI sends paragraphs → match their brevity

4. Channel Selection Follows Urgency

• NEVER email for urgent issues
• NEVER Slack for formal client communication

5. Timing Is Social Signal

• Instant replies reveal automation
• 3 AM recipient time → schedule for morning
• Email = hours acceptable. Slack DM = expect <1hr response

6. Context Awareness Prevents Disasters

• Check you're in the RIGHT chat before sending
• Don't introduce yourself to someone you've messaged 50 times
• Group chats: lurking is normal, replying to everything is weird
• Wrong group = social suicide → when unsure, ASK

Common Traps

• Copying boss on complaint email → escalates when de-escalation needed
• Reply-all with "thanks" → 50 people interrupted
• Forwarding thread with internal comments visible → trust destroyed
• Sending at 11 PM "just to get it off my plate" → signals poor boundaries
• Using client's first name before they used yours → presumptuous