slack-messaging
Guidance for composing well-formatted, effective Slack messages using standard markdown
What this skill does
# 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`. ## Formatting Slack MCP accepts standard markdown. Use familiar markdown syntax when composing messages: | Format | Syntax | |--------|--------| | Bold | `**text**` | | Italic | `_text_` or `*text*` | | Strikethrough | `~text~` | | Code (inline) | `` `code` `` | | Code block | `` ```code``` `` | | Quote | `> text` | | Link | `[display text](url)` | | Bulleted list | `- item` | | Numbered list | `1. item` | Not supported: - Tables - Headers `(#, ##, etc.)` - Images via markdown `()` ## 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 in Productivity
gitea-workflow
IncludedOrchestrate agile development workflows for Gitea repositories using the tea CLI. Use when working with Gitea-hosted repos and asking to 'run the workflow', 'continue working', 'what's next', 'complete the task cycle', 'start my day', 'end the sprint', 'implement the next task', or wanting guided step-by-step development assistance. Keywords: workflow, orchestrate, agile, task cycle, sprint, daily, implement, review, PR, standup, retrospective, gitea, tea.
microsoft-graph-gateway
IncludedRoute Microsoft Graph work in this workspace. Use when users want to read or write Outlook mail, calendar events, contacts, OneDrive or SharePoint files, Teams, Planner, To Do, users, groups, directory data, or arbitrary Microsoft Graph endpoints from VS Code. Prefer WorkIQ for common read scenarios. Use Microsoft Graph for write actions and gap-read scenarios that need exact Graph properties, filters, permissions, or endpoints.
copilotkit
IncludedUse when building with CopilotKit — setup, development, integrations, debugging, upgrading, or contributing. Routes to the appropriate specialized skill based on the task.
wordly-wisdom
IncludedProvides calibrated decision analysis using Charlie Munger-style multiple mental models, inversion, incentive mapping, circle-of-competence checks, misjudgment audits, second-order effects, and forecast updates. Use when the user asks for an oracle take, a hard call, a decision memo, a premortem, an outside view, a red-team, a sanity-check, what am I missing, think this through, or wants a strategy, hire, investment, plan, product, partnership, or major life choice analysed. Avoid for simple factual lookups or time-sensitive legal, medical, or market questions without fresh evidence.
swain-session
IncludedSession management and project status dashboard. Owns the full session lifecycle (start/work/close/resume), focus lane, bookmarks, worktree detection, and tab naming. Also serves as the project status dashboard — shows active epics, progress, actionable next steps, blocked items, tasks, GitHub issues, and recommendations. Worktree creation is deferred to swain-do task dispatch (SPEC-195). Triggers on: 'session', 'status', 'what's next', 'dashboard', 'overview', 'where are we', 'what should I work on', 'show me priorities', 'bookmark', 'focus on', 'session info'.
gandi
IncludedComprehensive Gandi domain registrar integration for domain and DNS management. Register and manage domains, create/update/delete DNS records (A, AAAA, CNAME, MX, TXT, SRV, and more), configure email forwarding and aliases, check SSL certificate status, create DNS snapshots for safe rollback, bulk update zone files, and monitor domain expiration. Supports multi-domain management, zone file import/export, and automated DNS backups. Includes both read-only and destructive operations with safety controls.