slackapi/slack-skills-plugin

slack-messaging

Use when writing, drafting, scheduling, or improving a Slack message, announcement, or reply sent via the Slack MCP tools (slacksendmessage, slacksendmessagedraft, slackschedulemessage).

Voir la source

Mode d’emploi

  1. Copiez la commande et examinez le paquet avant de l’installer dans votre environnement agent.
  2. Consultez le document original pour les outils, identifiants et environnements requis.
  3. Décrivez les entrées et le livrable souhaité ; comparez la sortie aux sources.
npx skills add https://github.com/slackapi/slack-skills-plugin --skill slack-messaging

Avant de commencer

  • L’installation n’inclut ni abonnement au modèle, ni quota API, ni accès aux fichiers.
  • Étoiles et installations reflètent l’activité, pas un test indépendant de qualité ou de sécurité.
Document Skill original

Rendu depuis le dépôt source en conservant titres, exemples, code, tableaux, liens et images.

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_schedule_message. The formatting rules below cover these message tools. slack_create_canvas uses a different, richer markdown dialect — see the Canvas note below.

Formatting

The message tools (slack_send_message, slack_send_message_draft, slack_schedule_message) accept standard markdown and convert it to Slack formatting on send. Write normal markdown. Do not use Slack's legacy mrkdwn syntax (*bold*, ~strike~); those single-character forms mean something different in standard markdown. Each text element is limited to ~5000 characters.

FormatSyntax
Bold**text**
Italic_text_ (or *text*)
Strikethrough~~text~~
Code (inline) code
Quote> text
Link[display text](url)
Bulleted list- item
Numbered list1. item

Block elements also work. Write them as literal markdown:

  • Code block with an optional language for syntax highlighting:
`text

print("hello")

  • Table with | delimiters (escape a literal pipe inside a cell as \|):
text
  | Feature | Status |
  |---------|--------|
  | Tables  | works  |
  • Headers with # / ## / ###:
text
  ## Section title

The one thing that does not embed in a message: inline images (![alt](url)) typically render as a plain link rather than an inline image. For rich embedded layouts (buttons, images, structured cards) you need Block Kit; for a document-style surface where images do embed, use a canvas. See the Notes below.

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 (the ~5000-character limit is a ceiling, not a target). If the message is long or structured, consider 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.
  • For simple acknowledgments, add an emoji reaction with slack_add_reaction instead of a reply message (use slack_get_reactions to read existing reactions).
  • When writing announcements, use a clear structure: context, key info, call to action.

Scheduling

  • Use slack_schedule_message to post later. post_at is a Unix timestamp that must be at least 2 minutes in the future and at most 120 days out; the message body uses the same standard markdown as above.
  • Scheduled messages can't be edited via the API once set — the user manages them from Drafts & sent in Slack.

Notes

  • Canvas formatting is different. slack_create_canvas uses Canvas-flavored Markdown, a richer dialect than the message tools: headers, tables, checklists, and inline images (![alt](url)) all embed, and it also supports user/channel reference cards, callouts, and columns. Do not assume the message rules above apply — follow the slack_create_canvas tool's own formatting guidance when composing a canvas.
  • Scope: this skill owns composing and formatting the text of messages sent through the Slack MCP message tools. For interactive layouts (buttons, menus, modals, Home tabs, or any Block Kit JSON), use the block-kit skill, which composes and validates the block payload. For calling the Slack Web API directly (chat.postMessage and friends) rather than the MCP tools, use the slack-api skill.
du même dépôt

Autres Skills

Tous les Skills
slackapi
Communauté

block-kit

Use when a developer wants to build or validate Block Kit layouts for Slack messages, modals, or Home tabs: message layouts, modals/forms/dialogs, Home tab interfaces, interactive buttons or menus, or modifying existing Block Kit JSON. Also trigger on any Slack UI component (sections, actions, inputs, headers, alerts, tables, carousels), the words "blocks" or "Block Kit Builder", a request to preview rendered blocks, or pasted JSON like "type": "section". Validates via the blocks.validate API me

Installations / 1h
2
GitHub Stars
170
Mis à jour
18 nov.
slackapi
Communauté

create-slack-app

Use when a developer wants to create, scaffold, or bootstrap a new Slack app or agent from scratch with the Slack CLI, or scaffold the project for a new app just created in App Settings (--app, --template, --team). Covers prerequisites, authentication, choosing a workspace to install into, and creating a project from a Bolt (JS or Python) template locally. Trigger on "create a Slack app", "new Bolt app", "start a Slack agent".

Installations / 1h
2
GitHub Stars
170
Mis à jour
18 nov.
slackapi
Communauté

deploy-slack-app

Use when a developer wants to deploy, host, or run a Slack app somewhere it keeps working after the local process stops, or mentions Railway, Heroku, railway up, git push heroku, slack deploy, a deploy hook in .slack/hooks.json, hosting a Socket Mode or Request URL (HTTP) Bolt app, deploying from Windows, graduating an app out of a developer sandbox, or tearing down a deployed app. Not for conceptual questions about how Slack app hosting works, which the slack-docs skill answers.

Installations / 1h
2
GitHub Stars
170
Mis à jour
18 nov.
slackapi
Communauté

slack-api

Use when a developer asks which Slack Web API method does something, needs a method's OAuth scopes or token type, wants to call or test a family.method endpoint (chat.postMessage, conversations.history, users.info, views.open), is handling cursor pagination (nextcursor) or rate limits (tier/ratelimited/Retry-After), or is debugging errors like missingscope, invalidauth, or channelnotfound. Also trigger on a pasted slack.com/api/ URL or docs.slack.dev/reference/methods link.

Installations / 1h
2
GitHub Stars
170
Mis à jour
18 nov.