Index of every page on this site: llms.txt
All skills
ccheney avatar

/slack-mrkdwn

@0eea7b0
Run it yourself

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.

Use this Skill: https://skilld.dev/gh/ccheney/robust-skills/slack-mrkdwn

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈58 tokens for metadata: the name and description. ≈647 when used: this file. ≈6.1k more on demand in 4 files.

Description uses 2.9% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈233 characters, or 2.9%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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

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.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts2mo4 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    The skill provides comprehensive instructions and reference material for formatting Slack messages across different surfaces (mrkdwn, Markdown, rich text). It includes proactive security guidance for escaping untrusted input and preventing data exfiltration via Slack's link unfurling mechanism. No executable code or security vulnerabilities were detected.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: LOW · No issues

  • Runlayer8mo

    2 files scanned · No issues

Signed by skilld at 0eea7b0. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last month.

Steadyupdated 2 months ago

README badge

README badge for ccheney/robust-skills/slack-mrkdwn