Agent skill
slack-formatting
Format messages for Slack using mrkdwn syntax. Use when responding to Slack channels (folder starts with "slack_" or JID contains slack identifiers).
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/slack-formatting
SKILL.md
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> # @channel
Lists
Slack supports simple bullet lists but NOT numbered lists:
• First item
• Second item
• Third item
Use • (bullet character) or - or * for bullets.
Block quotes
> This is a block quote
> It can span multiple lines
Emoji
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
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?