serejaris/telegram-skills / skills/tg-operator-cards
tg-operator-cards
VerifiedUse 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.
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), tables (tg-rich-messages), or rewriting agent prose (tg-reply-rewrite). Write in the operator's language.
Rules
- 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. - 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.
- 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. - 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.
- Say what the bot did.
Confirmation sent, notsent him the confirmation. In languages with grammatical gender this keeps the card correct for every person. - Format numbers for reading.
19 000 ₽, not19000. Name the moment a date refers to:Paid … on 08.11, not a bare date. - No filler. No "successfully", no "please note", no closing period on a one-fact line.
- Escape
&,<,>in every dynamic value. Names come from users. One unescaped<and Telegram rejects the whole message with400 can't parse entities: the action happened, and the operator saw nothing. - The decision edits the card. When the operator presses a button, edit the same message with
editMessageText: the same card text, a footer line, and no decision buttons. One event stays one message in the chat. - What the bot knows about the person is a second block. After one blank line: a count line, then past orders oldest first, each with its period and amount. Name where the knowledge ends (
in the bot), so an empty history is not read as a new customer. Leave the current order out of the list. When the history cannot be read, omit the block:noneis a claim, not a fallback. - In a private chat the person block can be a widget. Send the person, the current order and their history as an HTML widget (
tg-widgets). The caption carries the first line and only the facts the widget does not show: a client that draws widgets puts the caption right under the widget, and a repeated fact is read twice. A client without widget support shows only the caption, so its first line still names the outcome and the person. Give the widget a button only for an action the operator takes: no copy button for a value nobody pastes. Groups refuse widgets today, see the delivery table in tg-widgets: there the card stays text. When the server refuses the widget, send the full text card instead.
Limits
| Part | Limit | Source |
|---|---|---|
| Event block | up to 6 lines | editorial, one glance |
| Person block | count line and up to 5 items | editorial; the count names the total |
| Line | about 45 characters | editorial, no wrap on a phone |
sendMessage text | 4 096 characters after entity parsing | Bot API |
callback_data | 1–64 bytes | Bot API |
An event that needs more than six lines is a report: send it with tg-rich-messages.
Examples (invented data)
Receipt, before:
Enrolled: Ada (@ada). Application #77, Autumn cohort.
Recorded payment 19000 ₽ from 08.11.2026 — the ledger will use it.
Ledger row exists, product code cohort_autumn_early.
Sent him the confirmation in a private message.
Receipt, after:
✅ <b>Enrolled: Ada</b> (@ada)
🧾 Application <b>#77</b> · Autumn cohort
💳 Paid <b>19 000 ₽</b> on 08.11.2026
📒 Ledger: recorded, code <code>cohort_autumn_early</code>
✉️ Confirmation sent
The same receipt when two steps failed (rule 4):
✅ <b>Enrolled: Ada</b> (@ada)
🧾 Application <b>#77</b> · Autumn cohort
💳 Paid <b>19 000 ₽</b> on 08.11.2026
⚠️ Ledger: row not written. Run the same command again, the retry adds it.
⚠️ Message not delivered: the bot is not started or the chat is closed
The receipt with the person block (rule 10), for a returning customer and for a first order:
✉️ Confirmation sent
🎓 Past programs in the bot: <b>2</b>
• Spring cohort · March 2026 · 39 000 ₽
• Summer cohort · June 2026 · 35 000 ₽
✉️ Confirmation sent
🎓 No past programs in the bot
The caption under the widget (rule 11). Plain text: the widget shows the application, the payment and the history, the caption adds the rest:
✅ Enrolled: Ada (@ada)
📒 Ledger: recorded, code cohort_autumn_early
✉️ Confirmation sent
Review card with Confirm and Reject buttons, then the footer after the decision (rule 9):
🧾 <b>Order #482</b> · pinned post
👤 Ada Lovelace (@ada)
🎟 Tickets: <b>2</b>
💳 Card: <b>80 $</b>
✅ <b>CONFIRMED</b> · Grace, 14:02 · code <code>K7Q2</code>
Building a line (rule 8):
from html import escape
head = f"✅ <b>Enrolled: {escape(first_name)}</b> (@{escape(username)})"
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |