slack-messaging

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Slack Messaging Best Practices

Slack消息撰写最佳实践

This skill provides guidance for composing well-formatted, effective Slack messages.

本技能提供关于撰写格式规范、高效Slack消息的指导。

When to Use

适用场景

Apply this skill whenever composing, drafting, or helping the user write a Slack message, including when using

slack_send_message

slack_send_message_draft

, or

slack_schedule_message

. The formatting rules below cover these message tools.

slack_create_canvas

uses a different, richer markdown dialect — see the Canvas note below.

当撰写、草拟或协助用户编写Slack消息时均可应用本技能，包括使用

slack_send_message

、

slack_send_message_draft

或

slack_schedule_message

工具的场景。以下格式规则适用于这些消息工具。

slack_create_canvas

使用另一种更丰富的Markdown语法变体——请查看下方的Canvas说明。

Formatting

格式规范

The message tools (

slack_send_message

slack_send_message_draft

slack_schedule_message

) accept standard markdown and convert it to Slack formatting on send. Write normal markdown. Do not use Slack's legacy

mrkdwn

syntax (

*bold*

~strike~

); those single-character forms mean something different in standard markdown. Each text element is limited to ~5000 characters.

Format	Syntax
Bold	`text`
Italic	`_text_` (or `text` )
Strikethrough	`~~text~~`
Code (inline)	`code`
Quote	`> text`
Link	`[display text](url)`
Bulleted list	`- item`
Numbered list	`1. item`

Block elements also work. Write them as literal markdown:

Code block with an optional language for syntax highlighting:
text
```
```python
print("hello")
```
```

Table with

delimiters (escape a literal pipe inside a cell as

\|

text

| Feature | Status |
|---------|--------|
| Tables  | works  |

Headers with
```
#
```
/
```
##
```
/
```
###
```
:
text
```
## Section title
```

The one thing that does not embed in a message: inline images (

![alt](url)

) typically render as a plain link rather than an inline image. For rich embedded layouts (buttons, images, structured cards) you need Block Kit; for a document-style surface where images do embed, use a canvas. See the Notes below.

消息工具（

slack_send_message

、

slack_send_message_draft

、

slack_schedule_message

）支持标准Markdown，发送时会自动转换为Slack格式。请使用常规Markdown语法，不要使用Slack的旧版

mrkdwn

语法（如

*bold*

、

~strike~

）；这些单字符格式在标准Markdown中含义不同。每个文本元素的字符限制约为5000个。

格式类型	语法
加粗	`text`
斜体	`_text_` （或 `text` ）
删除线	`~~text~~`
行内代码	`code`
引用	`> text`
链接	`[display text](url)`
无序列表	`- item`
有序列表	`1. item`

块级元素同样适用，请直接使用字面Markdown语法编写：

代码块（可指定语言以实现语法高亮）：
text
```
```python
print("hello")
```
```
表格（使用
```
|
```
分隔符，单元格内的竖线需转义为
```
\|
```
）：
text
```
| Feature | Status |
|---------|--------|
| Tables  | works  |
```
标题（使用
```
#
```
/
```
##
```
/
```
###
```
）：
text
```
## Section title
```

消息中无法嵌入的内容：行内图片（

![alt](url)

）通常会显示为普通链接而非内嵌图片。如需实现包含按钮、图片、结构化卡片的富嵌入布局，需使用Block Kit；如需支持图片嵌入的文档式界面，请使用Canvas。请查看下方的说明部分。

Message Structure Guidelines

消息结构指南

Lead with the point. Put the most important information in the first line. Many people read Slack on mobile or in notifications where only the first line shows.
Keep it short. Aim for 1-3 short paragraphs (the ~5000-character limit is a ceiling, not a target). If the message is long or structured, consider a Canvas instead.
Use line breaks generously. Walls of text are hard to read. Separate distinct thoughts with blank lines.
Use bullet points for lists. Anything with 3+ items should be a list, not a run-on sentence.
Bold key information. Use
```
**bold**
```
for names, dates, deadlines, and action items so they stand out when scanning.

开门见山：将最重要的信息放在第一行。许多用户通过移动端或通知查看Slack，通常只能看到第一行内容。
简洁明了：目标为1-3个短段落（约5000字符的限制是上限而非目标）。如果消息较长或结构复杂，建议使用Canvas。
合理换行：大段文字难以阅读，不同的想法之间请用空行分隔。
列表用项目符号：任何包含3个及以上条目的内容都应使用列表，而非冗长的句子。
关键信息加粗：对名称、日期、截止日期和行动项使用
```
**bold**
```
加粗，方便用户快速扫描时注意到。

Thread vs. Channel Etiquette

线程与频道礼仪

Reply in threads when responding to a specific message to keep the main channel clean.
Use
reply_broadcast
(also post to channel) only when the reply contains information everyone needs to see.
Post in the channel (not a thread) when starting a new topic, making an announcement, or asking a question to the whole group.
Don't start a new thread to continue an existing conversation; find and reply to the original message.

回复线程：回复特定消息时请使用线程，保持主频道整洁。
使用
reply_broadcast
（同时发布到频道）：仅当回复内容是所有人都需要查看的信息时使用。
发布到频道（而非线程）：开启新话题、发布公告或向全体成员提问时，请直接发布到频道。
不要开启新线程：如需继续现有对话，请找到原始消息并回复，不要开启新线程。

Tone and Audience

语气与受众

Match the tone to the channel:
```
#general
```
is usually more formal than
```
#random
```
.
For simple acknowledgments, add an emoji reaction with
```
slack_add_reaction
```
instead of a reply message (use
```
slack_get_reactions
```
to read existing reactions).
When writing announcements, use a clear structure: context, key info, call to action.

匹配频道语气：
```
#general
```
频道通常比
```
#random
```
更正式。
简单确认时，使用
```
slack_add_reaction
```
添加表情反应即可，无需回复消息（可使用
```
slack_get_reactions
```
查看已有的反应）。
撰写公告时，使用清晰的结构：背景信息、关键内容、行动号召。

Scheduling

排程操作

Use
```
slack_schedule_message
```
to post later.
```
post_at
```
is a Unix timestamp that must be at least 2 minutes in the future and at most 120 days out; the message body uses the same standard markdown as above.
Scheduled messages can't be edited via the API once set — the user manages them from Drafts & sent in Slack.

使用
```
slack_schedule_message
```
延迟发送消息。
```
post_at
```
是Unix时间戳，必须至少设置为未来2分钟，最多不超过120天；消息正文使用与上述相同的标准Markdown语法。
排程消息设置后无法通过API编辑——用户需在Slack的草稿与已发送消息中管理。

Notes

说明

Canvas formatting is different.
```
slack_create_canvas
```
uses Canvas-flavored Markdown, a richer dialect than the message tools: headers, tables, checklists, and inline images (
```
![alt](url)
```
) all embed, and it also supports user/channel reference cards, callouts, and columns. Do not assume the message rules above apply — follow the
```
slack_create_canvas
```
tool's own formatting guidance when composing a canvas.
Scope: this skill owns composing and formatting the text of messages sent through the Slack MCP message tools. For interactive layouts (buttons, menus, modals, Home tabs, or any Block Kit JSON), use the
```
slack:block-kit
```
skill, which composes and validates the block payload. For calling the Slack Web API directly (
```
chat.postMessage
```
and friends) rather than the MCP tools, use the
```
slack:slack-api
```
skill.

Canvas格式不同：
```
slack_create_canvas
```
使用Canvas风格的Markdown，这是一种比消息工具更丰富的语法变体：标题、表格、复选列表和行内图片（
```
![alt](url)
```
）均可嵌入，还支持用户/频道引用卡片、提示框和列布局。请勿假设上述消息规则适用于Canvas——撰写Canvas时请遵循
```
slack_create_canvas
```
工具自身的格式指南。
适用范围：本技能负责处理通过Slack MCP消息工具发送的消息文本的撰写与格式化。如需交互式布局（按钮、菜单、模态框、主页标签或任何Block Kit JSON），请使用
```
slack:block-kit
```
技能，该技能负责撰写和验证块负载。如需直接调用Slack Web API（如
```
chat.postMessage
```
等）而非MCP工具，请使用
```
slack:slack-api
```
技能。