draft-message
Draft a Telegram Message (via Saved Messages)
Send a message to the user's Saved Messages so the user can review it, optionally edit it, then copy-paste it into the target chat's compose area before sending. Saved Messages is every Telegram account's built-in private chat with itself — it syncs across all clients automatically.
Why Saved Messages, not MTProto cloud drafts? The official Telegram clients have a known unfixed race condition (tdesktop#29111, closed "not planned") where the local empty-draft state silently overwrites cloud drafts pushed via
SaveDraftRequestfrom another authorization. We observed this in practice: the server confirmed the draft, but the user's compose area stayed empty. Saved Messages bypasses this entirely — full HTML formatting is preserved, and Telegram's native copy-paste between compose areas preserves rich text across iOS, Android, Desktop, and Web.
Self-Evolving Skill: This skill improves through use. If instructions are wrong, parameters drifted, or a workaround was needed — fix this file immediately, don't defer. Only update for real, reproducible issues.
When To Use Draft vs. Send
| Situation | Use |
|---|---|
| Long or multi-paragraph message an agent composed autonomously | Draft — let the human eyeball it before it lands |
| Message carries sensitive wording (hiring, firing, contract terms) | Draft — one typo or wrong name is expensive |
| Reply where tone matters (addressing a peer or an external party) | Draft — AI-generated tone can be subtly off |
| Short confirmations, status updates, routine responses | Send — friction of drafting exceeds value |
| Automated notifications, alerts, scheduled pings | Send — no human-in-the-loop needed |
| Time-critical message where draft→review→send round-trip is too slow | Send — accept the risk |
More from terrylica/cc-skills
pandoc-pdf-generation
PDF generation from markdown via Pandoc/XeLaTeX. TRIGGERS - markdown for PDF, print document, pandoc
379mise-tasks
Orchestrate multi-step project workflows using mise task definitions with dependency management and argument handling. Use whenever the user.
328python-logging-best-practices
Python logging with loguru, structlog, and orjson. TRIGGERS - loguru, structlog, structured logging
326mql5-indicator-patterns
MQL5 indicator development patterns. TRIGGERS - MQL5 indicator, OnCalculate, indicator buffers, MetaTrader 5.
324semantic-release
Automate versioning with Node.js semantic-release v25+. TRIGGERS - npm run release, version bump, changelog, conventional commits, release automation.
213latex-build
LaTeX builds with latexmk and live preview. TRIGGERS - latexmk, LaTeX build, live preview, compilation.
167