skills$openclaw/telegram-compose
tmchow3.6k

by tmchow

telegram-compose – OpenClaw Skill

telegram-compose is an OpenClaw Skills integration for writing workflows. |

3.6k stars2.5k forksSecurity L1
Updated Feb 7, 2026Created Feb 7, 2026writing

Skill Snapshot

nametelegram-compose
description| OpenClaw Skills integration.
ownertmchow
repositorytmchow/telegram-compose
languageMarkdown
licenseMIT
topics
securityL1
installopenclaw add @tmchow/telegram-compose
last updatedFeb 7, 2026

Maintainer

tmchow

tmchow

Maintains telegram-compose in the OpenClaw Skills directory.

View GitHub profile
File Explorer
2 files
.
_meta.json
462 B
SKILL.md
4.2 KB
SKILL.md

name: telegram-compose description: | Compose rich, readable Telegram messages using HTML formatting via direct Telegram API. Use when: (1) Sending any Telegram message beyond a simple one-line reply, (2) Creating structured messages with sections, lists, or status updates, (3) Need formatting unavailable via Clawdbot's Markdown conversion (underline, spoilers, expandable blockquotes, user mentions by ID), (4) Sending alerts, reports, summaries, or notifications to Telegram, (5) Want professional, scannable message formatting with visual hierarchy. Default to this skill for substantive Telegram communication.

Telegram Compose

Rich, scannable Telegram messages via direct API with HTML formatting.

Credentials

Bot tokens: Stored in Clawdbot config at channels.telegram.accounts.<name>.botToken

# Get token from config
BOT_TOKEN=$(jq -r '.channels.telegram.accounts.alerts.botToken' ~/.clawdbot/clawdbot.json)
# Or for main bot:
BOT_TOKEN=$(jq -r '.channels.telegram.accounts.main.botToken' ~/.clawdbot/clawdbot.json)

Chat IDs: See TOOLS.md → Telegram section for configured chat IDs.


Direct API Call

# Get token and send
BOT_TOKEN=$(jq -r '.channels.telegram.accounts.alerts.botToken' ~/.clawdbot/clawdbot.json)
CHAT_ID="TARGET_CHAT_ID"  # See TOOLS.md

curl -s -X POST "https://api.telegram.org/bot${BOT_TOKEN}/sendMessage" \
  -H "Content-Type: application/json" \
  -d "$(jq -n --arg chat "$CHAT_ID" --arg text "$MESSAGE" '{
    chat_id: $chat,
    text: $text,
    parse_mode: "HTML"
  }')"

HTML Tags

<b>bold</b>  <i>italic</i>  <u>underline</u>  <s>strike</s>
<code>mono</code>  <pre>code block</pre>
<tg-spoiler>hidden until tapped</tg-spoiler>
<blockquote>quote</blockquote>
<blockquote expandable>collapsed by default</blockquote>
<a href="url">link</a>
<a href="tg://user?id=123">mention by ID</a>

Escape in text: <&lt; >&gt; &&amp;


Structure Pattern

EMOJI <b>HEADING IN CAPS</b>

<b>Label:</b> Value
<b>Label:</b> Value

<b>SECTION</b>

• Bullet point
• Another point

<blockquote>Key quote or summary</blockquote>

<blockquote expandable><b>Details</b>

Hidden content here...
Long details go in expandable blocks.</blockquote>

<a href="https://...">Action Link →</a>

Examples

Status update:

📋 <b>TASK COMPLETE</b>

<b>Task:</b> Deploy v2.3
<b>Status:</b> ✅ Done
<b>Duration:</b> 12 min

<blockquote>All health checks passing.</blockquote>

Alert:

⚠️ <b>ATTENTION NEEDED</b>

<b>Issue:</b> API rate limit at 90%
<b>Action:</b> Review usage

<a href="https://dashboard.example.com">View Dashboard →</a>

List:

✅ <b>PRIORITIES</b>

• <s>Review PR #234</s> — done
• <b>Finish docs</b> — in progress
• Deploy staging

<i>2 of 3 complete</i>

Style Rules

  1. Faux headings: EMOJI <b>CAPS TITLE</b> with blank line after
  2. Emojis: 1-3 per message as visual anchors, not decoration
  3. Whitespace: Blank lines between sections
  4. Long content: Use <blockquote expandable>
  5. Links: Own line, with arrow: Link Text →

Avoid Markdown Tables

Markdown tables render too wide on mobile — often unreadable. Use these alternatives:

Vertical key-value (best for 2-3 columns):

<pre>
hzl-cli: 1.11.1 → 1.12.0
skill:   1.0.5 → 1.0.6
</pre>

Compact list with separators:

<pre>
▸ hzl-cli │ 1.12.0 ✓
▸ skill   │ 1.0.6 ✓
</pre>

Record cards (multi-field rows):

<b>Ruby</b>
Birthday: Jun 16 · Age: 11

<b>Rhodes</b>
Birthday: Oct 1 · Age: 8

Bullet lists (simplest):

• <b>hzl-cli:</b> 1.12.0
• <b>skill:</b> 1.0.6

Rule: Reserve <pre> blocks for code/commands. For structured data, use bullets + bold or vertical key-value.


Limits

  • Message: 4,096 chars
  • Caption: 1,024 chars

When to Use Direct API vs Clawdbot

Direct APIClawdbot message tool
Structured messagesQuick acknowledgments
Status/alerts/reportsSimple replies
Need underline/spoiler/expandableBasic formatting sufficient
Visual hierarchy mattersThrowaway messages
README.md

No README available.

Permissions & Security

Security level L1: Low-risk skills with minimal permissions. Review inputs and outputs before running in production.

Requirements

  • OpenClaw CLI installed and configured.
  • Language: Markdown
  • License: MIT
  • Topics:

FAQ

How do I install telegram-compose?

Run openclaw add @tmchow/telegram-compose in your terminal. This installs telegram-compose into your OpenClaw Skills catalog.

Does this skill run locally or in the cloud?

OpenClaw Skills execute locally by default. Review the SKILL.md and permissions before running any skill.

Where can I verify the source code?

The source repository is available at https://github.com/openclaw/skills/tree/main/skills/tmchow/telegram-compose. Review commits and README documentation before installing.