{"id":"2305185c-65dc-4119-8600-6440d73466a5","entityType":"agent","slug":"clawhub-hith3sh-telegram-messaging","name":"Telegram","canonicalUrl":"https://www.xpersona.co/agent/clawhub-hith3sh-telegram-messaging","canonicalPath":"/agent/clawhub-hith3sh-telegram-messaging","generatedAt":"2026-10-09T22:08:16.362Z","source":"CLAWHUB","claimStatus":"UNCLAIMED","verificationTier":"NONE","summary":{"evidence":{"source":"editorial-content","verified":true,"confidence":"high","updatedAt":"2026-10-09T13:41:04.120Z","emptyReason":null},"description":"Send messages, manage chats, handle files, and automate Telegram bot workflows via the Telegram Bot API. Use this skill when users want to send messages, man... Skill: Telegram Owner: hith3sh Summary: Send messages, manage chats, handle files, and automate Telegram bot workflows via the Telegram Bot API. Use this skill when users want to send messages, man... Tags: latest:0.2.2 Version history: v0.2.2 | 2026-06-09T07:19:40.343Z | user Add UTM attribution tags (utm_source=clawhub) to ClawLink branding links so visits from this skill page are tracked as a distinct traffic sour","descriptionLabel":"Technical summary","evidenceSummary":"Capability contract not published. No trust telemetry is available yet. 2.5K downloads reported by the source. Last updated 10/9/2026.","installCommand":"clawhub skill install s173vws87a7ss71xf9rq53k5gd8568kv:telegram-messaging","sourceUrl":"https://clawhub.ai/hith3sh/telegram-messaging","homepage":"https://clawhub.ai/hith3sh/skills/telegram-messaging","primaryLinks":[{"label":"View on ClawHub","url":"https://clawhub.ai/hith3sh/telegram-messaging","kind":"source"},{"label":"Homepage","url":"https://clawhub.ai/hith3sh/skills/telegram-messaging","kind":"homepage"}],"safetyScore":84,"overallRank":62,"popularityScore":68,"trustScore":null,"claimedByName":null,"isOwner":false,"seoDescription":"Send messages, manage chats, handle files, and automate Telegram bot workflows via the Telegram Bot API. Use this skill when users want to send messages, man..."},"coverage":{"evidence":{"source":"public-profile","verified":false,"confidence":"medium","updatedAt":"2026-10-09T13:41:04.120Z","emptyReason":null},"protocols":[{"protocol":"OPENCLEW","label":"OpenClaw","status":"self-declared","notes":"Declared in the public agent profile."}],"capabilities":[],"verifiedCount":0,"selfDeclaredCount":1,"capabilityMatrix":{"rows":[{"key":"OPENCLEW","type":"protocol","support":"unknown","confidenceSource":"profile","notes":"Listed on profile"}],"flattenedTokens":"protocol:OPENCLEW|unknown|profile"}},"adoption":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-09T13:41:04.120Z","emptyReason":null},"stars":null,"forks":null,"downloads":2546,"packageName":null,"latestVersion":"0.2.2","tractionLabel":"2.5K downloads"},"release":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-09T13:41:04.120Z","emptyReason":null},"lastUpdatedAt":"2026-10-09T13:41:04.120Z","lastCrawledAt":"2026-10-09T13:41:04.120Z","lastIndexedAt":null,"nextCrawlAt":"2026-10-10T13:41:04.120Z","lastVerifiedAt":null,"highlights":[{"version":"0.2.2","createdAt":"2026-06-09T07:19:40.343Z","changelog":"Add UTM attribution tags (utm_source=clawhub) to ClawLink branding links so visits from this skill page are tracked as a distinct traffic source.","fileCount":3,"zipByteSize":5989},{"version":"0.2.1","createdAt":"2026-06-09T05:37:55.691Z","changelog":"- Added the Telegram brand logo image at the top of SKILL.md for clearer branding. - Minor documentation updates for style and formatting in SKILL.md. - Removed the redundant skill-card.md file.","fileCount":3,"zipByteSize":5928},{"version":"0.2.0","createdAt":"2026-06-07T13:38:09.883Z","changelog":"Full rewrite to new standard","fileCount":3,"zipByteSize":6039}]},"execution":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No published capability contract is available yet."},"installCommand":"clawhub skill install s173vws87a7ss71xf9rq53k5gd8568kv:telegram-messaging","setupComplexity":"low","setupSteps":["Setup complexity is LOW. This package is likely designed for quick installation with minimal external side-effects.","Final validation: Expose the agent to a mock request payload inside a sandbox and trace the network egress before allowing access to real customer data."],"contract":{"contractStatus":"missing","authModes":[],"requires":[],"forbidden":[],"supportsMcp":false,"supportsA2a":false,"supportsStreaming":false,"inputSchemaRef":null,"outputSchemaRef":null,"dataRegion":null,"contractUpdatedAt":null,"sourceUpdatedAt":null,"freshnessSeconds":null},"invocationGuide":{"preferredApi":{"snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-telegram-messaging/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-telegram-messaging/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-telegram-messaging/trust"},"curlExamples":["curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-telegram-messaging/snapshot\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-telegram-messaging/contract\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-telegram-messaging/trust\""],"jsonRequestTemplate":{"query":"summarize this repo","constraints":{"maxLatencyMs":2000,"protocolPreference":["OPENCLEW"]}},"jsonResponseTemplate":{"ok":true,"result":{"summary":"...","confidence":0.9},"meta":{"source":"CLAWHUB","generatedAt":"2026-10-09T22:08:16.361Z"}},"retryPolicy":{"maxAttempts":3,"backoffMs":[500,1500,3500],"retryableConditions":["HTTP_429","HTTP_503","NETWORK_TIMEOUT"]}},"endpoints":{"dossierUrl":"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-telegram-messaging/dossier","snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-telegram-messaging/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-telegram-messaging/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-telegram-messaging/trust"}},"reliability":{"evidence":{"source":"runtime-metrics","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No trust, reliability, or runtime telemetry is available."},"trust":{"status":"unavailable","handshakeStatus":"UNKNOWN","verificationFreshnessHours":null,"reputationScore":null,"p95LatencyMs":null,"successRate30d":null,"fallbackRate":null,"attempts30d":null,"trustUpdatedAt":null,"trustConfidence":"unknown","sourceUpdatedAt":null,"freshnessSeconds":null},"decisionGuardrails":{"doNotUseIf":["Contract metadata is missing or unavailable for deterministic execution."],"safeUseWhen":[],"riskFlags":["missing_or_unavailable_contract","trust_data_unavailable","schema_references_missing"],"operationalConfidence":"low"},"executionMetrics":{"observedLatencyMsP50":null,"observedLatencyMsP95":null,"estimatedCostUsd":null,"uptime30d":null,"rateLimitRpm":null,"rateLimitBurst":null,"lastVerifiedAt":null,"verificationSource":null},"runtimeMetrics":{"successRate":null,"avgLatencyMs":null,"avgCostUsd":null,"hallucinationRate":null,"retryRate":null,"disputeRate":null,"p50Latency":null,"p95Latency":null,"lastUpdated":null}},"benchmarks":{"evidence":{"source":"no-benchmark-data","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No benchmark suites or observed failure patterns are available."},"suites":[],"failurePatterns":[]},"artifacts":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"high","updatedAt":"2026-10-09T13:41:04.120Z","emptyReason":null},"readme":"Skill: Telegram\n\nOwner: hith3sh\n\nSummary: Send messages, manage chats, handle files, and automate Telegram bot workflows via the Telegram Bot API. Use this skill when users want to send messages, man...\n\nTags: latest:0.2.2\n\nVersion history:\n\nv0.2.2 | 2026-06-09T07:19:40.343Z | user\n\nAdd UTM attribution tags (utm_source=clawhub) to ClawLink branding links so visits from this skill page are tracked as a distinct traffic source.\n\nv0.2.1 | 2026-06-09T05:37:55.691Z | auto\n\n- Added the Telegram brand logo image at the top of SKILL.md for clearer branding.\n- Minor documentation updates for style and formatting in SKILL.md.\n- Removed the redundant skill-card.md file.\n\nv0.2.0 | 2026-06-07T13:38:09.883Z | user\n\nFull rewrite to new standard\n\nArchive index:\n\nArchive v0.2.2: 3 files, 5989 bytes\n\nFiles: skill-card.md (2237b), SKILL.md (14397b), _meta.json (137b)\n\nFile v0.2.2:SKILL.md\n\n---\nname: telegram-messaging\ndescription: Send messages, manage chats, handle files, and automate Telegram bot workflows via the Telegram Bot API. Use this skill when users want to send messages, manage groups, handle media, or automate notifications via Telegram.\n---\n\n# Telegram\n\n\n\nSend messages, manage chats, handle files, and automate Telegram bot workflows via the Telegram Bot API.\n\nThis skill uses [ClawLink](https://claw-link.dev/?utm_source=clawhub&utm_medium=referral&utm_content=telegram-messaging) for hosted connection flows and credentials so you do not need to configure Telegram API access yourself.\n\n### Setup in 3 Steps\n\n| Step 1: Install | Step 2: Pair Account | Step 3: Connect Telegram |\n|:---:|:---:|:---:|\n|  |  | *App-specific connection GIF coming soon* |\n| Run the install command in OpenClaw | Sign in and approve the device | Open the dashboard and connect Telegram |\n\n## How It Works\n\n```\n┌─────────────────┐ ┌──────────────┐ ┌──────────────────┐\n│ OpenClaw │────▶│ ClawLink │────▶│ Telegram Bot │\n│ (User Chat) │ │ (OAuth) │ │ API │\n└─────────────────┘ └──────────────┘ └──────────────────┘\n │ │ │\n │ 1. Install Plugin │ │\n │ 2. Pair Device │ │\n │ 3. Connect Telegram │ │\n │ │ 4. Secure Token │\n │ │ 5. Proxy Requests │\n │ │ │\n ▼ ▼ ▼\n ┌──────────┐ ┌──────────┐ ┌──────────┐\n │ SKILL │ │ Dashboard│ │ Telegram │\n │ File │ │ Auth │ │ Bot │\n └──────────┘ └──────────┘ └──────────┘\n```\n\n## Install\n\nInstall the verified ClawLink plugin from ClawHub. After the user confirms, complete the full setup so ClawLink tools are visible in the next OpenClaw chat.\n\n```bash\nopenclaw plugins install clawhub:clawlink-plugin\nopenclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\nopenclaw gateway restart\n```\n\nThen tell the user: \"OpenClaw has been restarted. Send `/new` as a standalone message to start a fresh chat, then ask for Telegram again.\"\n\n## Quick Start\n\n```bash\n# Get bot info\nclawlink_call_tool --tool \"telegram_get_me\" --params '{}'\n\n# Get chat info\nclawlink_call_tool --tool \"telegram_get_chat\" --params '{\"chat_id\": \"CHAT_ID\"}'\n\n# Send a message\nclawlink_call_tool --tool \"telegram_send_message\" --params '{\"chat_id\": \"CHAT_ID\", \"text\": \"Hello from OpenClaw!\"}'\n```\n\n## Authentication\n\nAll Telegram tool calls are authenticated automatically by ClawLink using the bot token from the user's connected Telegram bot.\n\n**No bot token is required in chat.** ClawLink stores the bot token securely and injects it into every Telegram Bot API request on the user's behalf.\n\n### Getting Connected\n\n1. Install the ClawLink plugin (see Install above).\n2. Pair the plugin with `clawlink_begin_pairing` if it is not configured yet.\n3. Open https://claw-link.dev/dashboard?add=telegram and connect Telegram.\n4. Call `clawlink_list_integrations` to verify the connection is active.\n\n## Connection Management\n\n### List Connections\n\n```bash\nclawlink_list_integrations\n```\n\n**Response:** Returns all connected integrations. Look for `telegram` in the list.\n\n### Verify Connection\n\n```bash\nclawlink_list_tools --integration telegram\n```\n\n**Response:** Returns the live tool catalog for Telegram.\n\n### Reconnect\n\nIf Telegram tools are missing or the connection shows an error:\n\n1. Direct the user to https://claw-link.dev/dashboard?add=telegram\n2. After they confirm, call `clawlink_list_integrations` to verify\n3. Then call `clawlink_list_tools --integration telegram`\n\n## Security & Permissions\n\n- Access is scoped to the Telegram bot token connected during setup.\n- **All write operations (send message, delete message, kick user) require explicit user confirmation.**\n- Messages can only be sent to chats where the bot is a member with posting rights.\n- The bot must have admin rights in groups/channels to perform moderation actions.\n- Rate limits apply (~30 messages/second globally, ~1 message/second per chat).\n\n## Tool Reference\n\n### Bot Info\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `telegram_get_me` | Get basic bot information (username, name, capabilities) | Read |\n| `telegram_get_updates` | Receive incoming updates via long polling | Read |\n\n### Messages\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `telegram_send_message` | Send a text message to a chat | Write |\n| `telegram_send_photo` | Send a photo to a chat | Write |\n| `telegram_send_document` | Send a document/file to a chat | Write |\n| `telegram_send_location` | Send a location point on a map | Write |\n| `telegram_send_poll` | Send a native poll to a chat | Write |\n| `telegram_edit_message` | Edit an existing bot-sent message | Write |\n| `telegram_delete_message` | Delete a bot-sent or service message | Write |\n| `telegram_forward_message` | Forward a message to another chat | Write |\n\n### Chats\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `telegram_get_chat` | Get chat information by ID | Read |\n| `telegram_get_chat_history` | Get messages from a chat | Read |\n| `telegram_get_chat_member` | Get a user's status/role in a chat | Read |\n| `telegram_get_chat_administrators` | List admins in a chat | Read |\n| `telegram_get_chat_members_count` | Get member count for a chat | Read |\n| `telegram_create_chat_invite_link` | Generate a new primary invite link | Write |\n| `telegram_revoke_chat_invite_link` | Revoke an existing invite link | Write |\n\n### Callbacks\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `telegram_answer_callback_query` | Send an answer to a callback query from inline keyboard | Write |\n\n### Bot Commands\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `telegram_set_my_commands` | Set the bot's command list | Write |\n| `telegram_get_my_commands` | Get the bot's current command list | Read |\n\n## Code Examples\n\n### Send a text message\n\n```bash\nclawlink_call_tool --tool \"telegram_send_message\" \\\n --params '{\n \"chat_id\": \"-1001234567890\",\n \"text\": \"Deployment complete! Version 2.1.0 is live on production.\"\n }'\n```\n\n### Send a photo\n\n```bash\nclawlink_call_tool --tool \"telegram_send_photo\" \\\n --params '{\n \"chat_id\": \"-1001234567890\",\n \"photo\": \"https://example.com/chart.png\",\n \"caption\": \"Weekly activity report\"\n }'\n```\n\n### Send a poll\n\n```bash\nclawlink_call_tool --tool \"telegram_send_poll\" \\\n --params '{\n \"chat_id\": \"-1001234567890\",\n \"question\": \"Which feature should we prioritize next?\",\n \"options\": [\"Dark mode\", \"Export to PDF\", \"Team sharing\", \"API access\"]\n }'\n```\n\n### Get chat information\n\n```bash\nclawlink_call_tool --tool \"telegram_get_chat\" \\\n --params '{\n \"chat_id\": \"-1001234567890\"\n }'\n```\n\n### Get chat member info\n\n```bash\nclawlink_call_tool --tool \"telegram_get_chat_member\" \\\n --params '{\n \"chat_id\": \"-1001234567890\",\n \"user_id\": \"123456789\"\n }'\n```\n\n### Forward a message\n\n```bash\nclawlink_call_tool --tool \"telegram_forward_message\" \\\n --params '{\n \"chat_id\": \"-1009876543210\",\n \"from_chat_id\": \"-1001234567890\",\n \"message_id\": 42\n }'\n```\n\n## Discovery Workflow\n\n1. Call `clawlink_list_integrations` to confirm Telegram is connected.\n2. Call `clawlink_list_tools --integration telegram` to see the live catalog.\n3. Treat the returned list as the source of truth. Do not guess or assume what tools exist.\n4. If the user describes a capability but the exact tool is unclear, call `clawlink_search_tools` with a short query and integration `telegram`.\n5. If no Telegram tools appear, direct the user to https://claw-link.dev/dashboard?add=telegram.\n\n## Execution Workflow\n\n```\n┌─────────────────────────────────────────────────────────────┐\n│ READ OPERATIONS (Safe) │\n│ get → list → fetch → describe │\n│ │\n│ Example: Get chat info → Get chat history → Report │\n└─────────────────────────────────────────────────────────────┘\n │\n ▼\n┌─────────────────────────────────────────────────────────────┐\n│ WRITE OPERATIONS (Require Confirmation) │\n│ describe → preview → confirm → call │\n│ │\n│ Example: Preview message → User approves → Send message │\n└─────────────────────────────────────────────────────────────┘\n```\n\n1. For unfamiliar tools, ambiguous requests, or any write action, call `clawlink_describe_tool` first.\n2. Use the returned guidance, schema, `whenToUse`, `askBefore`, `safeDefaults`, `examples`, and `followups` to shape the call.\n3. Prefer read and get operations before writes when that reduces ambiguity.\n4. For writes or anything marked as requiring confirmation, call `clawlink_preview_tool` first.\n5. Execute with `clawlink_call_tool`. Pass confirmation only after the preview matches the user's intent.\n6. If the tool call fails, report the real error. Do not invent results or restate the failure as a missing capability unless the live catalog supports that conclusion.\n\n## Notes\n\n- Chat IDs for groups/channels start with `-100` (e.g., `-1001234567890`). User DMs use the user's numeric ID.\n- Telegram Bot API uses Unix timestamps in UTC for message dates.\n- `telegram_get_updates` and webhooks are mutually exclusive — if a webhook is active, polling returns a 409 Conflict.\n- Rate limits: ~30 messages/second globally, ~1 message/second per chat. On HTTP 429, honor the `retry_after` value.\n- The bot can only delete messages it sent itself or messages in groups where it has admin rights.\n- Photos are re-encoded by Telegram; use `send_document` to preserve original quality.\n- Messages older than 48 hours cannot be deleted in groups.\n\n## Error Handling\n\n| Status / Error | Meaning |\n|----------------|---------|\n| Tool not found | The tool name does not exist in the current catalog. Verify with `clawlink_list_tools --integration telegram`. |\n| Missing connection | Telegram is not connected. Direct the user to https://claw-link.dev/dashboard?add=telegram. |\n| `chat_not_found` | The chat ID does not exist or the bot is not a member. |\n| `bot_not_member` | The bot is not a member of the target chat. |\n| `message_not_found` | The message ID does not exist in the chat. |\n| `user_not_found` | The user ID does not match any chat member. |\n| `message_to_delete_not_found` | Cannot delete — message may be too old (48h+ in groups) or not bot-authored. |\n| `not_enough_rights` | Bot lacks admin rights needed for this action in the group. |\n| `retry_after` | Rate limited — honor the retry delay (seconds). |\n| `invalid_token` | The bot token is invalid. Reconnect Telegram. |\n| Write rejected | User did not confirm a write action. Always confirm before executing writes. |\n\n### Troubleshooting: Tools Not Visible\n\n1. Check that the ClawLink plugin is installed:\n ```bash\n openclaw plugins list\n ```\n2. If the plugin is installed but tools are missing, tell the user to send `/new` as a standalone message to reload the catalog.\n3. If a fresh chat does not help, run:\n ```bash\n openclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\n openclaw gateway restart\n ```\n4. After restart, tell the user to send `/new` again and retry.\n\n### Troubleshooting: Message Send Fails\n\n1. Confirm the bot is a member of the target chat with post rights.\n2. Check the chat ID format — groups use `-100` prefix, users use numeric ID.\n3. Verify the bot has permission to send media if attaching photos/documents.\n4. If `chat_not_found` appears, the bot may have been removed from the group.\n\n### Troubleshooting: Delete Message Fails\n\n1. The bot can only delete its own messages or messages in groups where it is an admin.\n2. Messages older than 48 hours in groups cannot be deleted via the Bot API.\n3. Service messages (user join/leave) cannot be deleted.\n\n## Resources\n\n- [Telegram Bot API Documentation](https://core.telegram.org/bots/api)\n- [Telegram Bot Features](https://core.telegram.org/bots/features)\n- [BotFather](https://t.me/botfather) — manage bot settings and commands\n- ClawLink: https://claw-link.dev/?utm_source=clawhub&utm_medium=referral&utm_content=telegram-messaging\n- ClawLink Docs: https://docs.claw-link.dev/openclaw\n- ClawLink Verification: https://claw-link.dev/verify\n\n---\n\n**Powered by [ClawLink](https://claw-link.dev/?utm_source=clawhub&utm_medium=referral&utm_content=telegram-messaging)** — an integration hub for OpenClaw\n\n\n\nFile v0.2.2:_meta.json\n\n{\n \"ownerId\": \"kn713pxvayh8fjhb503zjb8yxh815j54\",\n \"slug\": \"telegram-messaging\",\n \"version\": \"0.2.2\",\n \"publishedAt\": 1780989580343\n}\n\nFile v0.2.2:skill-card.md\n\n## Description:\n\nSend messages, manage chats, handle files, and automate Telegram bot workflows via the Telegram Bot API.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[hith3sh](https://clawhub.ai/user/hith3sh)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nExternal users, developers, and operations teams use this skill to send Telegram bot messages, inspect chats, manage bot commands, handle media, and automate notifications through ClawLink-hosted Telegram Bot API tooling.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: The setup installs and enables an external ClawLink plugin and hosted service that stores the connected Telegram bot token and proxies Telegram requests.\n\nMitigation: Install only when the user trusts ClawLink, understands the hosted credential flow, and has reviewed the enabled plugin access.\n\nRisk: Telegram write actions can send, delete, forward, moderate, or create invite-link changes in chats where the bot has permission.\n\nMitigation: Keep explicit user confirmation in place for write operations and preview the intended action before calling the tool.\n\n## Reference(s):\n\n- [Telegram Bot API Documentation](https://core.telegram.org/bots/api)\n- [Telegram Bot Features](https://core.telegram.org/bots/features)\n- [BotFather](https://t.me/botfather)\n- [ClawLink OpenClaw Docs](https://docs.claw-link.dev/openclaw)\n- [ClawHub Skill Page](https://clawhub.ai/hith3sh/skills/telegram-messaging)\n\n## Skill Output:\n\n**Output Type(s):** [guidance, shell commands, configuration, API calls, markdown]\n\n**Output Format:** [Markdown guidance with inline shell commands and JSON parameters for ClawLink tool calls]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Tool execution depends on the user connecting a Telegram bot through ClawLink; write operations require explicit user confirmation.]\n\n## Skill Version(s):\n\n0.2.2 (source: server release metadata)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nArchive v0.2.1: 3 files, 5928 bytes\n\nFiles: skill-card.md (2350b), SKILL.md (14184b), _meta.json (137b)\n\nFile v0.2.1:SKILL.md\n\n---\nname: telegram-messaging\ndescription: Send messages, manage chats, handle files, and automate Telegram bot workflows via the Telegram Bot API. Use this skill when users want to send messages, manage groups, handle media, or automate notifications via Telegram.\n---\n\n# Telegram\n\n\n\nSend messages, manage chats, handle files, and automate Telegram bot workflows via the Telegram Bot API.\n\nThis skill uses [ClawLink](https://claw-link.dev) for hosted connection flows and credentials so you do not need to configure Telegram API access yourself.\n\n### Setup in 3 Steps\n\n| Step 1: Install | Step 2: Pair Account | Step 3: Connect Telegram |\n|:---:|:---:|:---:|\n|  |  | *App-specific connection GIF coming soon* |\n| Run the install command in OpenClaw | Sign in and approve the device | Open the dashboard and connect Telegram |\n\n## How It Works\n\n```\n┌─────────────────┐ ┌──────────────┐ ┌──────────────────┐\n│ OpenClaw │────▶│ ClawLink │────▶│ Telegram Bot │\n│ (User Chat) │ │ (OAuth) │ │ API │\n└─────────────────┘ └──────────────┘ └──────────────────┘\n │ │ │\n │ 1. Install Plugin │ │\n │ 2. Pair Device │ │\n │ 3. Connect Telegram │ │\n │ │ 4. Secure Token │\n │ │ 5. Proxy Requests │\n │ │ │\n ▼ ▼ ▼\n ┌──────────┐ ┌──────────┐ ┌──────────┐\n │ SKILL │ │ Dashboard│ │ Telegram │\n │ File │ │ Auth │ │ Bot │\n └──────────┘ └──────────┘ └──────────┘\n```\n\n## Install\n\nInstall the verified ClawLink plugin from ClawHub. After the user confirms, complete the full setup so ClawLink tools are visible in the next OpenClaw chat.\n\n```bash\nopenclaw plugins install clawhub:clawlink-plugin\nopenclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\nopenclaw gateway restart\n```\n\nThen tell the user: \"OpenClaw has been restarted. Send `/new` as a standalone message to start a fresh chat, then ask for Telegram again.\"\n\n## Quick Start\n\n```bash\n# Get bot info\nclawlink_call_tool --tool \"telegram_get_me\" --params '{}'\n\n# Get chat info\nclawlink_call_tool --tool \"telegram_get_chat\" --params '{\"chat_id\": \"CHAT_ID\"}'\n\n# Send a message\nclawlink_call_tool --tool \"telegram_send_message\" --params '{\"chat_id\": \"CHAT_ID\", \"text\": \"Hello from OpenClaw!\"}'\n```\n\n## Authentication\n\nAll Telegram tool calls are authenticated automatically by ClawLink using the bot token from the user's connected Telegram bot.\n\n**No bot token is required in chat.** ClawLink stores the bot token securely and injects it into every Telegram Bot API request on the user's behalf.\n\n### Getting Connected\n\n1. Install the ClawLink plugin (see Install above).\n2. Pair the plugin with `clawlink_begin_pairing` if it is not configured yet.\n3. Open https://claw-link.dev/dashboard?add=telegram and connect Telegram.\n4. Call `clawlink_list_integrations` to verify the connection is active.\n\n## Connection Management\n\n### List Connections\n\n```bash\nclawlink_list_integrations\n```\n\n**Response:** Returns all connected integrations. Look for `telegram` in the list.\n\n### Verify Connection\n\n```bash\nclawlink_list_tools --integration telegram\n```\n\n**Response:** Returns the live tool catalog for Telegram.\n\n### Reconnect\n\nIf Telegram tools are missing or the connection shows an error:\n\n1. Direct the user to https://claw-link.dev/dashboard?add=telegram\n2. After they confirm, call `clawlink_list_integrations` to verify\n3. Then call `clawlink_list_tools --integration telegram`\n\n## Security & Permissions\n\n- Access is scoped to the Telegram bot token connected during setup.\n- **All write operations (send message, delete message, kick user) require explicit user confirmation.**\n- Messages can only be sent to chats where the bot is a member with posting rights.\n- The bot must have admin rights in groups/channels to perform moderation actions.\n- Rate limits apply (~30 messages/second globally, ~1 message/second per chat).\n\n## Tool Reference\n\n### Bot Info\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `telegram_get_me` | Get basic bot information (username, name, capabilities) | Read |\n| `telegram_get_updates` | Receive incoming updates via long polling | Read |\n\n### Messages\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `telegram_send_message` | Send a text message to a chat | Write |\n| `telegram_send_photo` | Send a photo to a chat | Write |\n| `telegram_send_document` | Send a document/file to a chat | Write |\n| `telegram_send_location` | Send a location point on a map | Write |\n| `telegram_send_poll` | Send a native poll to a chat | Write |\n| `telegram_edit_message` | Edit an existing bot-sent message | Write |\n| `telegram_delete_message` | Delete a bot-sent or service message | Write |\n| `telegram_forward_message` | Forward a message to another chat | Write |\n\n### Chats\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `telegram_get_chat` | Get chat information by ID | Read |\n| `telegram_get_chat_history` | Get messages from a chat | Read |\n| `telegram_get_chat_member` | Get a user's status/role in a chat | Read |\n| `telegram_get_chat_administrators` | List admins in a chat | Read |\n| `telegram_get_chat_members_count` | Get member count for a chat | Read |\n| `telegram_create_chat_invite_link` | Generate a new primary invite link | Write |\n| `telegram_revoke_chat_invite_link` | Revoke an existing invite link | Write |\n\n### Callbacks\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `telegram_answer_callback_query` | Send an answer to a callback query from inline keyboard | Write |\n\n### Bot Commands\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `telegram_set_my_commands` | Set the bot's command list | Write |\n| `telegram_get_my_commands` | Get the bot's current command list | Read |\n\n## Code Examples\n\n### Send a text message\n\n```bash\nclawlink_call_tool --tool \"telegram_send_message\" \\\n --params '{\n \"chat_id\": \"-1001234567890\",\n \"text\": \"Deployment complete! Version 2.1.0 is live on production.\"\n }'\n```\n\n### Send a photo\n\n```bash\nclawlink_call_tool --tool \"telegram_send_photo\" \\\n --params '{\n \"chat_id\": \"-1001234567890\",\n \"photo\": \"https://example.com/chart.png\",\n \"caption\": \"Weekly activity report\"\n }'\n```\n\n### Send a poll\n\n```bash\nclawlink_call_tool --tool \"telegram_send_poll\" \\\n --params '{\n \"chat_id\": \"-1001234567890\",\n \"question\": \"Which feature should we prioritize next?\",\n \"options\": [\"Dark mode\", \"Export to PDF\", \"Team sharing\", \"API access\"]\n }'\n```\n\n### Get chat information\n\n```bash\nclawlink_call_tool --tool \"telegram_get_chat\" \\\n --params '{\n \"chat_id\": \"-1001234567890\"\n }'\n```\n\n### Get chat member info\n\n```bash\nclawlink_call_tool --tool \"telegram_get_chat_member\" \\\n --params '{\n \"chat_id\": \"-1001234567890\",\n \"user_id\": \"123456789\"\n }'\n```\n\n### Forward a message\n\n```bash\nclawlink_call_tool --tool \"telegram_forward_message\" \\\n --params '{\n \"chat_id\": \"-1009876543210\",\n \"from_chat_id\": \"-1001234567890\",\n \"message_id\": 42\n }'\n```\n\n## Discovery Workflow\n\n1. Call `clawlink_list_integrations` to confirm Telegram is connected.\n2. Call `clawlink_list_tools --integration telegram` to see the live catalog.\n3. Treat the returned list as the source of truth. Do not guess or assume what tools exist.\n4. If the user describes a capability but the exact tool is unclear, call `clawlink_search_tools` with a short query and integration `telegram`.\n5. If no Telegram tools appear, direct the user to https://claw-link.dev/dashboard?add=telegram.\n\n## Execution Workflow\n\n```\n┌─────────────────────────────────────────────────────────────┐\n│ READ OPERATIONS (Safe) │\n│ get → list → fetch → describe │\n│ │\n│ Example: Get chat info → Get chat history → Report │\n└─────────────────────────────────────────────────────────────┘\n │\n ▼\n┌─────────────────────────────────────────────────────────────┐\n│ WRITE OPERATIONS (Require Confirmation) │\n│ describe → preview → confirm → call │\n│ │\n│ Example: Preview message → User approves → Send message │\n└─────────────────────────────────────────────────────────────┘\n```\n\n1. For unfamiliar tools, ambiguous requests, or any write action, call `clawlink_describe_tool` first.\n2. Use the returned guidance, schema, `whenToUse`, `askBefore`, `safeDefaults`, `examples`, and `followups` to shape the call.\n3. Prefer read and get operations before writes when that reduces ambiguity.\n4. For writes or anything marked as requiring confirmation, call `clawlink_preview_tool` first.\n5. Execute with `clawlink_call_tool`. Pass confirmation only after the preview matches the user's intent.\n6. If the tool call fails, report the real error. Do not invent results or restate the failure as a missing capability unless the live catalog supports that conclusion.\n\n## Notes\n\n- Chat IDs for groups/channels start with `-100` (e.g., `-1001234567890`). User DMs use the user's numeric ID.\n- Telegram Bot API uses Unix timestamps in UTC for message dates.\n- `telegram_get_updates` and webhooks are mutually exclusive — if a webhook is active, polling returns a 409 Conflict.\n- Rate limits: ~30 messages/second globally, ~1 message/second per chat. On HTTP 429, honor the `retry_after` value.\n- The bot can only delete messages it sent itself or messages in groups where it has admin rights.\n- Photos are re-encoded by Telegram; use `send_document` to preserve original quality.\n- Messages older than 48 hours cannot be deleted in groups.\n\n## Error Handling\n\n| Status / Error | Meaning |\n|----------------|---------|\n| Tool not found | The tool name does not exist in the current catalog. Verify with `clawlink_list_tools --integration telegram`. |\n| Missing connection | Telegram is not connected. Direct the user to https://claw-link.dev/dashboard?add=telegram. |\n| `chat_not_found` | The chat ID does not exist or the bot is not a member. |\n| `bot_not_member` | The bot is not a member of the target chat. |\n| `message_not_found` | The message ID does not exist in the chat. |\n| `user_not_found` | The user ID does not match any chat member. |\n| `message_to_delete_not_found` | Cannot delete — message may be too old (48h+ in groups) or not bot-authored. |\n| `not_enough_rights` | Bot lacks admin rights needed for this action in the group. |\n| `retry_after` | Rate limited — honor the retry delay (seconds). |\n| `invalid_token` | The bot token is invalid. Reconnect Telegram. |\n| Write rejected | User did not confirm a write action. Always confirm before executing writes. |\n\n### Troubleshooting: Tools Not Visible\n\n1. Check that the ClawLink plugin is installed:\n ```bash\n openclaw plugins list\n ```\n2. If the plugin is installed but tools are missing, tell the user to send `/new` as a standalone message to reload the catalog.\n3. If a fresh chat does not help, run:\n ```bash\n openclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\n openclaw gateway restart\n ```\n4. After restart, tell the user to send `/new` again and retry.\n\n### Troubleshooting: Message Send Fails\n\n1. Confirm the bot is a member of the target chat with post rights.\n2. Check the chat ID format — groups use `-100` prefix, users use numeric ID.\n3. Verify the bot has permission to send media if attaching photos/documents.\n4. If `chat_not_found` appears, the bot may have been removed from the group.\n\n### Troubleshooting: Delete Message Fails\n\n1. The bot can only delete its own messages or messages in groups where it is an admin.\n2. Messages older than 48 hours in groups cannot be deleted via the Bot API.\n3. Service messages (user join/leave) cannot be deleted.\n\n## Resources\n\n- [Telegram Bot API Documentation](https://core.telegram.org/bots/api)\n- [Telegram Bot Features](https://core.telegram.org/bots/features)\n- [BotFather](https://t.me/botfather) — manage bot settings and commands\n- ClawLink: https://claw-link.dev\n- ClawLink Docs: https://docs.claw-link.dev/openclaw\n- ClawLink Verification: https://claw-link.dev/verify\n\n---\n\n**Powered by [ClawLink](https://claw-link.dev)** — an integration hub for OpenClaw\n\n\n\nFile v0.2.1:_meta.json\n\n{\n \"ownerId\": \"kn713pxvayh8fjhb503zjb8yxh815j54\",\n \"slug\": \"telegram-messaging\",\n \"version\": \"0.2.1\",\n \"publishedAt\": 1780983475691\n}\n\nFile v0.2.1:skill-card.md\n\n## Description:
\nSend messages, manage chats, handle files, and automate Telegram bot workflows via the Telegram Bot API.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[hith3sh](https://clawhub.ai/user/hith3sh)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nExternal users, developers, and operators use this skill to connect a Telegram bot through ClawLink, inspect bot or chat state, send messages and media, manage bot commands, and perform group or channel moderation workflows through the Telegram Bot API.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: ClawLink stores and uses the connected Telegram bot token for authenticated Telegram Bot API calls.
\nMitigation: Install only when the user trusts ClawLink with the bot token and confirm the Telegram connection state before use.
\nRisk: Telegram write actions can post to public groups or channels, delete messages, change invite links, or update bot commands.
\nMitigation: Preview and explicitly confirm write operations before execution, especially actions affecting public chats, moderation, invite links, or command configuration.
\n\n\n## Reference(s):
\n- [Telegram Bot API Documentation](https://core.telegram.org/bots/api)
\n- [Telegram Bot Features](https://core.telegram.org/bots/features)
\n- [BotFather](https://t.me/botfather)
\n- [ClawLink](https://claw-link.dev)
\n- [ClawLink Docs](https://docs.claw-link.dev/openclaw)
\n- [ClawHub Skill Page](https://clawhub.ai/hith3sh/telegram-messaging)
\n\n\n## Skill Output:
\n**Output Type(s):** [text, markdown, shell commands, configuration, guidance]
\n**Output Format:** [Markdown with inline bash commands and JSON tool parameters]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [May include Telegram Bot API tool names, confirmation guidance for write actions, and troubleshooting steps.]
\n\n## Skill Version(s):
\n0.2.1 (source: server release evidence)
\n\n## Ethical Considerations:
\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.
\n\nArchive v0.2.0: 3 files, 6039 bytes\n\nFiles: skill-card.md (2629b), SKILL.md (14071b), _meta.json (137b)\n\nFile v0.2.0:SKILL.md\n\n---\nname: telegram-messaging\ndescription: Send messages, manage chats, handle files, and automate Telegram bot workflows via the Telegram Bot API. Use this skill when users want to send messages, manage groups, handle media, or automate notifications via Telegram.\n---\n\n# Telegram\n\nSend messages, manage chats, handle files, and automate Telegram bot workflows via the Telegram Bot API.\n\nThis skill uses [ClawLink](https://claw-link.dev) for hosted connection flows and credentials so you do not need to configure Telegram API access yourself.\n\n### Setup in 3 Steps\n\n| Step 1: Install | Step 2: Pair Account | Step 3: Connect Telegram |\n|:---:|:---:|:---:|\n|  |  | *App-specific connection GIF coming soon* |\n| Run the install command in OpenClaw | Sign in and approve the device | Open the dashboard and connect Telegram |\n\n## How It Works\n\n```\n┌─────────────────┐ ┌──────────────┐ ┌──────────────────┐\n│ OpenClaw │────▶│ ClawLink │────▶│ Telegram Bot │\n│ (User Chat) │ │ (OAuth) │ │ API │\n└─────────────────┘ └──────────────┘ └──────────────────┘\n │ │ │\n │ 1. Install Plugin │ │\n │ 2. Pair Device │ │\n │ 3. Connect Telegram │ │\n │ │ 4. Secure Token │\n │ │ 5. Proxy Requests │\n │ │ │\n ▼ ▼ ▼\n ┌──────────┐ ┌──────────┐ ┌──────────┐\n │ SKILL │ │ Dashboard│ │ Telegram │\n │ File │ │ Auth │ │ Bot │\n └──────────┘ └──────────┘ └──────────┘\n```\n\n## Install\n\nInstall the verified ClawLink plugin from ClawHub. After the user confirms, complete the full setup so ClawLink tools are visible in the next OpenClaw chat.\n\n```bash\nopenclaw plugins install clawhub:clawlink-plugin\nopenclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\nopenclaw gateway restart\n```\n\nThen tell the user: \"OpenClaw has been restarted. Send `/new` as a standalone message to start a fresh chat, then ask for Telegram again.\"\n\n## Quick Start\n\n```bash\n# Get bot info\nclawlink_call_tool --tool \"telegram_get_me\" --params '{}'\n\n# Get chat info\nclawlink_call_tool --tool \"telegram_get_chat\" --params '{\"chat_id\": \"CHAT_ID\"}'\n\n# Send a message\nclawlink_call_tool --tool \"telegram_send_message\" --params '{\"chat_id\": \"CHAT_ID\", \"text\": \"Hello from OpenClaw!\"}'\n```\n\n## Authentication\n\nAll Telegram tool calls are authenticated automatically by ClawLink using the bot token from the user's connected Telegram bot.\n\n**No bot token is required in chat.** ClawLink stores the bot token securely and injects it into every Telegram Bot API request on the user's behalf.\n\n### Getting Connected\n\n1. Install the ClawLink plugin (see Install above).\n2. Pair the plugin with `clawlink_begin_pairing` if it is not configured yet.\n3. Open https://claw-link.dev/dashboard?add=telegram and connect Telegram.\n4. Call `clawlink_list_integrations` to verify the connection is active.\n\n## Connection Management\n\n### List Connections\n\n```bash\nclawlink_list_integrations\n```\n\n**Response:** Returns all connected integrations. Look for `telegram` in the list.\n\n### Verify Connection\n\n```bash\nclawlink_list_tools --integration telegram\n```\n\n**Response:** Returns the live tool catalog for Telegram.\n\n### Reconnect\n\nIf Telegram tools are missing or the connection shows an error:\n\n1. Direct the user to https://claw-link.dev/dashboard?add=telegram\n2. After they confirm, call `clawlink_list_integrations` to verify\n3. Then call `clawlink_list_tools --integration telegram`\n\n## Security & Permissions\n\n- Access is scoped to the Telegram bot token connected during setup.\n- **All write operations (send message, delete message, kick user) require explicit user confirmation.**\n- Messages can only be sent to chats where the bot is a member with posting rights.\n- The bot must have admin rights in groups/channels to perform moderation actions.\n- Rate limits apply (~30 messages/second globally, ~1 message/second per chat).\n\n## Tool Reference\n\n### Bot Info\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `telegram_get_me` | Get basic bot information (username, name, capabilities) | Read |\n| `telegram_get_updates` | Receive incoming updates via long polling | Read |\n\n### Messages\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `telegram_send_message` | Send a text message to a chat | Write |\n| `telegram_send_photo` | Send a photo to a chat | Write |\n| `telegram_send_document` | Send a document/file to a chat | Write |\n| `telegram_send_location` | Send a location point on a map | Write |\n| `telegram_send_poll` | Send a native poll to a chat | Write |\n| `telegram_edit_message` | Edit an existing bot-sent message | Write |\n| `telegram_delete_message` | Delete a bot-sent or service message | Write |\n| `telegram_forward_message` | Forward a message to another chat | Write |\n\n### Chats\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `telegram_get_chat` | Get chat information by ID | Read |\n| `telegram_get_chat_history` | Get messages from a chat | Read |\n| `telegram_get_chat_member` | Get a user's status/role in a chat | Read |\n| `telegram_get_chat_administrators` | List admins in a chat | Read |\n| `telegram_get_chat_members_count` | Get member count for a chat | Read |\n| `telegram_create_chat_invite_link` | Generate a new primary invite link | Write |\n| `telegram_revoke_chat_invite_link` | Revoke an existing invite link | Write |\n\n### Callbacks\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `telegram_answer_callback_query` | Send an answer to a callback query from inline keyboard | Write |\n\n### Bot Commands\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `telegram_set_my_commands` | Set the bot's command list | Write |\n| `telegram_get_my_commands` | Get the bot's current command list | Read |\n\n## Code Examples\n\n### Send a text message\n\n```bash\nclawlink_call_tool --tool \"telegram_send_message\" \\\n --params '{\n \"chat_id\": \"-1001234567890\",\n \"text\": \"Deployment complete! Version 2.1.0 is live on production.\"\n }'\n```\n\n### Send a photo\n\n```bash\nclawlink_call_tool --tool \"telegram_send_photo\" \\\n --params '{\n \"chat_id\": \"-1001234567890\",\n \"photo\": \"https://example.com/chart.png\",\n \"caption\": \"Weekly activity report\"\n }'\n```\n\n### Send a poll\n\n```bash\nclawlink_call_tool --tool \"telegram_send_poll\" \\\n --params '{\n \"chat_id\": \"-1001234567890\",\n \"question\": \"Which feature should we prioritize next?\",\n \"options\": [\"Dark mode\", \"Export to PDF\", \"Team sharing\", \"API access\"]\n }'\n```\n\n### Get chat information\n\n```bash\nclawlink_call_tool --tool \"telegram_get_chat\" \\\n --params '{\n \"chat_id\": \"-1001234567890\"\n }'\n```\n\n### Get chat member info\n\n```bash\nclawlink_call_tool --tool \"telegram_get_chat_member\" \\\n --params '{\n \"chat_id\": \"-1001234567890\",\n \"user_id\": \"123456789\"\n }'\n```\n\n### Forward a message\n\n```bash\nclawlink_call_tool --tool \"telegram_forward_message\" \\\n --params '{\n \"chat_id\": \"-1009876543210\",\n \"from_chat_id\": \"-1001234567890\",\n \"message_id\": 42\n }'\n```\n\n## Discovery Workflow\n\n1. Call `clawlink_list_integrations` to confirm Telegram is connected.\n2. Call `clawlink_list_tools --integration telegram` to see the live catalog.\n3. Treat the returned list as the source of truth. Do not guess or assume what tools exist.\n4. If the user describes a capability but the exact tool is unclear, call `clawlink_search_tools` with a short query and integration `telegram`.\n5. If no Telegram tools appear, direct the user to https://claw-link.dev/dashboard?add=telegram.\n\n## Execution Workflow\n\n```\n┌─────────────────────────────────────────────────────────────┐\n│ READ OPERATIONS (Safe) │\n│ get → list → fetch → describe │\n│ │\n│ Example: Get chat info → Get chat history → Report │\n└─────────────────────────────────────────────────────────────┘\n │\n ▼\n┌─────────────────────────────────────────────────────────────┐\n│ WRITE OPERATIONS (Require Confirmation) │\n│ describe → preview → confirm → call │\n│ │\n│ Example: Preview message → User approves → Send message │\n└─────────────────────────────────────────────────────────────┘\n```\n\n1. For unfamiliar tools, ambiguous requests, or any write action, call `clawlink_describe_tool` first.\n2. Use the returned guidance, schema, `whenToUse`, `askBefore`, `safeDefaults`, `examples`, and `followups` to shape the call.\n3. Prefer read and get operations before writes when that reduces ambiguity.\n4. For writes or anything marked as requiring confirmation, call `clawlink_preview_tool` first.\n5. Execute with `clawlink_call_tool`. Pass confirmation only after the preview matches the user's intent.\n6. If the tool call fails, report the real error. Do not invent results or restate the failure as a missing capability unless the live catalog supports that conclusion.\n\n## Notes\n\n- Chat IDs for groups/channels start with `-100` (e.g., `-1001234567890`). User DMs use the user's numeric ID.\n- Telegram Bot API uses Unix timestamps in UTC for message dates.\n- `telegram_get_updates` and webhooks are mutually exclusive — if a webhook is active, polling returns a 409 Conflict.\n- Rate limits: ~30 messages/second globally, ~1 message/second per chat. On HTTP 429, honor the `retry_after` value.\n- The bot can only delete messages it sent itself or messages in groups where it has admin rights.\n- Photos are re-encoded by Telegram; use `send_document` to preserve original quality.\n- Messages older than 48 hours cannot be deleted in groups.\n\n## Error Handling\n\n| Status / Error | Meaning |\n|----------------|---------|\n| Tool not found | The tool name does not exist in the current catalog. Verify with `clawlink_list_tools --integration telegram`. |\n| Missing connection | Telegram is not connected. Direct the user to https://claw-link.dev/dashboard?add=telegram. |\n| `chat_not_found` | The chat ID does not exist or the bot is not a member. |\n| `bot_not_member` | The bot is not a member of the target chat. |\n| `message_not_found` | The message ID does not exist in the chat. |\n| `user_not_found` | The user ID does not match any chat member. |\n| `message_to_delete_not_found` | Cannot delete — message may be too old (48h+ in groups) or not bot-authored. |\n| `not_enough_rights` | Bot lacks admin rights needed for this action in the group. |\n| `retry_after` | Rate limited — honor the retry delay (seconds). |\n| `invalid_token` | The bot token is invalid. Reconnect Telegram. |\n| Write rejected | User did not confirm a write action. Always confirm before executing writes. |\n\n### Troubleshooting: Tools Not Visible\n\n1. Check that the ClawLink plugin is installed:\n ```bash\n openclaw plugins list\n ```\n2. If the plugin is installed but tools are missing, tell the user to send `/new` as a standalone message to reload the catalog.\n3. If a fresh chat does not help, run:\n ```bash\n openclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\n openclaw gateway restart\n ```\n4. After restart, tell the user to send `/new` again and retry.\n\n### Troubleshooting: Message Send Fails\n\n1. Confirm the bot is a member of the target chat with post rights.\n2. Check the chat ID format — groups use `-100` prefix, users use numeric ID.\n3. Verify the bot has permission to send media if attaching photos/documents.\n4. If `chat_not_found` appears, the bot may have been removed from the group.\n\n### Troubleshooting: Delete Message Fails\n\n1. The bot can only delete its own messages or messages in groups where it is an admin.\n2. Messages older than 48 hours in groups cannot be deleted via the Bot API.\n3. Service messages (user join/leave) cannot be deleted.\n\n## Resources\n\n- [Telegram Bot API Documentation](https://core.telegram.org/bots/api)\n- [Telegram Bot Features](https://core.telegram.org/bots/features)\n- [BotFather](https://t.me/botfather) — manage bot settings and commands\n- ClawLink: https://claw-link.dev\n- ClawLink Docs: https://docs.claw-link.dev/openclaw\n- ClawLink Verification: https://claw-link.dev/verify\n\n---\n\n**Powered by [ClawLink](https://claw-link.dev)** — an integration hub for OpenClaw\n\n\n\nFile v0.2.0:_meta.json\n\n{\n \"ownerId\": \"kn713pxvayh8fjhb503zjb8yxh815j54\",\n \"slug\": \"telegram-messaging\",\n \"version\": \"0.2.0\",\n \"publishedAt\": 1780839489883\n}\n\nFile v0.2.0:skill-card.md\n\n## Description:
\nSend messages, manage chats, handle files, and automate Telegram bot workflows via the Telegram Bot API.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[hith3sh](https://clawhub.ai/user/hith3sh)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nDevelopers and operators use this skill to connect a Telegram bot through ClawLink, inspect bot and chat state, and automate messages, media, polls, commands, invite links, and moderation workflows.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: The skill relies on ClawLink handling the connected Telegram bot token and using it to act in chats where the bot has access.
\nMitigation: Install only when the user trusts ClawLink with the bot token and confirm that the bot has only the chat access and permissions needed for the task.
\nRisk: Telegram write operations can send messages, delete content, change bot commands, or create and revoke invite links.
\nMitigation: Preview and explicitly confirm write actions before execution, and review target chat IDs, message content, and moderation effects carefully.
\nRisk: Bot actions may fail or behave differently when Telegram permissions, membership, rate limits, or message-age limits apply.
\nMitigation: Verify the live Telegram tool catalog and bot permissions before acting, honor rate-limit retry guidance, and report real API errors without inventing results.
\n\n\n## Reference(s):
\n- [ClawHub Skill Page](https://clawhub.ai/hith3sh/telegram-messaging)
\n- [Telegram Bot API Documentation](https://core.telegram.org/bots/api)
\n- [Telegram Bot Features](https://core.telegram.org/bots/features)
\n- [BotFather](https://t.me/botfather)
\n- [ClawLink](https://claw-link.dev)
\n- [ClawLink OpenClaw Docs](https://docs.claw-link.dev/openclaw)
\n\n\n## Skill Output:
\n**Output Type(s):** [text, markdown, shell commands, configuration, guidance]
\n**Output Format:** [Markdown with inline shell commands and JSON parameters]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [Guides agents to call ClawLink tools, preview write actions, and report Telegram API errors.]
\n\n## Skill Version(s):
\n0.2.0 (source: server release metadata)
\n\n## Ethical Considerations:
\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.
","readmeExcerpt":"Skill: Telegram Owner: hith3sh Summary: Send messages, manage chats, handle files, and automate Telegram bot workflows via the Telegram Bot API. Use this skill when users want to send messages, man... Tags: latest:0.2.2 Version history: v0.2.2 | 2026-06-09T07:19:40.343Z | user Add UTM attribution tags (utm_source=clawhub) to ClawLink branding links so visits from this skill page are tracked as a distinct traffic sour","codeSnippets":[],"executableExamples":[{"language":"text","snippet":"┌─────────────────┐ ┌──────────────┐ ┌──────────────────┐\n│ OpenClaw │────▶│ ClawLink │────▶│ Telegram Bot │\n│ (User Chat) │ │ (OAuth) │ │ API │\n└─────────────────┘ └──────────────┘ └──────────────────┘\n │ │ │\n │ 1. Install Plugin │ │\n │ 2. Pair Device │ │\n │ 3. Connect Telegram │ │\n │ │ 4. Secure Token │\n │ │ 5. Proxy Requests │\n │ │ │\n ▼ ▼ ▼\n ┌──────────┐ ┌──────────┐ ┌──────────┐\n │ SKILL │ │ Dashboard│ │ Telegram │\n │ File │ │ Auth │ │ Bot │\n └──────────┘ └──────────┘ └──────────┘"},{"language":"bash","snippet":"openclaw plugins install clawhub:clawlink-plugin\nopenclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\nopenclaw gateway restart"},{"language":"bash","snippet":"# Get bot info\nclawlink_call_tool --tool \"telegram_get_me\" --params '{}'\n\n# Get chat info\nclawlink_call_tool --tool \"telegram_get_chat\" --params '{\"chat_id\": \"CHAT_ID\"}'\n\n# Send a message\nclawlink_call_tool --tool \"telegram_send_message\" --params '{\"chat_id\": \"CHAT_ID\", \"text\": \"Hello from OpenClaw!\"}'"},{"language":"bash","snippet":"clawlink_list_integrations"},{"language":"bash","snippet":"clawlink_list_tools --integration telegram"},{"language":"bash","snippet":"clawlink_call_tool --tool \"telegram_send_message\" \\\n --params '{\n \"chat_id\": \"-1001234567890\",\n \"text\": \"Deployment complete! Version 2.1.0 is live on production.\"\n }'"}],"parameters":null,"dependencies":[],"permissions":[],"extractedFiles":[{"path":"SKILL.md","content":"---\nname: telegram-messaging\ndescription: Send messages, manage chats, handle files, and automate Telegram bot workflows via the Telegram Bot API. Use this skill when users want to send messages, manage groups, handle media, or automate notifications via Telegram.\n---\n\n# Telegram\n\n\n\nSend messages, manage chats, handle files, and automate Telegram bot workflows via the Telegram Bot API.\n\nThis skill uses [ClawLink](https://claw-link.dev/?utm_source=clawhub&utm_medium=referral&utm_content=telegram-messaging) for hosted connection flows and credentials so you do not need to configure Telegram API access yourself.\n\n### Setup in 3 Steps\n\n| Step 1: Install | Step 2: Pair Account | Step 3: Connect Telegram |\n|:---:|:---:|:---:|\n|  |  | *App-specific connection GIF coming soon* |\n| Run the install command in OpenClaw | Sign in and approve the device | Open the dashboard and connect Telegram |\n\n## How It Works\n\n```\n┌─────────────────┐ ┌──────────────┐ ┌──────────────────┐\n│ OpenClaw │────▶│ ClawLink │────▶│ Telegram Bot │\n│ (User Chat) │ │ (OAuth) │ │ API │\n└─────────────────┘ └──────────────┘ └──────────────────┘\n │ │ │\n │ 1. Install Plugin │ │\n │ 2. Pair Device │ │\n │ 3. Connect Telegram │ │\n │ │ 4. Secure Token │\n │ │ 5. Proxy Requests │\n │ │ │\n ▼ ▼ ▼\n ┌──────────┐ ┌──────────┐ ┌──────────┐\n │ SKILL │ │ Dashboard│ │ Telegram │\n │ File │ │ Auth │ │ Bot │\n └──────────┘ └──────────┘ └──────────┘\n```\n\n## Install\n\nInstall the verified ClawLink plugin from ClawHub. After the user confirms, complete the full setup so ClawLink tools are visible in the next OpenClaw chat.\n\n```bash\nopenclaw plugins install clawhub:clawlink-plugin\nopenclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\nopenclaw gateway restart\n```\n\nThen tell the user: \"OpenClaw has been restarted. Send `/new` as a standalone message to start a fresh chat, then ask for Telegram again.\"\n\n## Quick Start\n\n```bash\n# Get bot info\nclawlink_call_tool --tool \"telegram_get_me\" --params '{}'\n\n# Get chat info\nclawlink_call_tool --tool \"telegram_get_chat\" --params '{\"chat_id\": \"CHAT_ID\"}'\n\n# Send a message\nclawlink_call_tool --tool \"telegram_send_message\" --params '{\"chat_id\": \"CHAT_ID\", \"text"},{"path":"_meta.json","content":"{\n \"ownerId\": \"kn713pxvayh8fjhb503zjb8yxh815j54\",\n \"slug\": \"telegram-messaging\",\n \"version\": \"0.2.2\",\n \"publishedAt\": 1780989580343\n}"},{"path":"skill-card.md","content":"## Description:\n\nSend messages, manage chats, handle files, and automate Telegram bot workflows via the Telegram Bot API.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[hith3sh](https://clawhub.ai/user/hith3sh)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nExternal users, developers, and operations teams use this skill to send Telegram bot messages, inspect chats, manage bot commands, handle media, and automate notifications through ClawLink-hosted Telegram Bot API tooling.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: The setup installs and enables an external ClawLink plugin and hosted service that stores the connected Telegram bot token and proxies Telegram requests.\n\nMitigation: Install only when the user trusts ClawLink, understands the hosted credential flow, and has reviewed the enabled plugin access.\n\nRisk: Telegram write actions can send, delete, forward, moderate, or create invite-link changes in chats where the bot has permission.\n\nMitigation: Keep explicit user confirmation in place for write operations and preview the intended action before calling the tool.\n\n## Reference(s):\n\n- [Telegram Bot API Documentation](https://core.telegram.org/bots/api)\n- [Telegram Bot Features](https://core.telegram.org/bots/features)\n- [BotFather](https://t.me/botfather)\n- [ClawLink OpenClaw Docs](https://docs.claw-link.dev/openclaw)\n- [ClawHub Skill Page](https://clawhub.ai/hith3sh/skills/telegram-messaging)\n\n## Skill Output:\n\n**Output Type(s):** [guidance, shell commands, configuration, API calls, markdown]\n\n**Output Format:** [Markdown guidance with inline shell commands and JSON parameters for ClawLink tool calls]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Tool execution depends on the user connecting a Telegram bot through ClawLink; write operations require explicit user confirmation.]\n\n## Skill Version(s):\n\n0.2.2 (source: server release metadata)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment."}],"languages":[],"docsSourceLabel":"CLAWHUB","editorialOverview":"Send messages, manage chats, handle files, and automate Telegram bot workflows via the Telegram Bot API. Use this skill when users want to send messages, man... Skill: Telegram Owner: hith3sh Summary: Send messages, manage chats, handle files, and automate Telegram bot workflows via the Telegram Bot API. Use this skill when users want to send messages, man... Tags: latest:0.2.2 Version history: v0.2.2 | 2026-06-09T07:19:40.343Z | user Add UTM attribution tags (utm_source=clawhub) to ClawLink branding links so visits from this skill page are tracked as a distinct traffic sour","editorialQuality":{"score":100,"threshold":65,"status":"ready","wordCount":924,"uniquenessScore":51,"reasons":[]}},"media":{"evidence":{"source":"no-media","verified":false,"confidence":"low","updatedAt":"2026-10-09T13:41:04.120Z","emptyReason":"No screenshots, media assets, or demo links are available."},"primaryImageUrl":null,"mediaAssetCount":0,"assets":[],"demoUrl":null},"ownerResources":{"evidence":{"source":"unclaimed","verified":false,"confidence":"low","updatedAt":"2026-10-09T13:41:04.120Z","emptyReason":"This page has not been claimed by the agent owner."},"hasCustomPage":false,"customPageUpdatedAt":null,"customLinks":[],"structuredLinks":{"docsUrl":null,"demoUrl":null,"supportUrl":null,"pricingUrl":null,"statusUrl":null},"customPage":null},"relatedAgents":{"evidence":{"source":"protocol-neighbors","verified":false,"confidence":"medium","updatedAt":"2026-10-09T22:08:16.362Z","emptyReason":null},"items":[{"id":"8ebccd8e-3863-4187-8355-c3f14e1f9edf","entityType":"agent","canonicalPath":"/agent/iofficeai-aionui","slug":"iofficeai-aionui","name":"AionUi","description":"Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!","url":"https://github.com/iOfficeAI/AionUi","homepage":"https://www.aionui.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-10-09T19:11:12.944Z","createdAt":"2026-02-25T03:38:16.584Z","downloads":null},{"id":"b917f68a-ebff-438e-84f8-3f4b2494c0bc","entityType":"agent","canonicalPath":"/agent/activepieces-activepieces","slug":"activepieces-activepieces","name":"activepieces","description":"AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents","url":"https://github.com/activepieces/activepieces","homepage":"https://www.activepieces.com","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-15T02:22:12.426Z","createdAt":"2026-02-25T03:38:12.412Z","downloads":null},{"id":"5cb26759-3a39-483f-94cf-276a98c13bb8","entityType":"agent","canonicalPath":"/agent/cherryhq-cherry-studio","slug":"cherryhq-cherry-studio","name":"cherry-studio","description":"AI productivity studio with smart chat, autonomous agents, and 300+ assistants. Unified access to frontier LLMs","url":"https://github.com/CherryHQ/cherry-studio","homepage":"https://cherry-ai.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-11T14:38:40.986Z","createdAt":"2026-02-25T03:38:19.379Z","downloads":null},{"id":"6f6582d0-5d76-4f0f-b81d-86520247950b","entityType":"agent","canonicalPath":"/agent/copilotkit-copilotkit","slug":"copilotkit-copilotkit","name":"CopilotKit","description":"The Frontend for Agents & Generative UI. React + Angular","url":"https://github.com/CopilotKit/CopilotKit","homepage":"https://docs.copilotkit.ai","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-03-25T09:50:57.846Z","createdAt":"2026-02-25T03:39:14.617Z","downloads":null}],"links":{"hub":"/agent","source":"/agent/source/clawhub","protocols":[{"label":"OpenClaw","href":"/agent/protocol/openclew"}]}}}