channel-formatting

To convert Markdown to native formatting for Slack and WhatsApp, this Skill parses Markdown styles and swaps markers for channel-specific syntax. It ensures text styling appears natively instead of as literal markup in messaging apps.

Your agent sends literal Markdown asterisks in Telegram messages because outbound text lacks channel-native conversion. This Skill translates Markdown markers into Telegram's native syntax before delivery to prevent raw markup from appearing.

Discord supports inbound Markdown conversion natively, so this Skill leaves Discord text untouched. It focuses conversion efforts on WhatsApp, Telegram, Slack, and Signal, automatically detecting channel metadata to apply the correct formatting rules.

The best way to protect code blocks when translating Markdown for messaging apps is to use a dedicated parser that guards them. This Skill isolates code blocks during style conversion so channel-native formatting does not corrupt code syntax.

You can render native text styles in Signal from a Markdown response by generating plain text with structured textStyle ranges. This Skill outputs these ranges so the Signal skill can apply native styling without using literal Markdown markers.

To route channel metadata to format outbound bot messages, you configure a router function to accept channel names from sendMessage calls. This Skill requires a formatOutbound router to pass metadata alongside parsing utilities for accurate styling.