メニュー
Ask a question via Telegram with inline buttons and wait for the user's response — either a button press or a free-text reply to the message. Use when you need user confirmation, input, or a decision before proceeding (e.g. "deploy to prod?", "which option?").
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Internal dependency, not a user action. Provides the shared `telegram` binary used by the telegram-notify, telegram-ask, and telegram-manage-contacts skills. Do not invoke this skill directly; install it because the others depend on it.
Manage Telegram contacts for the telegram-notify and telegram-ask skills. Use when the user asks to add, remove, or list Telegram contacts/recipients.
Send a one-way Telegram message to configured contacts. Use when the user asks to send a message, notify, ping, or alert via Telegram. Also use when you need to proactively notify the user about something (e.g. a long task completing). This skill is send-only and does NOT wait for or receive a reply — if you need an answer or decision back from the user, use the telegram-ask skill instead.
First-time setup for the Telegram skills — connect a bot and capture the user's chat ID. Use when the user wants to set up, connect, configure, or get started with Telegram notifications, or when another telegram skill fails because no bot token / chat is configured.
| name | telegram-ask |
| description | Ask a question via Telegram with inline buttons and wait for the user's response — either a button press or a free-text reply to the message. Use when you need user confirmation, input, or a decision before proceeding (e.g. "deploy to prod?", "which option?"). |
| metadata | {"author":"roziscoding","version":"1.0.0"} |
Ask questions via Telegram with inline keyboard buttons. The script blocks until the user answers — either by pressing a button or by replying directly to the question message — and prints the answer to stdout.
Create ~/.config/telegram-skills/credentials.json:
{
"bot_token": "your-bot-token-from-botfather",
"default_chat_id": "your-chat-id",
"contacts": {
"alice": "123456",
"bob": "789012"
}
}
The binary is at <skill-dir>/../telegram-skills-bin/bin/telegram. It reads the question from stdin. Use --choice to define the buttons.
Requires the
telegram-skills-binskill. The binary lives in that sibling skill. If<skill-dir>/../telegram-skills-bin/bin/telegramdoes not exist, tell the user to install it (bunx skills add roziscoding/telegram-skills) instead of failing with a raw error.
# Yes/No question
ANSWER=$(echo "Deploy to production?" | <skill-dir>/../telegram-skills-bin/bin/telegram --choice "Yes" --choice "No")
echo "User chose: $ANSWER"
# Multiple options
ANSWER=$(echo "Which environment?" | <skill-dir>/../telegram-skills-bin/bin/telegram --choice "staging" --choice "production" --choice "cancel")
# Ask a specific person by chat ID
ANSWER=$(echo "Approve release?" | <skill-dir>/../telegram-skills-bin/bin/telegram -c 123456 --choice "Approve" --choice "Reject")
# Ask a named contact
ANSWER=$(echo "Approve release?" | <skill-dir>/../telegram-skills-bin/bin/telegram --to alice --choice "Approve" --choice "Reject")
Usage: <bin> [-c chat_id ...] [--to name ...] --choice "Option" [--choice "Option" ...] — reads question from stdin. The script blocks until the user answers, then prints the answer to stdout. The user can either press a button (the chosen option's text is printed) or send a Telegram reply to the question message (the reply text is printed). Either way the original message is edited to show the answer and the buttons are removed.
--choice options