slack-messaging
Guidance for composing well-formatted, effective Slack messages using mrkdwn syntax
Best use case
slack-messaging is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Guidance for composing well-formatted, effective Slack messages using mrkdwn syntax
Teams using slack-messaging should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/slack-messaging/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How slack-messaging Compares
| Feature / Agent | slack-messaging | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Guidance for composing well-formatted, effective Slack messages using mrkdwn syntax
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
AI Agents for Marketing
Discover AI agents for marketing workflows, from SEO and content production to campaign research, outreach, and analytics.
AI Agents for Startups
Explore AI agent skills for startup validation, product research, growth experiments, documentation, and fast execution with small teams.
AI Agents for Coding
Browse AI agent skills for coding, debugging, testing, refactoring, code review, and developer workflows across Claude, Cursor, and Codex.
SKILL.md Source
# 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
slack-search
Guidance for effectively searching Slack to find messages, files, channels, and people
pipeline-review
Analyze pipeline health — prioritize deals, flag risks, get a weekly action plan. Use when running a weekly pipeline review, deciding which deals to focus on this week, spotting stale or stuck opportunities, auditing for hygiene issues like bad close dates, or identifying single-threaded deals.
forecast
Generate a weighted sales forecast with best/likely/worst scenarios, commit vs. upside breakdown, and gap analysis. Use when preparing a quarterly forecast call, assessing gap-to-quota from a pipeline CSV, deciding which deals to commit vs. call upside, or checking pipeline coverage against your number.
draft-outreach
Research a prospect then draft personalized outreach. Uses web research by default, supercharged with enrichment and CRM. Trigger with "draft outreach to [person/company]", "write cold email to [prospect]", "reach out to [name]".
daily-briefing
Start your day with a prioritized sales briefing. Works standalone when you tell me your meetings and priorities, supercharged when you connect your calendar, CRM, and email. Trigger with "morning briefing", "daily brief", "what's on my plate today", "prep my day", or "start my day".
create-an-asset
Generate tailored sales assets (landing pages, decks, one-pagers, workflow demos) from your deal context. Describe your prospect, audience, and goal — get a polished, branded asset ready to share with customers.
competitive-intelligence
Research your competitors and build an interactive battlecard. Outputs an HTML artifact with clickable competitor cards and a comparison matrix. Trigger with "competitive intel", "research competitors", "how do we compare to [competitor]", "battlecard for [competitor]", or "what's new with [competitor]".
call-summary
Process call notes or a transcript — extract action items, draft follow-up email, generate internal summary. Use when pasting rough notes or a transcript after a discovery, demo, or negotiation call, drafting a customer follow-up, logging the activity for your CRM, or capturing objections and next steps for your team.
update
Sync tasks and refresh memory from your current activity. Use when pulling new assignments from your project tracker into TASKS.md, triaging stale or overdue tasks, filling memory gaps for unknown people or projects, or running a comprehensive scan to catch todos buried in chat and email.
task-management
Simple task management using a shared TASKS.md file. Reference this when the user asks about their tasks, wants to add/complete tasks, or needs help tracking commitments.
memory-management
Two-tier memory system that makes Claude a true workplace collaborator. Decodes shorthand, acronyms, nicknames, and internal language so Claude understands requests like a colleague would. CLAUDE.md for working memory, memory/ directory for the full knowledge base.
write-spec
Write a feature spec or PRD from a problem statement or feature idea. Use when turning a vague idea or user request into a structured document, scoping a feature with goals and non-goals, defining success metrics and acceptance criteria, or breaking a big ask into a phased spec.