ccheney/robust-skills/slack-mrkdwn

Slack Text Formatting

Format the supplied content for the actual receiving field. The user's explicit instructions take precedence over this skill's guidelines.

Select the renderer

Use the text and destination field/method as input. Infer the destination from the existing payload; if it is unclear and changes the syntax, ask which surface receives the text. For an ordinary Slack message with no other context, state that you are using message text and mrkdwn.

Preserve content and controls

• Escape untrusted &, <, and > in mrkdwn, in that order. JSON escaping is separate. verbatim: true does not neutralize explicit <...> controls.
• Use real IDs for mentions and channels. If an ID is missing, leave a clearly labeled template value or ask for it when the output must be ready to send; do not guess from a display name.
• Preserve intended mentions and links without introducing broad notifications. Date controls need a fallback containing timezone information.
• Keep supplied fallback text complete and aligned with block content. Do not assume block rendering supplies mobile notification text.
• Check field-specific limits and method combination rules; non-streaming markdown_text cannot be combined with text or blocks on the documented chat methods.

Return the requested formatted string, text object, or corrected payload. Preserve meaning and explain a renderer mismatch when fixing one. A formatting task can be completed without posting; send only when that action is requested or already authorized.

References

Read only the part needed for the destination or control syntax.

For changing surface support, use Slack's formatting guide and the receiving field/method reference.