Draft clear Slack messages using mrkdwn, Slack’s own text formatting syntax. Structure announcements and requests around the main point, format links and emphasis correctly, and choose between thread replies and channel posts based on the conversation.
Guidance for composing well-formatted, effective Slack messages using mrkdwn syntax
Review the instructions the agent will receive before you install.
This skill provides guidance for composing well-formatted, effective Slack messages.
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 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 |
**bold** (double asterisks) — Slack uses *bold* (single asterisks)## headers — Slack does not support Markdown headers. Use *bold text* on its own line instead.[text](url) for links — Slack uses <url|text> format--- for horizontal rules — Slack does not render these*bold* for names, dates, deadlines, and action items so they stand out when scanning.reply_broadcast (also post to channel) only when the reply contains information everyone needs to see.#general is usually more formal than #random.No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Review a design or web page against WCAG 2.1 AA, an accessibility standard. Organize findings on contrast, keyboard access, forms, and screen reader behavior, with severity levels and practical recommendations for fixes.
Build a single brief on an existing customer using available sales records, emails, documents, call notes, and internal chat. Understand the current situation, key contacts, recent discussions, and gaps that may need attention.
Build or refresh a strategic customer account plan from sales records, emails, and meeting transcripts. Organize goals, stakeholders, growth opportunities, risks, and dated actions into a document, then sync approved highlights to the customer relationship management system.
Research prospective companies and contacts, check existing customer records, and assess fit against your ideal customer profile. Receive a sourced brief covering recent developments, likely priorities, outreach talking points, and a suggested next step.
Research sales accounts using Common Room data to summarize company details, buying signals, ownership, and key contacts. Answer specific questions directly or prepare a broader briefing with evidence-based next steps, clearly identifying missing information.
Score and group accounts by customer fit and engagement, such as recent contact and open sales opportunities. Identify where to focus sales effort, choose next actions, and spot promising accounts with neglected outreach or missing information.