Format messages for Telegram Markdown bold italic links code
Scanned 9/10/2026
Install to Claude Code
npx -y skills add LoopyLuci/Skills --skill telegram-message-formatting --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Telegram Message Formatting?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/loopyluci-telegram-message-formatting)More formats (shields.io, HTML) on the badges page.
---
name: telegram-message-formatting
description: "Format messages for Telegram Markdown bold italic links code"
---
# Telegram Message Formatting
Telegram uses a **subset** of Markdown. These rules ensure your messages render correctly.
## Supported Formatting
| Style | Syntax | Example |
|-------|--------|---------|
| Bold | `**text**` | **bold** |
| Italic | `*text*` | *italic* |
| Underline | `__text__` | <u>underline</u> |
| Strikethrough | `~~text~~` | ~~strikethrough~~ |
| Spoiler | `\|\|text\|\|` | ||spoiler|| |
| Inline code | `` `code` `` | `code` |
| Code block | ```` ```lang ... ``` ```` | Multi-line code |
| Links | `[text](url)` | [link](https://example.com) |
| Pre-formatted | Indented 4 spaces | Preserved whitespace |
## Critical Rules
**1. No nested formatting** — bold inside italic, code inside bold all fail silently.
```diff
- **bold *and italic** text* ← BROKEN
+ **bold text** and *italic* ← OK separately
```
**2. Link text cannot contain formatting** — `**[bold link](url)**` does NOT work. Use `[bold link](url)` in bold context instead.
**3. Code blocks need a language hint** for syntax highlighting on mobile:
````
```python
print("hello")
```
````
**4. Emoji within formatting** — most emoji work inside bold/italic but some break. Test if unsure.
**5. Escape special characters** with backslash if they appear literally:
```
\*not italic\* \`not code\`
```
## Headers
Only `## Header` (level 2) renders as a header. `#` and `###` show as plain text.
```
## This renders as header
# This does not
```
## Best Practices
| Goal | Do This |
|------|---------|
| Key-value pairs | `**Name:** Value` on its own line |
| Bullet lists | `- item` with blank line before list |
| Code in lists | Use 4-space indent after `- ` |
| Mixed content | Use separate lines, not inline mixing |
| Status indicators | Use ✅ ❌ ⚠️ 🔥 ● ○ at line start |
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!