Telegram Chip
Unified Telegram core (HTTP API + MCP stdio + tgdl + sales hooks) with single-session Telethon architecture. Use when setting up Telegram automation, reading/sending Telegram messages via local API, exporting chat history, or troubleshooting Telethon auth/session conflicts.
Install
$ agentstack add skill-qwwiwi-agentos-skills-public-telegram-chip ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ● Environment & secrets Used
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-qwwiwi-agentos-skills-public-telegram-chip) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
telegram-chip
Unified Telegram core with a single Telethon client and optional sales hooks.
Correct authorization procedure (important)
Use this exact order:
- Prepare
.envwithTELEGRAM_API_IDandTELEGRAM_API_HASH. - Run
./generate-session.shand complete interactive login:
- phone number (
+7...), - Telegram login code,
- 2FA password (if enabled).
- Verify
TELEGRAM_SESSION_STRINGis present in.env. - Start only one active Telethon process for this session string.
Credential acquisition recommendations
When obtaining TELEGRAM_API_ID / TELEGRAM_API_HASH at my.telegram.org/apps:
- Prefer phone mobile internet (without Wi‑Fi/VPN), or
- Use a clean private/incognito browser session.
This reduces auth friction and weird web-session/cache issues.
Hard rules
- Never share
TELEGRAM_SESSION_STRINGin chats/logs. - If session leaks, revoke/regenerate immediately.
- One session string must not be used by multiple concurrent Telethon processes (prevents
AuthKeyDuplicatedError). - Use HTTP API (
api.py) as the only integration point. - Do not use direct Telethon imports outside this skill runtime (
skills/telegram-chip/.venv).
Reading polls
Anonymous multi-choice polls hide per-option vote counts from non-participants. Ask the session-owner human to vote manually in Telegram first, then GET /chats/{chat_id}/messages/{message_id} returns poll.results[].voters. See README.md → "Reading polls" for details.
Read receipts (readoutboxmax_id)
To check if a peer has read a message you sent: sent_message_id <= read_outbox_max_id ⇒ read.
GET /chats/listreturnsread_outbox_max_id,read_inbox_max_id,top_message_idper chat (alongsideunread_count).GET /chats/{chat_id}/read_status— single-peer endpoint, lighter than/chats/list(usesGetPeerDialogsRequest).
read_outbox_max_id == top_message_id ⇒ peer прочитал всё.
See README.md → "Read receipts" for details.
See README.md and TROUBLESHOOTING.md for full setup and failure recovery.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: qwwiwi
- Source: qwwiwi/agentos-skills-public
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.