← ClaudeAtlas

tg-operator-cardslisted

Use when a bot reports one event to the person who runs it — a payment, an order, an enrollment, a moderation decision — in an admin chat or a private chat with the owner. Shapes the message as a card read in two seconds on a phone: outcome and person on the first line, one fact per line, a status footer after the decision. Use tg-rich-messages for tables and long reports.
serejaris/telegram-skills · ★ 41 · AI & Automation · score 87
Install: claude install-skill serejaris/telegram-skills
# tg-operator-cards Input: the facts of one event. Output: a short `sendMessage` text in `parse_mode: HTML` for the operator of the bot. Three shapes share one layout: the **review card** (waits for a decision), the **receipt** (the bot already acted), and the **decision footer** (records who decided and when). Not for messages to customers, digests of many events ([`tg-rich-digest`](../tg-rich-digest/)), tables ([`tg-rich-messages`](../tg-rich-messages/)), or rewriting agent prose ([`tg-reply-rewrite`](../tg-reply-rewrite/)). Write in the operator's language. ## Rules 1. **First line: outcome and person.** It must make sense alone in a notification preview: `✅ Enrolled: Ada (@ada)`. Bold the outcome and the name. A review card starts with the thing to decide: `🧾 Order #482`. 2. **One fact per line.** Each line starts with one emoji that names the kind of fact: 🧾 order or application, 💳 money, ✉️ delivery to the person. The same emoji means the same kind of fact in every card of the bot. No blank lines inside a block. 3. **Label first, value second.** Bold only the values the operator checks against another system: the amount, the order number. Put values the operator copies in `<code>`: product code, ticket code, ID. 4. **A problem takes the place of the normal line.** Where the card would say what went fine, put ⚠️, what failed, and the next step in one sentence. The card keeps its shape, so the warning line is the one that looks different. 5. **Say what the bot did.