SkillAgentSearch skills...

slack-messaging

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

Install / Use

npx skills add anthropics/knowledge-work-plugins --skill slack-messaging

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

82/100

Supported Platforms

Universal

Our assessment of slack-messaging

slack-messaging scores 82/100 on our quality scale, 345th of 395 Communication skills we index.

Its SKILL.md is 3.0 KB long, split into 7 sections and no code examples: a solid amount of guidance for an agent.

With 25,526 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
26/30
Structure
11/20
Description
12/15
Adoption
19/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so slack-messaging is actively maintained.
  • Our last check on 2026-10-16 found the source still online.
  • It is released under the Apache-2.0 license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-09-27. Automated pattern scan on 2026-09-26. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

slack-messaging compared with similar skills

All 4 of these similar skills score higher than slack-messaging; compare them before choosing.

SkillScoreStarsUpdatedFormat
slack-messaging (this skill)by anthropics8225.5k53d agoSKILL.md
x402by browser-use100121.0k3d agoSKILL.md
algorithmic-artby anthropics100177.9k55d agoSKILL.md
pptxby anthropics100177.9k55d agoSKILL.md
designby nextlevelbuilder100149.0k6d agoSKILL.md

Frequently asked questions

How do I install slack-messaging?
Run npx skills add anthropics/knowledge-work-plugins --skill slack-messaging. The install tabs above show the steps for each supported agent.
Which AI agents does slack-messaging work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is slack-messaging safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is Apache-2.0-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is slack-messaging still maintained?
The repository was last updated about 2 months ago, so slack-messaging is actively maintained.

name: slack-messaging description: Guidance for composing well-formatted, effective Slack messages using mrkdwn syntax

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:

| Format | Syntax | Notes | |--------|--------|-------| | Bold | *text* | Single asterisks, NOT double | | Italic | _text_ | Underscores | | Strikethrough | ~text~ | Tildes | | Code (inline) | `code` | Backticks | | Code block | ```code``` | Triple backticks | | Quote | > text | Angle 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 • item | Dash or bullet character | | Numbered list | 1. item | Number 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 Skills

View on GitHub
GitHub Stars25.5k
CategoryCommunication
Updated1mo ago
Forks3.0k

Languages

Python

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions