agentleFS
MicrosoftKnown publishermicrosoft/amplifier-app-nanoclaw/container/skills/slack-formatting/SKILL.md

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

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
  1. Distinctive:

    When responding to Slack channels, use Slack's mrkdwn syntax instead of standard Markdown.

    line 8
  2. Distinctive:

    Check your group folder name or workspace path:

    line 12
  3. Very specific:

    Use • (bullet character) or - or * for bullets.

    line 49
  4. Very specific:

    Use standard emoji shortcodes: :white_check_mark:, :x:, :rocket:, :tada:

    line 60
  5. Very specific:

    Use *bold* not bold

    line 89
  6. Very specific:

    Use • bullets, avoid numbered lists

    line 91

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
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 for slack_ prefix

Formatting reference

Text styles

StyleSyntaxExample
Bold*text*bold text
Italic_text_italic text
Strikethrough~text~strikethrough
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

  1. Use *bold* not **bold**
  2. Use <url|text> not [text](url)
  3. Use • bullets, avoid numbered lists
  4. Use :emoji: shortcodes
  5. Quote blocks with >
  6. Skip headings — use bold text instead

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.