Format messages for Slack using mrkdwn syntax. Use when responding to Slack channels (folder starts with "slack_" or JID contains slack identifiers).
When responding to Slack channels, use Slack's mrkdwn syntax instead of standard Markdown.
Check your group folder name or workspace path:
slack_ (e.g., slack_engineering, slack_general)/workspace/group/ path for slack_ prefix| Style | Syntax | Example |
|---|---|---|
| Bold | *text* | bold text |
| Italic | _text_ | italic text |
| Strikethrough |
~text~ |
| Code (inline) | `code` | inline code |
| Code block | ```code``` | Multi-line code |
<https://example.com|Link text> # Named link
<https://example.com> # Auto-linked URL
<@U1234567890> # Mention user by ID
<#C1234567890> # Mention channel by ID
<!here> # @here
<!channel> # @channel
Slack supports simple bullet lists but NOT numbered lists:
• First item
• Second item
• Third item
Use • (bullet character) or - or * for bullets.
> This is a block quote
> It can span multiple lines
Use standard emoji shortcodes: :white_check_mark:, :x:, :rocket:, :tada:
## headings (use *Bold text* for headers instead)**double asterisks** for bold (use *single asterisks*)[text](url) links (use <url|text> instead)1. numbered lists (use bullets with numbers: • 1. First)--- horizontal rules*Daily Standup Summary*
_March 21, 2026_
• *Completed:* Fixed authentication bug in login flow
• *In Progress:* Building new dashboard widgets
• *Blocked:* Waiting on API access from DevOps
> Next sync: Monday 10am
:white_check_mark: All tests passing | <https://ci.example.com/builds/123|View Build>
*bold* not **bold**<url|text> not [text](url)• bullets, avoid numbered lists:emoji: shortcodes>