channel-formatting
Convert Claude's Markdown output to each channel's native text syntax before delivery. Adds zero-dependency formatting for WhatsApp, Telegram, and Slack (marker substitution). Also ships a Signal rich-text helper (parseSignalStyles) used by the Signal skill.
Best for Multi-channel bot deploymen…Works with GitHubLow risk
⌘source
- author
@qwibitai- language
- TypeScript
★27kstars
12kforks
Apr 18, 2026
✦overview.md
Key Features
- ·Converts Markdown to native WhatsApp/Telegram/Slack syntax
- ·Preserves code blocks during transformation
- ·Provides Signal-specific text style helper
- ·Passthrough for Discord and Signal parseTextStyles
Use Cases
- →Ensuring Claude's responses render correctly on WhatsApp without literal asterisks
- →Making Telegram messages display bold and italic formatting natively
- →Formatting Slack messages with proper link syntax
- →Generating Signal-compatible text styles for use by Signal skill
Best for
- ✓Multi-channel bot deployments
- ✓Teams using WhatsApp/Telegram/Slack integration
Not ideal for
- !Single-channel applications
- !Platforms with native Markdown support like Discord
FAQs
name
channel-formatting
description
Convert Claude's Markdown output to each channel's native text syntax before delivery. Adds zero-dependency formatting for WhatsApp, Telegram, and Slack (marker substitution). Also ships a Signal rich-text helper (parseSignalStyles) used by the Signal skill.
Channel Formatting
This skill wires channel-aware Markdown conversion into the outbound pipeline so Claude's
responses render natively on each platform — no more literal **asterisks** in WhatsApp or
Telegram.
| Channel | Transformation |
|---|---|
**bold** → *bold*, *italic* → _italic_, headings → bold, links → text (url) | |
| Telegram | same as WhatsApp, but [text](url) links are preserved (Markdown v1 renders them natively) |
| Slack | same as WhatsApp, but links become <url|text> |
| Discord | passthrough (Discord already renders Markdown) |
| Signal | passthrough for parseTextStyles; parseSignalStyles in src/text-styles.ts produces plain text + native textStyle ranges for use by the Signal skill |
Code blocks (fenced and inline) are always protected — their content is never transformed.
Phase 1: Pre-flight
Check if already applied
test -f src/text-styles.ts && echo "already applied" || echo "not yet applied"
If already applied, skip to Phase 3 (Verify).
Phase 2: Apply Code Changes
Ensure the upstream remote
git remote -v
$install
1-click copynpx skills add qwibitai/nanoclaw --skill channel-formattingSafety assessment
★
Clarity score
How clear and easy to understand the SKILL.md instructions are, rated from 1 to 5.
3/ 5
goodMostly clear, but there are still a few confusing or poorly structured parts.
◎
Actionability score
How directly an agent can act on the SKILL.md instructions, rated from 1 to 5.
3/ 5
mediumPartially actionable with several concrete steps, but still missing important details.