opencode-skills-collection 4.0.0 → 4.0.2

package/bundled-skills/telegram-bot-messaging/README.md

@@ -0,0 +1,185 @@
+# Telegram Skill
+
+An AI agent skill for sending Telegram messages, files, and alerts via the Bot API - send updates, ask-and-wait for approval with inline buttons, and read replies. Works with Claude Code, Gemini CLI, Cursor, OpenAI Codex, Goose, and other AI clients supporting the [Agent Skills Standard](https://agentskills.io).
+
+## Features
+
+- **Send** - Plain text, MarkdownV2, or HTML messages (auto-splits over 4096 chars, auto-falls back to plain text if formatting is rejected)
+- **File** - Send documents; images (png/jpg/jpeg/gif/webp) are automatically sent as photos
+- **Ask** - Ask a question with inline buttons and wait for a tap or free-text reply (approve-from-phone)
+- **Read** - Print new incoming messages since the last read
+- **Multi-bot** - Register additional named bots alongside the default
+- **Multi-target** - Route messages to named chats, groups, or channels
+- **Hook integration** - Wire into Claude Code hooks, cron jobs, or CI for notifications
+
+Pure bash + curl + jq — no install beyond a bot token.
+
+## Requirements
+
+- `bash`
+- `curl`
+- `jq` (`brew install jq` on macOS, `apt install jq` on Debian/Ubuntu)
+
+macOS ships bash and curl out of the box; only `jq` typically needs installing.
+
+## Quick Start
+
+### 1. Create a bot
+
+1. Open [@BotFather](https://t.me/BotFather) in Telegram
+2. Send `/newbot` and follow the prompts (display name, then a username ending in "bot")
+3. BotFather replies with an HTTP API token
+
+### 2. Run setup
+
+```bash
+bash scripts/telegram.sh setup
+```
+
+This walks you through pasting the token, validates it via `getMe`, and asks you to send a message to your new bot so it can discover your chat ID. Config is written to `~/.config/telegram/config` (mode 600), and a confirmation message is sent to confirm everything works.
+
+### 3. Add more bots (optional)
+
+```bash
+bash scripts/telegram.sh setup --bot alerts
+```
+
+Repeat with a different `--bot NAME` for each additional bot. Named bots share the default chat ID unless you configure a different target for them.
+
+### 4. Find group/channel IDs (optional)
+
+To send to a group or channel instead of your personal chat:
+
+1. Add your bot to the group/channel
+2. Send any message in that group/channel
+3. Run `bash scripts/telegram.sh read --all` to see the chat ID printed alongside the message
+4. Add `TARGET_<NAME>=<chat_id>` to `~/.config/telegram/config`, then use `--to <name>`
+
+## Usage Examples
+
+### Send Messages
+
+```bash
+# Basic alert
+bash scripts/telegram.sh send "Deploy finished ✅"
+
+# No notification sound
+bash scripts/telegram.sh send "low priority update" --silent
+
+# MarkdownV2 formatting (falls back to plain text if rejected)
+bash scripts/telegram.sh send "*bold* alert" --format md
+
+# HTML formatting
+bash scripts/telegram.sh send "<b>bold</b> alert" --format html
+
+# Named target and named bot
+bash scripts/telegram.sh send "hi" --to alerts --bot work
+```
+
+### Send Files
+
+```bash
+# Send a document
+bash scripts/telegram.sh file report.pdf "Q3 report"
+
+# Images are auto-detected and sent as photos
+bash scripts/telegram.sh file screenshot.png "Build output"
+
+# To a named target, silently
+bash scripts/telegram.sh file backup.zip --to alerts --silent
+```
+
+### Ask and Wait for an Answer
+
+```bash
+# Default Yes/No options, 5-minute timeout
+ANSWER=$(bash scripts/telegram.sh ask "Deploy to prod?" --options "Yes,No" --timeout 300)
+echo "$ANSWER"
+
+# Custom options
+bash scripts/telegram.sh ask "Which environment?" --options "Staging,Prod,Cancel"
+```
+
+Exit code `0` means answered (the answer is printed to stdout); exit code `2` means the timeout was reached with no reply.
+
+### Read Incoming Messages
+
+```bash
+# New messages since the last read (advances the offset)
+bash scripts/telegram.sh read
+
+# Limit the number of messages
+bash scripts/telegram.sh read --limit 5
+
+# Ignore the saved offset and show everything available
+bash scripts/telegram.sh read --all
+```
+
+Note: `ask` and `read` share the same per-bot cursor, so an `ask` consumes incoming messages that a later `read` would otherwise show.
+
+## Command Reference
+
+| Command | Description | Arguments | Exit codes |
+|---------|-------------|-----------|------------|
+| `setup` | Guided bot registration + chat-ID discovery | `--bot NAME` | 0 success, 1 error |
+| `send MESSAGE` | Send a text message | `--to TARGET`, `--bot NAME`, `--silent`, `--format md\|html` | 0 success, 1 error |
+| `file PATH [CAPTION]` | Send a document (or photo for images) | `--to TARGET`, `--bot NAME`, `--silent` | 0 success, 1 error |
+| `ask QUESTION` | Ask with inline buttons, wait for reply | `--options "Yes,No"`, `--timeout SECS`, `--to TARGET`, `--bot NAME` | 0 answered, 2 timeout, 1 error |
+| `read` | Print new incoming messages since last read | `--limit N`, `--bot NAME`, `--all` | 0 success, 1 error |
+
+## Config Reference
+
+Environment variables take precedence; anything not set in the environment falls back to `~/.config/telegram/config` (created with mode 600):
+
+```
+TELEGRAM_BOT_TOKEN=123:ABC...     # default bot token
+TELEGRAM_CHAT_ID=987654321        # default chat/target
+BOT_ALERTS_TOKEN=456:DEF...       # named bot: --bot alerts (add via: setup --bot alerts)
+TARGET_FAMILY=-100987...          # named target: --to family (any chat/group/channel id)
+TELEGRAM_APPROVER_IDS=123456789   # default group approver user IDs (comma-separated)
+APPROVERS_FAMILY=123456789,987654321 # approvers for --to family (overrides default)
+```
+
+- `TELEGRAM_BOT_TOKEN` / `TELEGRAM_CHAT_ID` — default bot token and default send target.
+- `BOT_<NAME>_TOKEN` — a named bot's token, selected with `--bot <name>` (uppercased key, e.g. `--bot alerts` → `BOT_ALERTS_TOKEN`).
+- `TARGET_<NAME>=<chat_id>` — a named send target, selected with `--to <name>` (uppercased key, e.g. `--to family` → `TARGET_FAMILY`). A numeric `--to` value is used directly as a chat ID without a lookup.
+- `TELEGRAM_APPROVER_IDS` — Telegram user IDs allowed to answer `ask` in a group target.
+- `APPROVERS_<NAME>` — target-specific group approvers (for example, `APPROVERS_FAMILY`); overrides the global allowlist for that named target.
+- `TELEGRAM_CONFIG_DIR` — overrides the config directory (default `~/.config/telegram`).
+
+## Claude Code hooks (settings.json)
+
+Ping your phone when Claude needs input, and when it finishes:
+
+```json
+{
+  "hooks": {
+    "Notification": [{"hooks": [{"type": "command",
+      "command": "bash ~/.claude/skills/telegram/scripts/telegram.sh send \"🔔 Claude needs input in $(basename \\\"$PWD\\\")\""}]}],
+    "Stop": [{"hooks": [{"type": "command",
+      "command": "bash ~/.claude/skills/telegram/scripts/telegram.sh send \"✅ Claude finished in $(basename \\\"$PWD\\\")\" --silent"}]}]
+  }
+}
+```
+
+Approval gate in any script/automation:
+
+```bash
+if [ "$(bash scripts/telegram.sh ask 'Deploy to prod?' --options 'Yes,No')" = "Yes" ]; then
+  ./deploy.sh
+fi
+```
+
+## Security Notes
+
+- The bot token grants full control of the bot — anyone with it can send/receive as your bot. Treat it like a password.
+- Token-bearing API URLs are passed to curl through stdin, not exposed in curl process arguments.
+- `~/.config/telegram/config` is created with mode 600 (owner read/write only).
+- Private-chat answers are accepted only when the sender user ID equals the chat ID. Group
+  targets require an explicit `TELEGRAM_APPROVER_IDS` or target-specific `APPROVERS_<NAME>`
+  allowlist, and `ask` accepts button taps and text only from those user IDs.
+- By default, bots in group chats only see messages that mention them or are replies to them. To read all group messages, either make the bot an admin or disable privacy mode for it via @BotFather (`/setprivacy`).
+
+## License
+
+Apache 2.0

package/bundled-skills/telegram-bot-messaging/SKILL.md

@@ -0,0 +1,101 @@
+---
+name: telegram-bot-messaging
+description: "Send Telegram messages, files, and alerts via bot API; ask questions with inline buttons and wait for the answer. Supports multiple bots, named chat targets, and CI/cron/hook notifications."
+category: productivity
+risk: critical
+source: https://github.com/sanjay3290/ai-skills/tree/main/skills/telegram
+source_repo: sanjay3290/ai-skills
+source_type: community
+date_added: "2026-07-09"
+author: sanjay3290
+tags: [telegram, notifications, bots, approvals]
+tools: [claude, cursor, gemini]
+license: "Apache-2.0"
+license_source: "https://github.com/sanjay3290/ai-skills/blob/main/LICENSE"
+---
+
+# Telegram
+
+## When to Use
+
+- Use when you need to send a Telegram message, file, or alert from a workflow, hook, cron job, or CI pipeline
+- Use when a long-running task should notify you or ask for approval on your phone (inline-button questions that wait for the answer)
+- Use when wiring "notify me when done" or "ask me before proceeding" behavior into automated sessions
+
+Send updates, alerts, and files to Telegram; read replies; run ask-and-wait
+approval flows. Pure bash + curl + jq — no install beyond a bot token.
+
+First run: `bash scripts/telegram.sh setup` (guided BotFather walkthrough).
+
+## Safety Gate
+
+Before setup, sending a message or file, reading replies, or enabling a hook, obtain the
+user's explicit approval for the target chat, bot account, and exact content or file. Never
+send workspace, customer, credential, or secret data automatically. Treat a token as a secret:
+do not echo it, commit it, or place it in shell history.
+
+## Commands
+
+```bash
+bash scripts/telegram.sh send "Deploy finished ✅"                    # basic alert
+bash scripts/telegram.sh send "low priority" --silent                # no notification sound
+bash scripts/telegram.sh send "*bold* alert" --format md             # MarkdownV2 (falls back to plain)
+bash scripts/telegram.sh send "hi" --to alerts --bot work            # named target + named bot
+bash scripts/telegram.sh file report.pdf "Q3 report"                 # document (photos auto-detected)
+bash scripts/telegram.sh read                                        # new incoming messages since last read
+ANSWER=$(bash scripts/telegram.sh ask "Deploy to prod?" --options "Yes,No" --timeout 300)
+# exit 0 = answered (stdout = answer), 2 = timeout
+```
+
+## Config
+
+Env vars win, then `~/.config/telegram/config` (mode 600):
+
+```
+TELEGRAM_BOT_TOKEN=123:ABC...     # default bot
+TELEGRAM_CHAT_ID=987654321        # default target
+BOT_ALERTS_TOKEN=456:DEF...       # --bot alerts   (add via: setup --bot alerts)
+TARGET_FAMILY=-100987...          # --to family    (any chat/group/channel id)
+TELEGRAM_APPROVER_IDS=123456789   # default group approver user IDs (comma-separated)
+APPROVERS_FAMILY=123456789,987654321 # approvers for --to family (overrides default)
+```
+
+Replies and answers are only accepted from configured chat IDs. Private chats preserve the
+direct-chat behavior (the sender user ID must equal the chat ID). Because a group chat ID is
+shared by every member, `ask` fails closed for groups unless `TELEGRAM_APPROVER_IDS` or the
+target-specific `APPROVERS_<NAME>` explicitly lists the Telegram user IDs allowed to answer.
+
+## Claude Code hooks (settings.json)
+
+Ping your phone when Claude needs input, and when it finishes:
+
+```json
+{
+  "hooks": {
+    "Notification": [{"hooks": [{"type": "command",
+      "command": "bash ~/.claude/skills/telegram/scripts/telegram.sh send \"🔔 Claude needs input in $(basename \\\"$PWD\\\")\""}]}],
+    "Stop": [{"hooks": [{"type": "command",
+      "command": "bash ~/.claude/skills/telegram/scripts/telegram.sh send \"✅ Claude finished in $(basename \\\"$PWD\\\")\" --silent"}]}]
+  }
+}
+```
+
+Approval gate in any script/automation:
+
+```bash
+if [ "$(bash scripts/telegram.sh ask 'Deploy to prod?' --options 'Yes,No')" = "Yes" ]; then
+  ./deploy.sh
+fi
+```
+
+## Limitations
+
+- Telegram is a third-party service: message and file contents leave the local machine and may
+  be retained under Telegram's policies.
+- This skill cannot verify that a chat ID belongs to the intended recipient; confirm the target
+  before every new destination or automation.
+- Bot tokens grant control of the bot. Store them only in a protected local secret store or
+  mode-600 configuration file. The script supplies token-bearing API URLs to curl through
+  stdin rather than process arguments; rotate a token if exposure is suspected.
+- Do not use the examples to create unattended notifications or approval flows without the
+  user's explicit, current authorization.