Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Use inline buttons when communicating with Rahul on Telegram (message tool) to reduce typing and force crisp decisions. Trigger when drafting Telegram messag...
Use inline buttons when communicating with Rahul on Telegram (message tool) to reduce typing and force crisp decisions. Trigger when drafting Telegram messag...
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
When sending a proactive message or asking Rahul to choose/confirm something on Telegram, prefer inline buttons over free-text prompts. Use buttons for: Y/N confirmations A/B (or A/B/C) choices “Do it now vs later” Selecting one of a few next actions Do not use buttons when: The message is purely informational (no action required) The user needs to paste/enter a value (then ask for text input) There are >5 options (summarize + offer “Show more”)
Keep button labels short (1–4 words) 2–4 buttons is ideal Always include a safe escape hatch when appropriate: “Not now” / “Later” / “Skip” Map button presses to clear next actions in follow-up turns
Telegram doesn’t support arbitrary text color in normal bot messages. To make the selection visually pop, do this automatically after a click: Edit the original message to remove the inline keyboard Append a standout selection line using emoji / symbols (chosen based on meaning)
✅ / 🟩 = approve / yes / proceed / confirm 🟥 = no / cancel / stop ⬛ = later / skip / defer Do not send an extra follow-up message that repeats the selection—editing is sufficient unless there’s additional context/results to report. Tooling rule: if you used functions.message (send/edit) as the user-visible delivery, respond in chat with NO_REPLY (unless you need to include additional results/details beyond what the edit shows).
If a callback arrives after the message was already finalized (buttons removed / selection committed), do nothing: No extra message No additional edits Just silently ignore
When using functions.message with action=send, include a buttons grid. Recommended layouts:
Row 1: ["Yes"] ["No"]
Row 1: ["Do it"] ["Not now"] Row 2: ["More info"]
Row 1: ["A"] ["B"] ["C"]
Text: "Want me to proceed with <action>?" Buttons: [Proceed] [Hold]
Text: "Pick the next move:" Buttons: [Option A] [Option B] [Option C] [Not now]
Text: "When should I remind you?" Buttons: [15m] [1h] [Tonight] [Tomorrow]
If a button-triggered flow will branch, keep the first message short; put details in the follow-up after the click. Multi-step flows: (1) edit prior message to commit selection, then (2) send the next question with buttons. Don’t narrate the selection separately. Keep callback_data stable and unique per flow step (e.g., flow_step_choice).
Messaging, meetings, inboxes, CRM, and teammate communication surfaces.
Largest current source with strong distribution and engagement signals.