slack-mrkdwn
Skill60 starsChanged 2 months agoMITView on GitHub
Format or debug Slack message text, mentions, links, dates, and escaping. Use when choosing Slack mrkdwn versus Markdown, rich_text, or plain_text for a receiving field; not Block Kit layout or Slack history retrieval.
In this repository10 other files it gives its agents.
- bazelSkill
- clean-ddd-hexagonalSkill
- feature-slicingSkill
- mermaid-diagramsSkill
- modern-cssSkill
- modern-javascriptSkill
- postgres-drizzleSkill
- slack-block-kitSkill
- teams-adaptive-cardsSkill
- teams-message-formattingSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 24
Use real IDs for mentions and channels.
- Distinctive: line 26
Keep supplied fallback text complete and aligned with block content.
- Very specific: line 27
Check field-specific limits and method combination rules.
- Distinctive: line 33
Read only the part needed for the destination or control syntax.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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.
| Destination | Format | |
Message text, type: "mrkdwn" objects | Slack mrkdwn: *bold*, `<url | label>` |
markdown block, markdown_text, Work Object Markdown fields | Standard Markdown: **bold**, [label](url) | |
rich_text block | Nested elements and style objects, not markup strings | |
Labels or plain_text objects | Literal text |
Preserve content and controls
- Escape untrusted
&,<, and>in mrkdwn, in that order. JSON escaping is separate.verbatim: truedoes 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_textcannot be combined withtextorblockson 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.
| Task | Reference |
| Markdown surfaces, text objects, rich text, Work Object text | RENDERERS.md |
| mrkdwn syntax, mentions, date tokens, escaping | SYNTAX.md |
| Links/unfurls, parse flags, notifications, legacy attachments | MESSAGE-BEHAVIOR.md |
| Compact field and syntax lookup | CHEATSHEET.md |
For changing surface support, use Slack's formatting guide and the receiving field/method reference.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.