anthropics/knowledge-work-plugins

slack-messaging

Guidance for composing well-formatted, effective Slack messages using mrkdwn syntax

View source

How to use

  1. Copy the installation command and review the source package before installing it in your own agent environment.
  2. Check the source document for required tools, credentials and supported hosts.
  3. Describe your input and desired deliverable; review the output against the source material.
npx skills add https://github.com/anthropics/knowledge-work-plugins --skill slack-messaging

Before you start

  • Installation does not include a model subscription, API allowance or permission to access your files.
  • Repository stars and installation counts describe activity, not an independent quality or security test.
Original skill document

Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.

Slack Messaging Best Practices

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

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_create_canvas.

Slack Formatting (mrkdwn)

Slack uses its own markup syntax called mrkdwn, which differs from standard Markdown. Always use mrkdwn when composing Slack messages:

FormatSyntaxNotes
Bold*text*Single asterisks, NOT double
Italic_text_Underscores
Strikethrough~text~Tildes
Code (inline) code Backticks
Code block code Triple backticks
Quote> textAngle bracket
Link`<url\display text>`Pipe-separated in angle brackets
User mention<@U123456>User ID in angle brackets
Channel mention<#C123456>Channel ID in angle brackets
Bulleted list- item or • itemDash or bullet character
Numbered list1. itemNumber followed by period

Common Mistakes to Avoid

  • Do NOT use **bold** (double asterisks) — Slack uses *bold* (single asterisks)
  • Do NOT use ## headers — Slack does not support Markdown headers. Use *bold text* on its own line instead.
  • Do NOT use [text](url) for links — Slack uses <url|text> format
  • Do NOT use --- for horizontal rules — Slack does not render these

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. If the message is long, consider using 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.

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.

Tone and Audience

  • Match the tone to the channel — #general is usually more formal than #random.
  • Use emoji reactions instead of reply messages for simple acknowledgments (though note: the MCP tools can't add reactions, so suggest the user do this manually if appropriate).
  • When writing announcements, use a clear structure: context, key info, call to action.

Related by task

from this repository

More skills

All skills
anthropics
Official

process-doc

Document a business process — flowcharts, RACI, and SOPs. Use when formalizing a process that lives in someone's head, building a RACI to clarify who owns what, writing an SOP for a handoff or audit, or capturing the exceptions and edge cases of how work actually gets done.

1h installs
1
GitHub stars
36.6K
Updated
Nov 20
anthropics
Official

data-visualization

Create effective data visualizations with Python (matplotlib, seaborn, plotly). Use when building charts, choosing the right chart type for a dataset, creating publication-quality figures, or applying design principles like accessibility and color theory.

1h installs
5
GitHub stars
36.6K
Updated
Nov 20
anthropics
Official

accessibility-review

Run a WCAG 2.1 AA accessibility audit on a design or page. Trigger with "audit accessibility", "check a11y", "is this accessible?", or when reviewing a design for color contrast, keyboard navigation, touch target size, or screen reader behavior before handoff.

1h installs
4
GitHub stars
36.6K
Updated
Nov 20
anthropics
Official

sql-queries

Write correct, performant SQL across all major data warehouse dialects (Snowflake, BigQuery, Databricks, PostgreSQL, etc.). Use when writing queries, optimizing slow SQL, translating between dialects, or building complex analytical queries with CTEs, window functions, or aggregations.

1h installs
4
GitHub stars
36.6K
Updated
Nov 20