Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
skillhq avatar

Telegram

skillhq/telegram

  • 435 installs
  • 11 repo stars
  • Updated June 1, 2026
  • skillhq/telegram

telegram is a developer skill that helps build Telegram bots and webhooks to send messages, handle commands, inline keyboards, and channel notifications from a backend or agent service.

About

telegram is a skillhq skill that teaches coding agents to integrate Telegram Bot API features into backend and agent services. It covers webhook setup, command routing, inline keyboard interactions, and channel notification patterns so services can push alerts and accept user input through Telegram. Developers reach for telegram when adding bot commands to ops dashboards, wiring agent replies to a messaging channel, or broadcasting deployment and monitoring events to a team channel. The skill assumes standard Telegram bot architecture—HTTP webhooks or polling, token-authenticated requests, and handler maps for updates—rather than generic chat UI work. Use it while scaffolding notification pipelines, conversational agent interfaces, or lightweight mobile-friendly control surfaces without building a separate client app.

  • Bot token setup and webhook configuration
  • Command handlers and inline keyboard UX
  • Outbound alerts and scheduled messaging
  • Secure handling of chat IDs and API secrets

Telegram by the numbers

  • 435 all-time installs (skills.sh)
  • +8 installs in the week ending Aug 5, 2026 (Skillselion tracking)
  • Ranked #1,008 of 4,347 Backend & APIs skills by installs in the Skillselion catalog
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/skillhq/telegram --skill telegram

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs435
repo stars★ 11
Last updatedJune 1, 2026
Repositoryskillhq/telegram ↗

How do you build Telegram bot webhooks and commands?

Build Telegram bots and webhooks—send messages, handle commands, inline keyboards, and channel notifications from your backend or agent.

Who is it for?

Backend developers adding Telegram bots, alerts, or command interfaces to APIs, agents, or internal tooling.

Skip if: Projects needing Slack, Discord, or SMS integrations without Telegram, or teams prohibited from third-party messaging APIs.

When should I use this skill?

A developer asks to send Telegram messages, register bot commands, configure webhooks, or add inline keyboard interactions from a service.

What you get

Telegram bot handlers, webhook endpoints, inline keyboard flows, and channel notification integrations.

  • webhook handlers
  • command routers
  • notification integrations

Files

SKILL.mdMarkdownGitHub ↗

📬 Telegram CLI

Fast Telegram CLI for reading, searching, and sending messages.

🎯 When to Use

Use this skill when the user:

  • Asks to check Telegram messages or inbox
  • Wants to search Telegram for a topic/keyword
  • Wants to send a Telegram message or reply to one
  • Asks about a Telegram group, contact, or chat
  • Wants to see unread messages
  • Needs to look up group members or admins
  • Wants to mute/unmute a noisy chat or group
  • Needs to kick/remove a user from a group
  • Wants to promote a member to admin
  • Wants to transfer ownership of a group/channel to someone else
  • Wants to export or sync chat history to files
  • Asks to organize chats into folders
  • Wants to check their logged-in account or session status

📦 Install

npm install -g @skillhq/telegram

🔐 Authentication

First-time setup requires API credentials from https://my.telegram.org/apps

telegram auth                                # First-time login
telegram logout                              # Clear saved session
telegram check                               # Verify session is valid
telegram whoami                              # Show logged-in account
telegram whoami --json                       # Account info as JSON

📖 Commands

Reading Messages

telegram inbox                               # Unread messages summary
telegram chats                               # List all chats
telegram chats --type group                  # Filter: user, group, supergroup, channel
telegram chats -n 200                        # List up to 200 chats
telegram read "ChatName" -n 50               # Read last 50 messages
telegram read "ChatName" --since "1h"        # Messages from last hour
telegram read "ChatName" --until "2h"        # Messages up to 2 hours ago
telegram read @username -n 20                # Read DM with user
telegram read 123456789 -n 10               # Read by chat ID

Searching

telegram search "query" --chat "ChatName"    # Search within chat
telegram search "query" --all                # Search all chats (global)
telegram search "query" -n 20               # Limit results

Sending Messages

telegram send @username "message"            # Send DM
telegram send "GroupName" "message"          # Send to group
telegram reply "ChatName" 12345 "response"   # Reply to message ID

Contacts & Groups

telegram contact @username                   # Get contact info
telegram members "GroupName"                 # List group members
telegram members "GroupName" -n 500          # Fetch up to 500 members
telegram admins "GroupName"                  # List admins only
telegram groups                              # List all groups
telegram groups --admin                      # Groups where you're admin
telegram kick "GroupName" @username           # Remove user from group
telegram promote "GroupName" @username        # Promote a member to admin
telegram promote "GroupName" @username --rank "Mod"  # Promote with a custom admin title
telegram promote "GroupName" @username --add-admins  # Allow them to add admins too
telegram transfer-owner "GroupName" @username # Hand over ownership (prompts for 2FA password)

`transfer-owner` notes:

  • Irreversible: you drop to a regular admin/member and only the new owner can transfer it back.
  • Requires two-step verification (cloud password) on your account; it is prompted for securely at runtime.
  • Supergroups and channels only - convert a basic group to a supergroup first.
  • The target must already be a member. Telegram also blocks transfer for ~24h after a new login and ~7 days after setting/changing your 2FA password.
  • Prompts you to retype the group name to confirm; pass -y to skip that confirmation.

Muting

telegram mute "ChatName"                     # Mute forever
telegram mute "ChatName" -d 1h               # Mute for 1 hour
telegram mute @username -d 8h                # Mute DM for 8 hours
telegram mute "GroupName" -d 1d              # Mute for 1 day
telegram unmute "ChatName"                   # Unmute

Folders

telegram folders                             # List all folders
telegram folder "Work"                       # Show chats in folder
telegram folder-add "Work" "ProjectChat"     # Add chat to folder
telegram folder-remove "Work" "ProjectChat"  # Remove chat from folder

Sync / Export

telegram sync                                # Sync last 7 days to ./telegram-sync
telegram sync --days 30                      # Sync last 30 days
telegram sync --since "12h"                  # Sync messages from last 12 hours
telegram sync --until "2d"                   # Sync messages up to 2 days ago
telegram sync --all                          # Sync entire chat history (no time limit)
telegram sync --chat "ChatName"              # Sync specific chat only
telegram sync --output ~/exports             # Custom output directory
telegram sync --resume                       # Incremental: only fetch new messages
telegram sync --resume --all                 # Keep a complete archive up to date

Incremental sync (`--resume`):

  • Tracks last synced message ID per chat in .sync-meta.json
  • On subsequent runs, only fetches messages newer than last sync
  • Appends new messages to existing markdown files
  • Combine with --all to maintain a complete, up-to-date archive

📤 Output Formats

Most commands support multiple output formats:

FlagUse Case
(default)Human-readable terminal output
--jsonStructured JSON for programmatic processing
--markdownMarkdown-formatted for display or export
telegram inbox --json                        # JSON format
telegram inbox --markdown                    # Markdown format
telegram read "Chat" --json                  # JSON with messages array
telegram read "Chat" --markdown              # Markdown with messages
telegram chats --json                        # JSON with chat list
telegram members "Group" --markdown          # Markdown member list

Supported on: inbox, read, search, chats, members, groups, contact, whoami

📎 Media Metadata

Messages containing media (photos, videos, documents, voice notes, stickers, etc.) now include metadata instead of showing "(no text)":

Media TypeDisplay
Photo[📷 Photo]
Video[🎥 Video (2.1 MB)]
Document[📎 report.pdf (540.0 KB)]
Voice[🎤 Voice message]
Audio[🎵 song.mp3 (3.2 MB)]
Sticker[😀 Sticker]
GIF[🎬 GIF]
Location[📍 Location]
Contact[👤 Contact]
Poll[📊 Poll]

In JSON output, messages include mediaType, fileName, and fileSize fields when media is present.

🤖 AI Agent Guidance

When using this CLI as an AI agent:

  • For processing data (counting, filtering, extracting): use --json
  • For displaying to the user: use default or --markdown
  • Chat identification: names are partial-matched (e.g., "MetaDAO" matches "MetaDAO Community"), usernames must start with @, numeric IDs also work
  • Read operations are safe to run without confirmation
  • Write operations (send, reply, kick, promote, transfer-owner) should be confirmed with the user before executing
  • `transfer-owner` is irreversible and interactive (it prompts for a 2FA password and a typed confirmation), so it cannot be run unattended; never script it on a user's behalf without explicit instruction
  • Rate limiting: avoid rapid successive calls; the Telegram API has rate limits
  • Large groups: use -n to limit members output on very large groups
  • Full archive: use telegram sync --all --chat "Name" to export complete chat history
  • Keeping archives fresh: use telegram sync --resume to incrementally update previous exports
  • Media-rich chats: messages with photos/videos/files now show metadata, not just "(no text)"

💡 Examples

Check inbox for unread messages:

telegram inbox

Read recent messages from a group:

telegram read "MetaDAO Community" -n 20

Get messages from the last 2 hours:

telegram read "Project Chat" --since "2h"

Search for a topic across all chats:

telegram search "futarchy" --all

Search within a specific chat:

telegram search "deadline" --chat "Work Team"

Send a message:

telegram send @username "Hello, checking in!"

Export a chat's complete history:

telegram sync --all --chat "Project Chat" --output ~/exports

Incrementally update an existing export:

telegram sync --resume --output ~/exports

Filter chats by type:

telegram chats --type channel --json

Kick a user from a group:

telegram kick "My Group" @spammer

Promote a member to admin:

telegram promote "My Group" @trustedmember

Transfer ownership of a group to someone else:

telegram transfer-owner "My Group" @newowner

📝 Notes

  • Chat names can be partial matches (e.g., "MetaDAO" matches "MetaDAO Community")
  • Usernames must start with @ (e.g., @username)
  • Chat IDs (numeric) can be used anywhere a chat name is accepted
  • Messages are returned in reverse chronological order (newest first)
  • Time flags (--since, --until) accept formats like "1h", "30m", "7d"
  • The sync command creates one markdown file per chat in the output directory
  • Sync metadata (.sync-meta.json) enables incremental sync with --resume
  • Sender names are cached per request for faster syncs (avoids redundant API calls)
  • Messages paginate automatically — no silent truncation for large chats

Related skills

open.feishu.cnLark Openapi ExplorerInstantly explore, test, and generate calls against the full Lark (Feishu) OpenAPI surface without leaving their agent workflow.493klarksuiteLark EventConsume real-time events from Lark/Feishu as structured NDJSON streams inside AI agent workflows.387k16klarksuiteLark Openapi ExplorerWhen an existing Lark/Feishu skill or CLI command cannot fulfill a specific requirement and they need to discover and invoke the exact native OpenAPI endpoint.386k16kscrapegraphaiJust ScrapeQuickly search, crawl, extract structured JSON, or monitor web pages without writing custom scraping code.245k41larksuiteLark AppsQuery the current visibility and permission scope of a Lark (Feishu) app without writing HTTP client code.235k16kmattpocockDesign An InterfaceGenerate multiple radically different interface or API designs in parallel before committing to one.188k198k

FAQ

What Telegram features does the telegram skill cover?

The telegram skill covers Bot API webhooks, command handlers, inline keyboards, and channel notifications. It helps developers connect backend or agent services to Telegram for inbound commands and outbound alerts.

Can agents use telegram for notifications?

Yes. The telegram skill supports wiring agent or API backends to send channel notifications and process user commands through Telegram webhooks, giving teams a lightweight messaging control surface.

Backend & APIsintegrationsbackend
Browse by category
AI & AgentsFrontend & DesignBackend & DataDev ToolsAutomationTesting & ReviewSecurityMonitoring & CloudDocs & Planning
Design & frontend
Design systemsAnimation & motionAccessibility (a11y)CSS & TailwindUI designUXDesign to codeshadcn/uiLanding pagesBest design skills
Most searched skills
find-skillscavemanfrontend-designbrainstormingsystematic-debuggingstop-slopemil-design-engui-ux-pro-maxkarpathy-guidelinesweb-design-guidelinesreact-best-practicesgrill-meimprovemicrosoft-foundryagent-browser
Browse all listings
All agent skillsAll MCP serversAll marketplacesAll plugins

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.