Prototype · Preview: every server in the official registry, synced every 30 minutes. Sign in with Google to write reviews.Prototype · updated every 30 min
PopNx MCPMCP servers for people who use AI · explained in plain words

tlgr Skill

Repository ↗

by tlgrcli★ 2011 skills

Install

What it does

CLI for Telegram — agent-friendly, daemon-based, with webhook event push.

  • Connects Instruction files the AI reads
  • Account or key Not confirmed yet (README not read yet)
  • Category Coding
For makers: add a badge to your README

If you made this, paste this code into your README. The badge links back to this page.

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/skill/tlgrcli-tlgr.svg)](https://mcp.popnx.com/en/skills/tlgrcli-tlgr)

Use together with

MCP servers that connect the AI to services for the same work

REA

Reverse engineer anything from your terminal or agent with one CLI and MCP server.

by morlutoWidely used↓ 388.7K/wk★ 464.1KUpdated 5 days ago

MCP · Connects a serviceRuns on your computer

Fallow

Codebase intelligence for TypeScript and JavaScript, exposed as structured MCP analysis tools.

by fallow-rsWidely used↓ 2.4M/wk★ 5.4KUpdated today

MCP · Connects a serviceRuns on your computer

Desktop Commander

MCP server for terminal commands, file operations, and process management

by wonderwhy-erWidely used↓ 740.3K/wk★ 10.3KUpdated 5 days ago

MCP · Connects a serviceRuns on your computer

Similar Skills

Same kind of work, ordered like the Skills list

Compared with similar ones
This one
tlgr
reaandrej-karpathy-skillsgraphifyMoneyPrinterTurbo
Makertlgrclimorlutomultica-aiGraphify-Labsharry0703
Skills11111
GitHub stars201463,670233,682148,887143,987
Last code changeOct 28, 2026Nov 17, 2026Apr 20, 2026Nov 17, 2026Nov 16, 2026
LicenseMITMIT–Apache-2.0MIT

1 skills (instruction sets) by tlgrcli that an AI reads and follows · not an MCP server

How a Skill differs from MCP

MCP = the hands

Connects the AI to an outside service or data, such as reading Notion or creating an invoice. A program or server has to be running.

Skill = the manual

A text file that teaches the AI how to do a task. It connects to nothing.

Some overlap: a few Skills run scripts that call tools, and a few MCP servers only send knowledge. Start from the task you want done.

Works with

Claude CodeCodexCursor

From the maker’s README and the folders in the repo

Install

Is it safe?

  • Who made it

    GitHub account tlgrcli (organization) is only 8 months old: take extra care

  • Use and upkeep

    ★ 201 stars, few users so far · code last changed Oct 28, 2026

  • Any scripts?

    No, plain text files the AI reads and follows

  • Uses the internet?

    No scripts, so it does not go online by itself

  • Changes machine-wide settings?

    No hooks or writes to machine settings found

Checked automatically from the repo files at commit 9b441f2 (read only, nothing was run). Not a safety guarantee: read it and decide for yourself

First: which AI do you use?

Pick your app and this page shows only how to install it there

Option 1Upload to claude.ai (web and app)

Uploading to claude.ai would fail: the description is over 200 characters (441). Use "Let the AI install it" instead

Option 1Let Claude Code install it

Copy this sentence and paste it into a Claude Code chat

Where to install

Checking the commands · copy buttons appear once they pass

Checking the commands · copy buttons appear once they pass

For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing

The AI tells you what it will do first and asks your permission at every step

Restart Claude Code, then type /tlgr or ask for a matching task and Claude picks it up

Checked against official docs Nov 12, 2026 · Source: code.claude.com

For Terminal users

A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.

The maker’s recommended way

Install Node.js (if you don’t have it)

Already installed? Check first · Open Terminal, type this command and press Enter

node -v
  • A version number such as v26.13.1 = installed, skip this step
  • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
How to open Terminal

Mac: press ⌘ + Space, type Terminal, press Enter

Windows: open Start, type Windows PowerShell, then Open

Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

Open the Node.js download page ↗

When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

Install once; it works for everything that needs Node.js

Checking the commands · copy buttons appear once they pass

Copied from the maker’s README; it downloads and runs the maker’s code

  1. Open Terminal

    Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead

  2. Copy the skill folder to ~/.claude/skills

    This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md

    Checking the commands · copy buttons appear once they pass

  3. Restart Claude Code, then type /tlgr or ask for a matching task and Claude picks it up

Skills you install yourself work in the ChatGPT desktop app, Codex CLI and the Codex IDE extension · ChatGPT on the web and mobile cannot use skills you install yourself, only skills that come with a plugin from the directory

ChatGPT desktop app

The ChatGPT desktop app has Codex built in, and Codex reads skills from ~/.agents/skills

Option 1Let ChatGPT install it

Open Codex in the ChatGPT desktop app and paste this sentence into the chat

Where to install

Checking the commands · copy buttons appear once they pass

Checking the commands · copy buttons appear once they pass

The AI always shows you the path before installing

The AI tells you what it will do first and asks your permission at every step

Option 2Put the folder there yourself

Put the tlgr folder at ~/.agents/skills/tlgr

~ is your home folder ($HOME)

For Terminal users

A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.

  1. Open Terminal

    Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead

  2. Copy the skill folder to ~/.agents/skills

    This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md

    Checking the commands · copy buttons appear once they pass

After installing

  • ChatGPT desktop app: open Skills in the sidebar to see that the skill is there
  • To use it: in ChatGPT type @ and pick the skill · in Codex CLI or the IDE extension run /skills or type $ and the skill name
  • Codex picks up newly installed skills by itself; if one does not show up, restart Codex

Checked against official docs Nov 15, 2026 · Source: learn.chatgpt.com

ChatGPT on the web and mobile

Skills you install yourself do not work here; only skills that come with a plugin from the directory

To use this skill with ChatGPT, use the ChatGPT desktop app as above

Checked against official docs Nov 15, 2026 · Source: learn.chatgpt.com

Option 1Let Codex install it

Copy this sentence and paste it into a Codex chat · Works in Codex inside the ChatGPT desktop app, Codex CLI and the IDE extension

Where to install

Checking the commands · copy buttons appear once they pass

Checking the commands · copy buttons appear once they pass

For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing

The AI tells you what it will do first and asks your permission at every step

Codex picks up newly installed skills by itself; if one does not show up, restart Codex · To use it: in ChatGPT type @ and pick the skill · in Codex CLI or the IDE extension run /skills or type $ and the skill name

Checked against official docs Nov 15, 2026 · Source: learn.chatgpt.com

For Terminal users

A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.

  1. Open Terminal

    Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead

  2. Copy the skill folder to ~/.agents/skills

    This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md

    Checking the commands · copy buttons appear once they pass

  3. Restart Codex, then ask for a matching task; Codex lists the skill

Option 1Let Cursor install it

Copy this sentence and paste it into a Cursor chat

Where to install

Checking the commands · copy buttons appear once they pass

Checking the commands · copy buttons appear once they pass

For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing

The AI tells you what it will do first and asks your permission at every step

In Cursor’s Agent chat, type / and pick tlgr

Checked against official docs Nov 12, 2026 · Source: cursor.com

For Terminal users

A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.

  1. Open Terminal

    Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead

  2. Copy the skill folder to ~/.cursor/skills

    This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md

    Checking the commands · copy buttons appear once they pass

  3. In Cursor’s Agent chat, type / and pick tlgr

Option 1Let the AI install it

For other apps that read skills. The sentence gives the paths for Claude Code, Codex and Cursor so the AI picks the one for your app · Copy this sentence into the app’s chat

Where to install

Checking the commands · copy buttons appear once they pass

Checking the commands · copy buttons appear once they pass

For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing

The AI tells you what it will do first and asks your permission at every step

Checked against official docs Nov 12, 2026 · Source: code.claude.com, learn.chatgpt.com, cursor.com

For Terminal users

Other apps that support Agent Skills (such as Gemini CLI or GitHub Copilot) use different folders. Check that app’s guide, then copy the folder with the SKILL.md there.

View on GitHub ↗

Skill folders checked against the official Claude Code, Codex and Cursor guides on Nov 11, 2026

View the original SKILL.md

The text below comes from the maker’s repo, not from PopNx MCP

6,162 characters · Open the full file on GitHub

---
name: tlgr
description: Read and act on a personal Telegram account from the terminal with the tlgr CLI (MTProto user account, not a bot). Use when the user wants to check unread Telegram chats, read or search message history, send, reply to, edit, forward or schedule messages, manage chats, groups, channels, contacts, folders, reactions, polls, media or stories, or receive Telegram events through a webhook. Every command answers in JSON with stable exit codes.
metadata: {"openclaw": {"requires": {"bins": ["tlgr"]}, "os": ["darwin", "linux"]}}
---

# tlgr: Telegram for agents

`tlgr` controls a real Telegram user account over MTProto through a local
daemon. Everything you can do in a Telegram app, you can do from a shell:
messages, chats, groups, channels, contacts, media, stories, polls and more.
The full reference is `AGENT.md` in the repository, and `tlgr schema --json`
describes every command, flag and response.

## Install and check

```bash
pipx install tlgr-cli          # the command is `tlgr`
tlgr agent whoami --json       # active account, daemon health, schema version
tlgr status --check            # non-zero exit when anything is wrong
```

The daemon starts itself on first use. If `whoami` reports no account, go to
**Logging in**.

## Rules that matter

1. **Always pass `--json`.** Errors are JSON on stdout too, and the exit code
   is the contract. `--results-only` strips the envelope and `--select a,b.c`
   projects fields.
2. **Reading can be visible.** `chat open` sends a read receipt the other side
   sees and clears the owner's unread badge. To look without a trace use
   `chat catchup`, `message list` or `chat open --no-read`. A read receipt
   cannot be taken back; `chat unread` only restores the owner's badge.
3. **Name the account when there is more than one.** Pass `-a <alias>` so a
   message never goes out from the wrong identity.
4. **Secrets never go in argv.** Use `--password-env`, `--api-hash-env`,
   `--token-env` and friends, or their `-stdin` and `-file` forms.
5. **Chats are `@username` or a numeric id.** Display names and phone numbers
   are not accepted. Put negative ids after `--`:
   `tlgr message list --json --limit 5 -- -100123456`.
6. **Preview before destructive calls** with `--dry-run`, and confirm with the
   user before deleting, leaving, blocking or sending to someone new.
7. **Respect rate limits.** Exit 7 carries `wait_seconds`; wait that long
   before retrying. Exit 13 means the answer is unknown, never treat it as a
   "no".

## Everyday loop

```bash
tlgr catchup --json                                  # every unread chat with recent messages, no read receipts
tlgr message list @alice --json --limit 20           # silent history
tlgr message search @team "invoice" --json           # search one chat
tlgr message send @alice "On my way" --json          # send
tlgr message send @alice "Yes" --reply-to 4211 --json
tlgr message edit @alice 4212 "Yes, 5pm" --json
tlgr message forward @news 88 90 --to @archive --json
tlgr chat open @alice --json                          # history plus a visible read receipt
```

Long text over 4096 UTF-16 units is refused unless you add `--split`.
`--typing-auto` shows "typing..." for a length-based duration before sending.
`--schedule TS` schedules instead of sending now.

Lists return `{items, has_more, next_cursor}`. Pass `--cursor <next_cursor>`
until `has_more` is false, or use `--all`.

## Beyond messages

Each group has `--help` and a generated page in `docs/reference/`:

| Group | Examples |
|---|---|
| `chat` | `list --unread`, `get --full`, `posters`, `members`, `archive`, `mute`, `leave` |
| `contact`, `user`, `resolve` | find, add and inspect people; turn a link or username into a peer |
| `reaction`, `poll`, `todo`, `location` | react, vote, create polls and checklists, share places |
| `media`, `sticker`, `gif`, `emoji` | upload, download, export |
| `story`, `folder`, `profile`, `privacy` | post stories, organise folders, change settings |
| `account` | `list`, `check`, `session list --unconfirmed` |

Before planning something unusual, run `tlgr agent capabilities --json`. It
separates what this build cannot do, what this account may not do (Premium,
bot-only, admin-only) and what tlgr refuses on purpose, each with a reason.

## Logging in

Login is two ordinary commands, so only reading the code needs a person:

```bash
tlgr auth send-code +15551234567 --alias main --api-id 12345 --api-hash-env TLGR_API_HASH --json
tlgr auth verify-code 12345 --alias main --json
```

Ask the user for the code Telegram sends them. Exit 4 with
`AUTH_PASSWORD_REQUIRED` means two-step verification is on: rerun
`verify-code` with `--password-env TLGR_2FA_PASSWORD` after the user sets
that variable. Never ask the user to paste a password into the chat.

## Reacting to events

To be woken by Telegram instead of polling, the daemon can push events to an
HTTP endpoint, signed with HMAC:

```bash
tlgr webhook set --url https://example.com/hooks/agent \
  --events message_new,message_edited --secret-env TLGR_WEBHOOK_SECRET --enabled
tlgr webhook test
```

`tlgr events list --json` lists all event types. Deterministic auto-replies and
forwards that need no model can run in the daemon as jobs in
`~/.tlgr/jobs.yaml`.

## Limiting what you can do

`--enable-commands message.list,message.send,chat.list` (or
`TLGR_ENABLE_COMMANDS`) allows only those operations; anything else exits 6.
Use it when the user wants you read-only or restricted to a few actions. It is
a guard rail, not a security boundary.

## Exit codes

| Code | Meaning | What to do |
|---|---|---|
| 0 | success | `meta.already: true` means it was already done |
| 2 | bad arguments | fix the call; check `tlgr schema <command> --json` |
| 3 | empty | nothing matched |
| 4 | auth needed | log in again |
| 5 | not found | wrong chat or id |
| 6 | permission denied or blocked by `--enable-commands` | do not retry |
| 7 | rate limited | wait `wait_seconds` |
| 8 | transient | retry shortly |
| 11, 12 | daemon or IPC problem | `tlgr daemon status --json`, then `tlgr daemon restart` |
| 13 | indeterminate | report as unknown |

Discussion

Ask, share a tip or report that it does not work. Sorted by what people marked helpful.

No posts yet. Be the first to ask or share.

Posts here are written by users, not the PopNx team.

Sign in to post

From GitHub

GitHub stars
201
Maker
tlgrcli
License
MIT
Last code change
Oct 28, 2026
SKILL.md files in the repo (including translated copies and templates)
1
Topics
agent-skills, ai-agents, automation, cli, llm-tools, mtproto, osint, python, telegram, telegram-cli, telethon, userbot