Telegram Compose

**Summary:** This update requires callers to explicitly specify the Telegram bot account for all deliveries; auto-selection of accounts is no longer allowed. - The bot account name (e.g., "main") must now be provided by the caller for every message; the skill will not auto-select or iterate accounts. - Session/task templates and documentation updated to require explicit `Bot account: <account_name>` specification. - Credentials section and all usage examples revised to validate and use only the specified account. - Added `metadata` with OS, binary, network, and credential requirements. - Improved error handling and validation message if account is missing or invalid. - No runtime/code file changes—documentation only.

**Major update:** Skill now runs as an auto-invoked sub-agent for structured Telegram message formatting and delivery. - Skill acts as a sub-agent, automatically called for substantive Telegram messages (>3 lines or with lists/sections) by the main session agent. - Clear decision rule: short/simple replies use OpenClaw message tool; structured/rich messages go through this skill. - Sub-agent receives the skill path, chat/thread IDs, and raw content, then formats and sends via Telegram API. - Expanded error handling: retries on formatting errors, splitting long messages, and fallbacks to plain text as needed. - Formatting and style rules clarified (escaping, structure, mobile display best practices). - Direct invocation and functional details are now internal; other skills do not need to call this explicitly.

Expanded OpenClaw compatibility and clarified formatting best practices: - Updated references and instructions for OpenClaw config location and usage (now supports both openclaw.json and legacy clawdbot.json). - Improved credential and API call sections, including dynamic account selection and how to send to topic threads. - Clarified HTML tag usage and escaping, with more Telegram-specific context. - Expanded guidance for message layout: strict rule against using <pre> for visual layouts, with concrete good/bad mobile examples. - Updated comparison: when to use direct API vs OpenClaw message tool. - Minor terminology updates (e.g., Clawdbot → OpenClaw) for clarity.

- Advises against using Markdown tables due to poor mobile readability on both desktop and mobile pclients. - Provides multiple structured message formats as alternatives, including vertical key-value, compact lists, record cards, and bullet lists. - Recommends reserving <pre> blocks for code/commands or key-value data, with bullets and bold for general structure.

Initial release of telegram-compose — a skill for composing rich, structured Telegram messages via direct API with advanced HTML formatting. - Provides example commands and configuration steps for sending messages with HTML tags. - Details available HTML formatting options, including headings, expandable blockquotes, user mentions by ID, and spoilers. - Supplies clear structural and stylistic guidelines for professional, scannable messaging. - Outlines use cases, message limits, and decision criteria for when to use direct API over Clawdbot’s Markdown conversion. - Includes practical message templates for alerts, status updates, and lists.