slack-formatting
Skill5 starsChanged 5 months agoMITView on GitHub
Format messages for Slack using mrkdwn syntax. Use when responding to Slack channels (folder starts with "slack_" or JID contains slack identifiers).
1 other project uses a version of this.
Adopted by
Most recently taken up by
- ssareli/skillstheir own version, first seen Apr 21, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- ssareli/skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository60 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- container/CLAUDE.mdCLAUDE.md
- add-amplifier-agentSkill
- add-atomic-chat-toolSkill
- add-codexSkill
- add-dashboardSkill
- add-deltachatSkill
- add-discordSkill
- add-emacsSkill
- add-gcal-toolSkill
- add-gchatSkill
- add-githubSkill
- add-gmail-toolSkill
- add-imessageSkill
- add-karpathy-llm-wikiSkill
- add-linearSkill
- add-macos-statusbarSkill
- add-matrixSkill
- add-mnemonSkill
- add-ollama-providerSkill
- add-ollama-toolSkill
- add-opencodeSkill
- add-parallelSkill
- add-resendSkill
- add-rtkSkill
- add-signalSkill
- add-slackSkill
- add-teamsSkill
- add-telegramSkill
- vercel-cliSkill
- add-vercelSkill
- add-webexSkill
- add-wechatSkill
- add-whatsapp-cloudSkill
- add-whatsappSkill
- clawSkill
- convert-to-apple-containerSkill
- customizeSkill
- debugSkill
- get-qodo-rulesSkill
- init-first-agentSkill
- init-onecliSkill
- manage-channelsSkill
- manage-mountsSkill
- migrate-from-openclawSkill
- migrate-from-v1Skill
- migrate-nanoclawSkill
- qodo-pr-resolverSkill
- setupSkill
- update-nanoclawSkill
- update-skillsSkill
- use-native-credential-proxySkill
- x-integrationSkill
- agent-browserSkill
- frontend-engineerSkill
- onecli-gatewaySkill
- self-customizeSkill
- vercel-cliSkill
- welcomeSkill
- whatsapp-formattingSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 2 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
When responding to Slack channels, use Slack's mrkdwn syntax instead of standard Markdown.
- Distinctive: line 12
Check your group folder name or workspace path:
- Very specific: line 49
Use • (bullet character) or - or * for bullets.
- Very specific: line 60
Use standard emoji shortcodes: :white_check_mark:, :x:, :rocket:, :tada:
- Very specific: line 89
Use *bold* not bold
- Very specific: line 91
Use • bullets, avoid numbered lists
≈ “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 Message Formatting (mrkdwn)
When responding to Slack channels, use Slack's mrkdwn syntax instead of standard Markdown.
How to detect Slack context
Check your group folder name or workspace path:
- Folder starts with
slack_(e.g.,slack_engineering,slack_general) - Or check
/workspace/group/path forslack_prefix
Formatting reference
Text styles
| Style | Syntax | Example |
| Bold | *text* | bold text |
| Italic | _text_ | italic text |
| Strikethrough | ~text~ | |
| Code (inline) | `code` | inline code |
| Code block | ```code``` | Multi-line code |
Links and mentions
<https://example.com|Link text> # Named link
<https://example.com> # Auto-linked URL
<@U1234567890> # Mention user by ID
<#C1234567890> # Mention channel by ID
<!here> # @here
<!channel> # @channelLists
Slack supports simple bullet lists but NOT numbered lists:
• First item
• Second item
• Third itemUse • (bullet character) or - or * for bullets.
Block quotes
> This is a block quote
> It can span multiple linesEmoji
Use standard emoji shortcodes: :white_check_mark:, :x:, :rocket:, :tada:
What NOT to use
- NO
##headings (use*Bold text*for headers instead) - NO
**double asterisks**for bold (use*single asterisks*) - NO
[text](url)links (use<url|text>instead) - NO
1.numbered lists (use bullets with numbers:• 1. First) - NO tables (use code blocks or plain text alignment)
- NO
---horizontal rules
Example message
*Daily Standup Summary*
_March 21, 2026_
• *Completed:* Fixed authentication bug in login flow
• *In Progress:* Building new dashboard widgets
• *Blocked:* Waiting on API access from DevOps
> Next sync: Monday 10am
:white_check_mark: All tests passing | <https://ci.example.com/builds/123|View Build>Quick rules
- Use
*bold*not**bold** - Use
<url|text>not[text](url) - Use
•bullets, avoid numbered lists - Use
:emoji:shortcodes - Quote blocks with
> - Skip headings — use bold text instead
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.

