MarketplaceSKILL.mdLeída en 8444efc
slack-messaging
Guidance for composing well-formatted, effective Slack messages using mrkdwn syntax
Resumen
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 —
#generalis 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.
Archivos 1 archivo
Instálala a mano
Deska ejecuta esto por ti, para cada agente que elijas. Para ejecutarlo tú en una terminal:
npx skills add anthropics/knowledge-work-plugins --skill slack-messagingMás de anthropics
- frontend-designanthropicsOficialGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.958 k instalaciones en skills.sh8
- skill-creatoranthropicsOficialCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.398.8 k instalaciones en skills.sh0
- pptxanthropicsOficialUse this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates (.potx), layouts, speaker notes, or comments. Trigger whenever the user mentions \"deck,\" \"slides,\" \"presentation,\" or references a .pptx or .potx filename, regardless of what they plan to do with the content afterward. If a .pptx or .potx file needs to be opened, created, or touched, use this skill.231.2 k instalaciones en skills.sh0
- pdfanthropicsOficialUse this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting/decrypting PDFs, extracting images, and OCR on scanned PDFs to make them searchable. If the user mentions a .pdf file or asks to produce one, use this skill.206.2 k instalaciones en skills.sh0
- docxanthropicsOficialUse this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files) or Word templates (.dotx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', '.dotx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx or .dotx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation.197.1 k instalaciones en skills.sh0
